BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

For those of you continuing to struggle with this issue, I wanted to provide you with the specific fix that worked for me, which is a variation on the theme. I did not end up having to reinstall Windows, which would have been a nightmare. Hopefully, Apple addresses this issue soon!

I was finally able to boot into my system after a god-awful number of tries. For some reason, it only occasionally works, with seemingly no rhyme nor reason. I tried variations of holding "option" at boot and selecting the boot camp partition, and booting into safe mode on the rare occasion that I was presented with recovery options. It also seemed like variations of having an external monitor and power hooked up seemed to help it boot – I never did get it to boot into Windows without being “docked.” Anyhow, all speculation… but if you can achieve a boot or safe mode of some kind:

In Windows Device Manager, I attempted to disable the Bluetooth adapter as mentioned in other threads, but it did not do anything – the same problem persisted. After trying many other solutions/restores/etc., I looked at the “devices by connection” view of device manager and noticed that Bluetooth was a child of “Broadcom Serial Bus Driver over UART Bus Enumerator.” I tried disabling that parent device (it is under “System devices”), and lo and behold, everything is rock solid again with multiple reboots.

While I have to live without Bluetooth connectivity, I think this is better than reinstalling the whole setup… hopefully we just have to live with that limitation until Apple issues a real fix and then we can re-enable Bluetooth.

Yes, indeed this worked. You don't have to delete the bootcamp partition nor re-install Windows 10.

I summarize what I did

1) Boot into Windows Safe mode

To display the start menu, where you can select the Windows boot option "Safe Mode", you have to press

the function key "F8" during Windows boot. On my MacBook, I had to plug in an USB keyboard,

as "F8" (internal keyboard) seemed not to work

2) When in Windows 10, open the Device Manager. You find it under Control panel / System / Info

3) Select "System Devices" and disable the driver "Intel(R) Serial IO UART Host Controller"

4) Reboot Windows

I had the same, but kept rebooting from the BSOD and kept pressing F1, F8, Shift and Alt rapidly and repeatedly in random order until the Boot Options menu appeared (external USB keyboard/macbook early 2015). From there I chose Troubleshoot->Advanced-> Startup Settings and then "Safe Mode" (by pressing the number key 4 on the keyboard). After booting Windows 10 in safe mode, I uninstalled the DRIVER for the "UART enumerator" device in device manager to disable it, and then did a proper reboot into Windows to disable the device completely (cannot be physically disabled in Safe Mode). This worked for me, getting to the Boot options menu was the hardest part and seemed totally random.

This is great, I have been using Windows on my Macbook for work, invested in expensive software and can't fully trust that I will be able to use my (now crippled) system. So now I have to carry an extra PC laptop around wherever I go, just in case. Great QA Apple. Now do something about it!

Per my few tests (I'm really busy that can't keep proceed testings and I don't accept to pay my time for fix Apple's fault). I can tell that the Bootcamp fail is 100% due to 10.12.1 updates.

I've reported in few weeks ago, but I will summaries it again :

I have 2015MB12 and 2016MB12. Both were running El Captain and Sierra with Bootcamp Win10 1607 without any problem. Until Apple launched 10.12.1 updates for Sierra, my 2015MB12 has core dump with ACPI.sys error when boot from BC Win10. Luckily that my other 2016MB12 was running fine (until last weekend which Bluebooth was disabled but suddenly the BT works again on Wed til now).

After tried couple of "solutions", I still couldn't fix BC Win10 on 2015MB12. Then I deleted the BC partition and rebuilt Bootcamp. I used the same Win10 1607 ISO file (for El Captain & Sierra 10.12.0 too), but ACPI.sys error again after all the BC drivers installed then restarted Windows. I didn't apply any Windows updates yet ! I've tried rebuilt 3 times but still had the ACPI.sys error, I gaveoff. When I found some members here shared their findings that due to BC BT drivers. I rebuilt the BC on my 2015MB12 again and skip not install the BC BT driver. This time, Windows loaded normally !! I immediately run Windows Updates, still no problem, Follow by installed MS Office and run Windows Updates for Office Updates. Still no any problem even tried reboot many times. I'm using BC Win10 1607 without Bluetooth without any problem for more that 2 weeks.

Conclusions :

OK 2015MB12 El Captiain + Bootcamp Windows 10 1607

OK 2015MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

FAIL 2015MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 (core dump, Win10 can't be loaded)

OK 2015MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 with NO Bluetooth driver or disabled

OK 2016MB12 El Captiain + Bootcamp Windows 10 1607

OK 2016MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

OK** 2016MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 (sometimes Bluetooth driver will fail)

OK 2016MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 with NO Bluetooth driver or diabled

keijiazum wrote:

could you pls tell me step by step how to delete broadcom bluetooth?

The following procedures is executed in Windows, not in OS X. (Copied from a previous post by rdragona1994)

1. Boot up into safe boot

2. Go to the device manager.

3. Switch to devices by connection and enable show hidden devices. You are looking for "Broadcom Serial Bus Driver over UART Bus Enumerator". Its parent should be not running (safe mode does this and it's why the computer should even be running now). You want to disable the parent. Should be able to run windows from here after a restart without needing a full restore.

Hi guys, after weeks of waiting... BOOTCAMP IS WORKING after macOS Sierra 10.12.2 Update!

Previously i always had the ACPI.sys error when booting up windows 10, after updating the macOS, boot up your windows and wait for it to repair, trust me it will not loop anymore 😉

thank you apple for the fix 🙂 ✅

@charr328

I had the same issues like the guy who started this topic. What a nightmare that update 10.12.1 from Apple! Windows 10 wouldn't start/boot anymore with Bootcamp.. blue screen with error message like others in this topic.

Now I have everything up and running again. What I did: i restored my iMac back to 10.12.0 via Time Machine. Luckily i had a backup of a few weeks back. The Bootcamp partition with Windows 10 was kept intact during the downgrade to 10.12.0. After restoring Windows en macOS started normally again. The first time the boot to Windows took al few seconds longer because Windows had to find some files back, which could be found now again because of the downgrade from macOS. What i've learned again: always make a backup from macOS as well as Windows. In Windows you also have an option for backing up like on a Mac.

I hope this information helps anyone.

Good luck and greets from The Netherlands. :-)

Hi androo79,

Appreciate what you done. Agreed that better than we are just discussing here. ^_^

I can't just keep waiting as don't know when Apple will release new fixes and will it be created and launched. Therefore, although I still can run Win10 1607 on my 2016 MBR12 with 10.12.1. Finally, I've again erased the Bootcamp partition on my 2015 MBR12 (Still 10.12.1) and re-install Win10 1607. But this time, I follow the valuable advises suggested here, skip NOT install the Bluetooth driver.

Then apply all Windows Updates and reinstall Symantec Endpoint, MS Office 2016, Adobe CC, and all the software which previous running on 10.12.0 BC. Everything are fine for now. My family won't screw up on one MBR Windows10.

Apple immediately please fix the ACPI.sys error in Boot Camp due to your 10.12.1 updates.

Okay. When my 2015MB12 failure to boot from Bootcamp after upgraded to 10.12.1. I've tried interrupted the Win10 boot up before display the ACPI.sys error, then Win10 will display the boot option menu instead of load the Win10 normally. I switched to vary Safe mode (i.e. with Command prompt, with Network, etc.) but still hit ACPI.sys error. I tried F10 for More Option then tried System Recover and many other options for try to fix problem.

How to go into Safe Mode while Win10 boot up:

Plug in an USB keyboard (I used Logitech Unify USB nano receiver for wireless keyboard and mouse). Then power on MB12 and hold the alt button, choose Bootcamp drive to boot Win10. When Win10 logo shows, press the power button to power off the MB12. Repeat the above steps again to power on, boot, power off. After couple times of this interruption, Windows will boot to open a boot option menu.

PS. Highly recommended you boot from macOS normally, open the Bootcamp partition, backup all your working files in your Win10 drive before try to repair the Bootcamp Win10. Just in case the repair methods may crash the Bootcamp partition.

RobjDerby wrote:

Why doesn't apple let you uninstall an OS 10.12.1patch ?

This issue is so frustrating, no point in doing a new Bootcamp install as the same issue will just reccur.

Apple does allow a roll back - macOS Sierra: Revert to a previous macOS version

and it has been suggested...

On Page 1 - Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1 and it works as noted in - Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1 .

On Page 3 - Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1 and as quoted in Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

MB Retina 2015 Sierra 10.12.1 is problematic with Windows Ten.

ad nauseam ad infinitum.

This specific post Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1 shows...

Conclusions :

OK 2015MB12 El Captiain + Bootcamp Windows 10 1607

OK 2015MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

OK 2016MB12 El Captiain + Bootcamp Windows 10 1607

OK 2016MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

... so stick to 10.12.0 on 2015/2016 MB12s.

You are more than welcome to analyze the entire discussion post-by-post, if you like.

Yeah fixed it just now I had to do an online recovery and then run first aid on the disk and with no problems it fixed the problem and now I can use bootcamp. Its abit odd that recovery mode local couldn't do it but the online one could as they are the same program just in different locations.

Hi Guys,

Thanks for the updates. The 10.12.2 works for me.

As mentioned previously, I've rebuilt my 2015MB12. I skipped NOT install the Bootcamp Bluetooth drivers while installing the Win10 1607. Then I can use BT Win10 for weeks without any issue.

Right NOW, I ONLY launched App Store in macOS 10.12.1 and go to Sierra. I can see 10.12.2 is available (I tried Hong Kong and Canada regions). I just downloaded and installed the 10.12.2 on my 2015MB12 and restart automatically.

Checked macOS is already 10.12.2, launched Bootcamp and downloaded BC drivers (saved in USB flash). Rebooted to load BC Win10, checked the BC Broadcom folder of 10.12.2 and 10.12.1, found the packages size are the same, package info are the same, the signature are the same. Then I run and install the Broadcom Bluetooth, The Win10 Device Manager show the Bluetooth installed properly.

Rebooted to load BC Win10 again, NORMAL. Run couples of software and browse Internet, no different. Tested Bluetooth mouse, works. Rebooted again and again for 5 more times, everything resumed normal. Great!

In addition, I also upgraded my 2016MB12 to 10.12.2, also everything normal.

I have 2 Macbooks Retina 12". One is 2015 and One is 2016. * PS. I'm an IT man

When the Sierra launches. I immediately erased both the SSD and installed a fresh Sierra by USB flash. Then I run Bootcamp to install Windows 10 1607. Basically, my two Macbook-12 have identical macOS and Windows running. They both didn't have any issue in the last 2 weeks.

Last night, I upgraded Sierra to 10.12.1. Both my MB-12 were normal, but then 2015 MB-12 failure start Win10 due to ACPI.sys problem. The 2016 MB-12 can load Win10 without any issue.

On the 2015 MB-12, I've tried Windows auto repair, boot vary Safe Modes but still have the same ACPI.sys problem. Then I run Windows System Restore, select the date in 2 days ago, failed. Then select 1 week older, still failed. It wasted me 3 hours in the midnight!!!

In this morning, I launched Bootcamp Assistant in macOS, run Restore to delete the Bootcamp partition. Installed Windows 10 1607 again. However, after Bootcamp drivers installed and reboot, the same ACPI.sys problem happen again!! This time, the Win10 is just Windows with Bootcamp drivers only, no any other drivers or components.

I'm very sure the problem is due to the bug bundled by the latest 10.12.1 which causes ACPPI.sys problem on Macbook Retina 2015.

Psykdel's fix worked for me (Re: BootCamp fails to start after upgrade to MacOS Sierra 10.12.1). I tried about 10 times to boot before it worked and my MacBook was plugged into the standard wall adapter, no monitor. Attached is a photo showing the location of the device to disable (Intel(R) Serial IO UART Host Controller).

I don't know how many times I deleted my Windows partition and reinstalled, trying to work out a fix to this.
I *currently* have a working Windows 10 Bootcamp in my 2015MBR12.

What I did was ran through the install as usual and when it came to the bootcamp software/drivers install at the end of the process, simply said "no" when it asked permission/if I wanted the Bluetooth installed.

Yes, I realize this is hardly a fix and it doesn't help those of you using bluetooth devices with your Windows installations.

It is however, a working install that could be easily updated with an in-windows update of the driver.

<sigh> Apple, please work on this.