Boot Camp: Unknown device in device manager

I agree. My 1st comment to the engineers who kept calling me was. Why do you allow it to proceed. Bootcamp can actually overheat the logic board causing warping (documented by Louis Rossmann) he is a well respected apple repair company. Once the logic board warps the heat-sink can not make contact and causes the processor to fail.

The T2 reboot does not work correctly with rebooting. It is documented again on apple support that a full shut down is required. (updated October 5th 2018) And if you check my other posts you would know that I work Directly with Apple Engineers in the UK Cork Offices and i have been on their team for the last 4 months. They have called me and emailed me to remotely control my laptop to test new drivers and see the conditions of use that are causing certain errors. My information is 100% correct and 100% accurate.

Loner T I follow dubayy2020's posts. He helped me and another guy get their laptops replaced when apple refused to do anything for us. He told us give him 2 days. 2 days later we got a call from apple executive relations asking us to please prepare our laptops and that DHL would come collect them and issue us new ones. He is right thou the T2 restart issues still exist in my 2018 MacBook pro 2.9. We talked to the guy from apple executive about the bootcamp issue and they said that "Dubayy knows more than executive relations does cause he works directly with our engineers" and that's how we found out what he does. So I wouldn't be trying to discredit and apple does say that you cant restart directly from windows to macos but you can go macos to windows. Dubayy is right again cuz even in Mojave the bootcamp partition isn't even listed in startup disks.

AhmedDagreatest wrote:

We talked to the guy from apple executive about the bootcamp issue and they said that "Dubayy knows more than executive relations does cause he works directly with our engineers" and that's how we found out what he does.

Thanks for vouching for Dubayy2020 . 😉

AhmedDagreatest wrote:

So I wouldn't be trying to discredit and apple does say that you cant restart directly from windows to macos but you can go macos to windows. Dubayy is right again cuz even in Mojave the bootcamp partition isn't even listed in startup disks.

I personally would not touch any 2017/2018 Macs for another 12-24 months except as toys. Mojave, T2, APFS - technologies which belong in the Lab. I use a refurbished 2016 MBP or a 2012/2013 MBP. Bleeding edge causes a lot of blood loss. 😝

Nothing against you Loner T. I don't like to brag about my experience. I will say this the T2 is a closed ecosystem chip. Bootcamp can barely access it or read from it. Remember the controller for everything is on the T2, SSD, Sound etc. Apple does not want windows to access the chip. Windows is running a software soundcard basically. Use Skype in Windows 10 Bootcamp (version 7 classic which is still current) you will see the sound will turn off completely. Plug in headphones and switch between the two audio sources it goes back on. The drivers are generic Microsoft. The missing drivers are for Power Management which is controlled by the T2 again Apple does not want windows to have access.

The 2018 Macbook pro's are not bleeding edge. Their specifications are 1 to 2 years behind other builders. Even the last EFI update put a clock lock on the i9 processor. What is the point of having an HK unlocked processor to have a lock put back on it? The i7 2.6 is greatly faster than the i9 now. A complete redesign will occur soon as Apple is calling 2018 merely a Spec Bump. Apple is working on a new form of virtualization that will have barely any performance loss while running windows 10 in VM. Hint... Look at a certain technology for Virtualization that the new Intel chips have.

Dubayy2020 wrote:

I will say this the T2 is a closed ecosystem chip. Bootcamp can barely access it or read from it. Remember the controller for everything is on the T2, SSD, Sound etc. Apple does not want windows to access the chip.

It is a matter of exposing APIs to a driver, which can control all aspects of functionality. The second statement is probably the key.

Dubayy2020 wrote:

The 2018 Macbook pro's are not bleeding edge. Their specifications are 1 to 2 years behind other builders. Even the last EFI update put a clock lock on the i9 processor. What is the point of having an HK unlocked processor to have a lock put back on it? The i7 2.6 is greatly faster than the i9 now.

This is normally the typical product vs technology cycle. If the T2 has documented interfaces, they can be used. If they are not, it creates a longevity issue.

Dubayy2020 wrote:

A complete redesign will occur soon as Apple is calling 2018 merely a Spec Bump. Apple is working on a new form of virtualization that will have barely any performance loss while running windows 10 in VM. Hint... Look at a certain technology for Virtualization that the new Intel chips have.

Remember the old DEC Alpha and HAL. It is interesting to have an Intel (virtually open) technology married to an Apple T2 (a completely closed ecosystem) to build a consumer device. Let us see where this iteration of Virtualization goes. There is no such thing as a Free Lunch. 😉 Once Apple is willing to manufacture a proprietary T2, perhaps a non-Intel/AMD/nVidia GPU (perhaps an eGPU model) is also on the horizon.

We have drifted afar from OP's issue.

The t2 is fully closed off even fan control is disabled from windows. so no we can not build api's to drive like a kext. It would expose T2 and since all control access must go thru the T2 to even send a signal to ramp fans or reduce would leave a loophole. Apple made sure this is closed. Next the Revamp will be Non-Intel chips. Apple has built 3 new factories. Look at the new Iphones Bionic Chip. Hint hint.... Apple also announced that it will make in-house processors. The revamps will be Apple CPU's which is why virtualization is so important.

Dubayy2020 wrote:

The t2 is fully closed off even fan control is disabled from windows. so no we can not build api's to drive like a kext. It would expose T2 and since all control access must go thru the T2 to even send a signal to ramp fans or reduce would leave a loophole. Apple made sure this is closed.

macOS can perform fan control functions, so what is the difference between macOS and Windows from a client (OS) to a server (T2) via an interface like UEFI? The 'closed' part is eventually a control technique. There will always be this 'open' vs 'closed' debate. For example, the Android vs iOS, market share.

Dubayy2020 wrote:

Next the Revamp will be Non-Intel chips. Apple has built 3 new factories. Look at the new Iphones Bionic Chip. Hint hint.... Apple also announced that it will make in-house processors. The revamps will be Apple CPU's which is why virtualization is so important.

The Processors would most likely be based on ARMv8.4-A. macOS will not stray too far from it's BSD/NeXT roots. Virtualization is important for keeping what you can run today, also running tomorrow, otherwise it is a disastrous marketing strategy.

Please read what the T2 is.

T2's closed ecosystem means that no OS outside MACOS can access the T2 Directly or indirectly. The EFI in Mac's is not like an EFI in a PC. Grasping the concept seems to be hard for some. The Difference is MACOS has the encryption keys to access it. Logic board, Touch ID and Touch bar are verified by the T2 before boot, during boot, and in OS without the key windows cannot access it. Microsoft Windows and Linux do not have the capability as during a OS selection the moment you select windows, it disabled the T2 and falls back onto the Intel HM370 Chipset to run windows. The T2 doesn't exist while running windows. Windows only sees missing bridges.

No the new processors are not ARM. I have been fortunate enough to see the roadmap and it is not even remotely similar to ARM.

Dubayy2020 wrote:

The Difference is MACOS has the encryption keys to access it.

As can any other OS. This is not a technical issue, but a marketing/sales decision.

Dubayy2020 wrote:

Microsoft Windows and Linux do not have the capability as during a OS selection the moment you select windows, it disabled the T2 and falls back onto the Intel HM370 Chipset to run windows. The T2 doesn't exist while running windows. Windows only sees missing bridges.

If you 'warm boot' a T2 Mac with FV2 disabled, most of the peripherals work seamlessly between the two OSes. I am certain there is a logical explanation.

Dubayy2020 wrote:

No the new processors are not ARM. I have been fortunate enough to see the roadmap and it is not even remotely similar to ARM.

That is very nice of Apple. Let us see what shows up in 2020.

I think this unknown device maybe relates to Apple T2 Chip.

My MacBook Pro 15 2018 also has the same problem after I installed macOS Mojave. However, this problem didn't show up in boot camp for windows 10 before I installed macOS Mojave. During Mojave update procedure, firmware for bridgeOS (T2 chip) is also updated, but boot camp driver still remains version 6.1, so there is no suitable driver for new bridgeOS firmware.

I think Apple should release new driver for boot camp to solve this problem, although the unknown device problem doesn't affect the use of boot camp for windows 10.

T2 chip is not permitted to communicate with Windows 10 or any other 3rd party OS Under any circumstances.

Driver missing existed before mojave and windows 10 update. It was just kept in HIDDEN DEVICES.

Windows 10 uses software emulation for SSD, SOUND etc. As the T2 chip is 100% disabled once windows 10 selection is made on boot. The Macbook switches to the Intel HM3** series controller for SSD, WIFI, SOUND. And again does NOT USE THE T2 CHIP

Performance is GREATLY reduced in windows due to T2 and missing hardware, the intel i9 thermal throttles as does the 2.6 the ssd is around 30% reduced due to switching to intel HM chipset which does not have the i9 fix applied. There is still a Documented and Known Issue with Sound in Windows 10 DUE to the software emulation.

I agree with you. Maybe I didn't make it clearly. The T2 chip is disabled in windows 10 and bridgeOS has nothing to do with boot camp. What I wanted to state is that the boot camp driver for windows should automatically hide or neglect the unknown device instead of leaving it unknown device in Device Manager ( just as you said that let it be in HIDDEN DEVICES is also a solution) although it does not affect the use of boot camp.

BTW, my i9 processor can work at 3.4~3.5GHz with XTU or 2.9GHz without XTU in windows when it runs 100% burn test. I use eGPU and disable built-in RP560X.

I agree with you. Actually, Bridge OS is modified from watchOS ( simplified iOS) and it runs independently on T2 chip, so Windows could do nothing with T2 chip. However, windows could detect some bridges between PCIe and T2 chip although those bridges are disabled in boot camp. According to my search in Windows Device Manager, the unknown device shares the same paternal devices with series of known PCIe controllers. There are reasons to believe the unknown device is a bridge between T2 and PCIe only working in MacOS.

Additionally, PCH chip from Intel could not be found in the ifixit teardown of MacBook Pro 15 2018 while the chip can be found in the teardown of iMac Pro with T2 chip and MacBook Pro 2017 with T1 chip. I doubt whether MacBook Pro 2018 switches to Intel HM3XX controller or T2 chip simulates the function of PCH chip.

I am having this exact same issue too. New MacBook Pro 15 2018 using macOS High Sierra (company VPN can't support Mojave yet) and Bootcamp 6.1 for Windows 10 Pro version 1803. Other Device ACPI\INT34BA not detected and BootCamp cannot find drivers to correct issue.