Boot Camp: Unknown device in device manager

Hi everyone,


I recently upgraded to Mojave and run the installation for Boot Camp for Win10 and found an unknown device in device manager as the picture below:

User uploaded file


The device is on Pci Bus and has (Code 28)

User uploaded file


The device detail: ACPI\INT34BA\3&11583659&0 as following picture:

User uploaded file


I tried reinstall Boot Camp setup for Windows couple times and got the same result.


Please help if anyone has solution for this. Appreciate it and thanks very much

MacBook Pro (15-inch, 2018), macOS Mojave (10.14), Second OS: Windows 10 build 1803

Posted on Sep 25, 2018 9:56 AM

Reply
57 replies

Oct 6, 2018 2:13 PM in response to Loner T

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.

Oct 6, 2018 2:22 PM in response to Dubayy2020

Apart from hardware-related issues, there are issues like Keyboard and touchpad after restart from windows to macOS not working which directly point to T2. From my perspective T2 is a single-point-of-failure. To save real-estate on boards, more such SPoF are created.


I prefer waiting another 12-24 months for maturity in the T2 controller design, before I invest in products with it.

Oct 6, 2018 2:46 PM in response to Loner T

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.

Oct 6, 2018 4:56 PM in response to Dubayy2020

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.

Oct 6, 2018 5:16 PM in response to Loner T

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.

Jan 1, 2019 6:11 PM in response to Loner T

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Boot Camp: Unknown device in device manager

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.