BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

unfortunately Windows 10 doesn't allow to enter "safe mode" and it just keeps rebooting.

the faulty driver is the Bluetooth one.

If you finally go for a new Windows installation, when you install the bootcamp drivers, you will experience the same issue, so the workaround is to delete the following folders under the WindowsSupport folder and run the installer again:

\WindowsSupport\AppleBluetoothBroadcom64

\WindowsSupport\BootCamp\Drivers\Broadcom

it worked for me after on a new Windows installation. of course the Bluetooth doesn't work.

The Truth is out there guys!!

Installed update, rebooted into Windows, boot failed.

Shutdown, boot back into Sierra and then reboot again.

This time Windows 10 started successfully.

Now have to run Windows Update and Apple Software Update.

Thanks to all those who attempted to help and put pressure on Apple to fix!!

I think we have the same problem. I have narrow it to Broadcom Bluetooth driver. Try disable it.

I did and i can boot/restart into Windows 10 and use as per normal less the bluetooth capability.

Regards Wayne

vanyue wrote:

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.

Can you check if About the security content of macOS Sierra 10.12.1, Security Update 2016-002 El Capitan, and Security Update 2016-006 Yo… was applied to your Mac?

I did finally manage to boot into normal mode by holding down shift and fn and pressing f8 on the original keyboard repeatedly. Probably ran boot loop for 30 times before getting lucky. I disabled the uart driver but I did not find any bluetooth elements underneath. Infact I've never used bluetooth on this computer and I haven't found a bluetooth driver on the windows. I checked the acpi.sys version which was same as the ones mentioned on the first page. I ran a bluescreenview to check the minidump and there was two red files highlighted.

==================================================

Dump File : 110516-8484-01.dmp

Crash Time : 11/5/2016 3:34:23 PM

Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code : 0x1000007e

Parameter 1 : ffffffff`c0000005

Parameter 2 : fffff800`2a26eed1

Parameter 3 : ffffac80`e0c2c0b8

Parameter 4 : ffffac80`e0c2b8e0

Caused By Driver : pci.sys

Caused By Address : pci.sys+650d

File Description : NT Plug and Play PCI Enumerator

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.14393.0 (rs1_release.160715-1616)

Processor : x64

Crash Address : ACPI.sys+1eed1

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\110516-8484-01.dmp

Processors Count : 4

Major Version : 15

Minor Version : 14393

Dump File Size : 285,100

Dump File Time : 11/5/2016 3:36:17 PM

==================================================

==================================================

Filename : ACPI.sys

Address In Stack : ACPI.sys+74190

From Address : fffff800`2a250000

To Address : fffff800`2a303000

Size : 0x000b3000

Time Stamp : 0x578997a7

Time String : 7/15/2016 10:10:47 PM

Product Name : Microsoft® Windows® Operating System

File Description : ACPI Driver for NT

File Version : 10.0.14393.0 (rs1_release.160715-1616)

Company : Microsoft Corporation

Full Path : C:\WINDOWS\system32\drivers\ACPI.sys

==================================================

==================================================

Filename : pci.sys

Address In Stack : pci.sys+650d

From Address : fffff800`2a3c0000

To Address : fffff800`2a417000

Size : 0x00057000

Time Stamp : 0x5801a742

Time String : 10/14/2016 11:49:22 PM

Product Name : Microsoft® Windows® Operating System

File Description : NT Plug and Play PCI Enumerator

File Version : 10.0.14393.0 (rs1_release.160715-1616)

Company : Microsoft Corporation

Full Path : C:\WINDOWS\system32\drivers\pci.sys

==================================================

Hopefully this info can help someone or apple solve the problem faster.

To those of you stuck in the boot loop, what I ended up doing was creating a recovery disk using a USB thumb drive and another Windows 10 machine. I booted to that on the Mac and from there I was able to get the Mac to boot into safe mode. There are some "Advanced Options" available once you're booted off the USB device. One of those options is to boot to safe mode.

I actually dig that as first step (i.e. loaded the Bootcamp partition), apparently Windows 10 was stuck on an update, you know the ones that download automatically. Loading the Bootcamp image "solved" the updating problem, fixing the Windows installation.

However, I needed to deactivate a floating license in a piece software in Windows in order to be able to use it on my other PC, but the Bootcamp image in VMware got another CPU ID, so the software appeared unlicensed with no way to "return" the license to the vendor. That was very aggravating, since I depend on the software for my freelance work.

Also note that Windows is not activated if loaded as a Bootcamp image (30 days grace). But yeah, this method did solve the Windows *****updating issue.

How I eventually got the Windows boot menu eventually is a bit of mystery, I just kept on hitting combinations of F1/F8-keys and control/shift/Win, I think, until something happened. About 10 reboots. After that I disabled the Bluetooth driver/hardware, returned my software license, and rebooted a couple of times.

Everything seems OK, but I don't trust my Macbook (12 inch/early 2015) with Windows anymore. It used to be my daily driver, but is now pretty useless.

So thanks a heap Apple.

Its quite simple go to the folder bootcamp on Windows and then go to drivers -> Broadcom and you can find it there you can also search for it in file explorer.

I would recommend however you update to mac OS 10.12.2 public beta 4 then redownload the boorcamp drivers from bootcamp assistance as the issue was fixed in the update

vanyue wrote:

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.

Downgrade this 2015 Mac to 10.12.0 and test.

You don't have to reinstall windows. As workaround described in detail in this thread start windows in safe mode and disable the UART enumerator in the Device Manager.

Build a USB Installer manually using Windows ISO or Windows Media Creation Tool from Microsoft and BC Assistant drivers from Apple and boot from it to repair Windows.

I had the same problem go delete the Broadcom bluetgoot drivers and you can boot up but with no Bluetooth

I have the same error and also have an early 2015 MacBook.

Error is normal Windows 10 BSoD screen.

Stop Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

What failed: ACPI.sys

I am able to get back in but each time I have to load the boot camp partition in VMware Fusion. First I get a BSoD and then I can boot to Safe Mode the second time. Then I restart and can boot to regular mode but with no taskbar and start button, still in VMware. Then I close out without shutting down and boot the Mac into real boot camp. Finally I can boot into Windows normally. After I restart the whole process starts again. At school so there is not much more troubleshooting I can do now. Will try to repair the boot camp drivers tonight or tomorrow.

charr328 wrote:

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?

The Security Update is the most likely candidate.

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.

Time Machine does/cannot back up Bootcamp. You cannot erase the whole disk, but just the OS X partition. Even if you erase only the OS X partition, there are common parts in the EFI Partition, depending on your model. It is safer to backup both OSes, your GPT and EFI to ensure the Mac can be returned to a fully functional state.

Imperator87 wrote:

I have macbook 2015 12 inch same problem - disable buetooth solve this. But where can i find information wheter Apple fix this ?

Run Apple Software Update on the Windows side to check.

Because i have second macbook and i want know when i can update to The latest Sierra (now have el capitan)

Stay with El Capitan, otherwise you will end up this problem on a second Mac.