BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

same issue here. it all started when my windows 10 couldn't boot showing a BSOD generating an error with ACPI.sys

So i thought it was windows and a went for a clean install through bootcamp. the thing happened again once i tried to install the apple drivers (previously downloaded by bootcamp itself).

APPLE please do something or we can't use windows.

Hi

I seemed to be lucky to have enabled F8 in my previous windows 10 installation. Just read that F8 is disabled by default in Windows 10 (UEFI + SSD) to make the boot process faster :-(

After the BSOD is there the option to restart. Seems that pressing Shift while selecting Restart enters safe mode as well. RobjDerby: Would you please try if this is working.

I think it's a problem of bluetooth driver.

My 2015-early new macbook had had same issue(acpi.sys error), and I tried to reinstall the boot camp partition. But the problem not solved. It failed when I installed boot camp driver(broadcom bluetooth).

So, I installed boot camp driver after deleting bluetooth driver in the setup image. It worked. but I can't use bluetooth devices.

RobjDerby wrote:

Am simply desperate to know how to get my 2015mb retina into windows 10 safe mode.

Seems that no combination of keys will make it happen and all I see here is guesses of F1 F8 shift Option or Command

Your 2015 Mac is a UEFI Boot. Download the ISO from https://www.microsoft.com/en-us/software-download/windows10ISO and copy it to a USB2 Flash drive formatted as MBR/FAT32 and boot from it. Alternatively, use Windows Media Creation Tool to create a bootable USB Flash drive and boot from it. Repair W10 or rollback drivers as you need to.

Hi All,

I have 1 more clarification. Due to 1 of Adobe CC 2015 Win on my 2016MB12 has new updates but can't be updated with error. Also there is another unwanted software but can't be uninstalled. I decided rebuild Bootcamp Win10 (maintains the macOS no change which is 10.12.1).

Yesterday, I deleted and rebuilt BC with the same Win10 1607. Due to it is my 2016MB12, I installed the BC Bluetooth driver as usual. The BC Win10 1607 starts normal after BC drivers were installed. Then applied Windows updates which has rebooted 3 times, everything ok included Bluetooth can be used normally. Re-install MS Office, Adobe and applied all the updates & patches. The BC Win10 still load and run normally, still can use BT mouse and speakers. However, per the last week experiences, not sure when the BT will be temporary fail.

Then I rebuilt BC Win10 1607 on my older 2015MB12 (although it is just rebuilt in 2 weeks ago). Of course I skip NOT installed the BC BT driver. The BC Win10 loads and run normally, but can't use BT mouse and speakers due to didn't install BT driver.

With these extra efforts, I'm now more than 100% ensure the problem is not on Windows side. It is definitely due to the Sierra updates 10.12.1.

I Don't think that works. I updated to 10.12.2 and installed the new drivers and it worked. I then downgraded to 10.12.1 and bootcamp no longer works so it may be more than a driver issue. I then updated back to 10.12.2 and without installing new drivers it worked. So I think the only way is updating. If its any concern the bea feels more stable than 10.12..1 its faster too

The same here.

I used Win10 (1607) under Bootcamp 10.12.1 by having disabled "Intel Serial IO UART Host Controller"

Just updated to macOS Sierra 10.12.2 and booted into Win10, enabled the "Intel Serial IO UART Host Controller" again, and it works.

Seems you don't have to install any new drivers on the Windows side. I assume 10.12.2 fixed the issue in the UEFI (formerly known as BIOS)

I do have Windows automatic updates on and all updates are installed. I am pretty sure the issue is due to power management (ACPI). I started having issues in Sierra 10.12.0 where sometimes Windows would not wake up from sleep and restart instead. Now as soon as 10.12.1 was installed this issue started. agonzalez1010 has the same computer and I believe bootcamp drivers are specific to the Mac so it seems there is a bug for the Early 2015 MacBook in the bootcamp drivers. I reinstalled the bootcamp drivers last night and it did not fix the issue. I also have a 2011 MacBook Air with Windows installed with Sierra 10.12.0 in Boot Camp and it has not ACPI issues, or any issues at all.

I have the same problem. MacBook Retina 12-inch, Mid 2014. I deleted the Bootcamp partition and re-installed Windows 10. The installation worked, but with 2 problems. First, the Bootcamp drivers would not install. Bootcamp setup started to install but then stopped. It didn't lock up, just quit. Second, Windows 10 booted properly the first time, but on the second try it had to run "automatic repair" before booting. Every time since, "automatic repair" has to run before boot. Immediately prior to installing update 10.12.1 Windows booted properly even after updating Windows. It was only after installing 10.12.1 that the problem started.

If you can read carefully. I wrote that I've erase my two MB then installed clean & fresh Sierra and BC Win 10. Both 2015 & 2016 MB were running fine for 2 weeks until I upgrade them to 10.12.1 last night. Then 2015 MB failure boot Win 10 and 2016 MB has no any issue.

Also, I wrote that re-erase and rebuild BC Win 10 on 2015 MB still has the same error. May I know why I have to check older macOS?

As replies earlier, I won't spend my time to rebuild my MB for helping Apple to identify the root cause. Actually, why my 2016 MB doesn't has any problem? Why there are many 2015 MB users like me have the same ACPI.sys problem right after upgraded to 10.12.1?

Thanks

MacBook (Retina, 12-inch, Early 2015)

Before some of this information was available, I deleted my Windows 10 Pro Boot Camp using the assistant (I had only recently created it prior to Sierra, so there was nothing critical yet setup) and then recreated it with 10.12.1 already installed. As such, I can confirm when saying No to the unverified Broadcom driver installation for the Windows Support Software setup, it will proceed without issue. I then created a full system backup with the old built in functionality (leftover of Win7), as well as a System Restore point. I disabled the last remaining unknown device in "Device Manager". I was able to make many repeated restarts/shutdowns while gradually installing software, without a BSOD for ACPI.sys occurring again.

I then created another restore point. Then I restarted into MacOS and proceeded to restore back to 10.12, after doing so I downloaded the "Windows Support Software" folder for that version. I could not find anywhere to download this directly from Apple other than through the Boot Camp Assistant. I then restarted back into Windows, enabled the unknown device and installed the Windows Support Software. This time I granted it permission to install the unverified driver. The system had restarted several times without issue. I again created a restore point.

I have now reinstalled 10.12.1 update and let App Store install the previously troublesome five (Pages, Numbers, Keynote, GarageBand and iMovie) App updates that were stalled out for many users in the last few days. Now restarting into Boot Camp has again produced a BSOD for ACPI.sys, Stop Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

My intention was to attempt to use a restore point to fix the issue. Though this scenario has not played out as I had wanted. It seems another snare has stopped me, there is no touch-pad or keyboard functionality in Auto Repair nor when booting from a Windows 10 USB installation. Unable to interact with Windows at all, I am now at a dead end.

I of course could rebuild from scratch, but that is not feasible for most other users. Also with this instability occurring after a major system update, there is no telling if something of its ilk will not occur again.

Happy to report that once back to 10.12.0 everything is working perfectly. No issues with booting, operation or drivers. My worry is how would we know whether any further Sierra update will adversely affect Bootcamp, unless of course Apple tells us that it has fixed this specific problem? My plan for now is to not update Sierra at all, however should I decide to do so I would make a Time Machine backup prior to installing the update. One thing I do not know is whether or not the Time Machine backup also backs up the Bootcamp side. I presume not as Bootcamp is on a separate partition, but don't know for sure. It seems to me that when using Disk Utility to erase and then restoring from Time Machine backup, you'd select Macintosh HD to restore to, leaving Bootcamp alone, but when I started all this troubleshooting I deleted the Bootcamp partition prior to erasing and reinstalling the Mac OX. So my question is, if you do not delete the Bootcamp partition, use Command R, use Disk Utility to erase and then restore from Time Machine backup, will the Bootcamp partition still be there and accessible? If not, I suppose you could make a Windows backup and use it to restore the Windows side. I haven't done a Windows backup for years, but I assume you can still do it.

I have macbook 2015 12 inch same problem - disable buetooth solve this. But where can i find information wheter Apple fix this ? Because i have second macbook and i want know when i can update to The latest Sierra (now have el capitan)

If the Windows usage is not related to heavy graphics or gaming, switch to a VM engine like VirtualBox, Fusion or Parallels and test Windows with the VM drivers. You can import the Bootcamp partition into the VM engine as a first step.