Boot Camp: Unknown device in device manager

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.

I have the same driver error message but otherwise windows seems to work without any problems. I'd like to use it for gaming with my Vega 64 eGPU. Games run fast and never experienced any problem. Your above comment made me think about risks. Are you saying that currently it is unsafe to use MacBook Pro 2018 laptops with Bootcamp or I should be fine running games if no issues appear?

Personally I fortunately had huge success over this weekend in testing an eGPU (razer core x) for gaming in boot camp on my new MacBook with a nvidia manufactured RTX 2080 FE that yielded results essentially what you would expect from desktop gaming running through a multitude of AAA games and benchmarks (4k@40-60 FPS typically), and even managed a decent overclock on the card with Precision x1. Setup was simply plug the eGPU into the MacBook and install nvidia drivers and it just worked. I since swapped my MacBook to the i9 with 1tb storage coming in a few weeks for the long haul (this will be used for work purposes if there are any issues regardless, and my desktop for backup until further testing is completed). I personally would not look to the dGPU built in for gaming personally if you are serious about gaming.

Edit: sorry this was meant for replying to Gator94.

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.

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

Thanks

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?

• Can we get proper replies from Apple?

will the problem be fixed?

• can I get refund/replacement for a damaged MBP?

I suggest you contact Apple Technical Support. If you have bought Macs from a reseller, you should raise this through the reseller as well. If you have a Corporate Business relationship with Apple, you should pursue under the auspices of that relationship.