Boot Camp: Unknown device in device manager

Dubayy2020 wrote:

They state their engineers are working on it and that bootcamp is NOT ready for the 2018 macbooks.

Good to know. Is there a Bug Tracker for this issue?

If the unknown device is not interfering with normal functionality of Bootcamp, you can safely ignore it.

wt7396 wrote:

But there was one time that I shut my laptop when it was fully charged and I turn it on the next day and found it only had 70% battery.

I don't know if this is related to the driver problem though.

It is unrelated. See How Power Nap works on your Mac - Apple Support for reference.

Dubayy2020 wrote:

No, as of current bootcamp is just not ready or designed for 2018 macbooks.

Then the BC Assistant on such models should have been removed with a clear notification. It is a bad idea to have statements like If you see the alert 'Installation cannot proceed with Boot Camp configured' - Apple Support (as referenced in the Mojave-compatible link - Install Windows on your Mac with Boot Camp - Apple Support ) and release products which behave incorrectly.

Dubayy2020 wrote:

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.

This is incorrect. See when are boot camp drivers going to be updated ? and the iMac Pro (Mac computers that have the Apple T2 chip - Apple Support) already works correctly.

The T2 has many issues. Also, 'immature' products should clearly warn the consumer about limitations. 😉 (... but there is always a way out as stated in Apple - Legal - Licensed Application End User License Agreement ).

This is not pointing the finger at you, but the sources of information that you are working with.

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.

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. 😝

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 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 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.

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.

Because ifixit are the rulers of all that is true? The chipset it published directly on apples details specs page. As well as every single repair website out there and under the Re-order ACS (apples ordering system)

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?

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