Boot Camp: Unknown device in device manager

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.

Does Windows Update find a driver for this device? Do not install it, but check. Do you have the Microsoft ACPI driver installed?

No, as of current bootcamp is just not ready or designed for 2018 macbooks. If you check your drivers including Sound Card you will notice microsoft generic drivers in use, check driver info. There is currently no Road Map for a Bootcamp Release for the 2018. Apple recommends using Vmware and Parallels. Apple also will not have a fix for the rebooting issue, where you must shut down windows then power the machine back on to enter MacOS with keyboard and mouse support. They stated it compromises the T2's Security. In english it is what is it.

If you run a SMC Reset and then re-scan for changes, does this device still show up?

Can you run Apple Software Update and check?

It is a known issue, Usualy apple sets it to be under Hidden devices. It controls the battery power usage and this is why bootcamp has such horrible battery life. Also it controls the CPU this is also why bootcamp thermal throttles. I have contacted apple for nearly 3 months at the SR EXEC LEVEL. They state their engineers are working on it and that bootcamp is NOT ready for the 2018 macbooks.

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.

What is the PID/VID of the device?

Can you confirm the year/model of your Mac?

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.

Hi, I have the same missing driver and have constant problems with external devices disconnecting. Particularly external SSDs. I have a 2018 MBPro and the disconnecting drives is causing tons of frustration.

Is this a Windows-only problem? How are these devices connected to the Mac - cables, hubs, etc.?

Do you think this driver is the source of the problem?

It can be. Can you check Windows Event Viewer for error messages for this specific device?

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.

It is an ACPI device. Do you run into any issues with external or internal devices or power-loss?

Is Windows Fast Start enabled?