BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

The Bootcamp.xml (and the driver packages) can be downloaded to a USB Flash drive using BC Assistant and using the Acton menu.

For BT, one option you have is to un-pair all BT devices from all pairings, pair it to Windows first, and then pair to OSX second.

Further update on drivers. Bluetooth works. Paired my iMac and Magic Mouse

Looked back at my flash drive support for Sierra 10.12.0 and bootcamp.xml is Product Version 6.0.0136

And thanks Loner, that's how I managed to finally pair the mouse

6.0.6136 is much older than 6.1.6459. This implies the newer drivers packages have issues. It is strange to see BCA behave this way. This is a first that I have seen. 😕

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.

HI vanyue,

i have the MB Retina 2015 and is having exactly the same problem as you. I used up multiple Microsoft Office 2010 Volume License as a result of re-installing Windows Ten. Perhaps it's time to get the NEW Launch MacBook Pro.

MB Retina 2015 Sierra 10.12.1 is problematic with Windows Ten.

REgards Wayne

HI maserluv,

I'm also worry about used up Win10 VL due to reinstalling the Win10. Can we claim Apple due to their OS bug which causes it?

For now, I will leave the new BC partition/Win 10 that I won't touch it anymore until 10.12.2 can resolve it. I can't afford to buy another Win10 license due to erase & rebuild.

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.

I agree. We all have the same issue and it started exactly when 10.12.1 was installed. I'm hoping 10.12.2 will correct it but not sure enough people even install Windows on 2015 MacBooks for Apple to be aware of the issue and fix this. It obviously wasn't discovered during the beta period. I will be using a new MacBook Pro and this will be a backup machine before 10.12.2 come out most likely.

With Microsoft's newfound dedication to hardware I may look to get a Surface Book for Windows use in the future.

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'm afraid that I've told I am an IT man.

If it is due to system bugs, why need trouble me and use my efforts? In my working environment, I only report the problem to vendors. Then they will reproduce the problem in their lab. Just like the recent worldwide crisis, did Samsung send some test plans to customers to ask them help to test out the problem?

As per my IT experiences, I already tested what I should do and what I can do. I believe my tests and reports from another users. It is very clear that 10.12.1 crashes Macbook Retina 12" 2015 model.

Please don't just simply advise downgrade OS. Do you have any roll back procedure? Otherwise, this means we must erase and reinstall the older version OS. Did you consider that our Macbook is not a toy. We purchase it for work, for study, and have thousands & millions of data. Who pay us for backup & restore?

Thanks

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

vanyue wrote:

Please don't just simply advise downgrade OS. Do you have any roll back procedure? Otherwise, this means we must erase and reinstall the older version OS.

Please see macOS Sierra: Revert to a previous macOS version .

Did you consider that our Macbook is not a toy.

It is your choice if you want to upgrade one machine, or many, knowing that you have a problem.

We purchase it for work, for study, and have thousands & millions of data. Who pay us for backup & restore?

Backup and Restore is for your own safety, not the vendor's safety. In the link I posted, there are two which may impact you.

AppleSMC

Available for: macOS Sierra 10.12

Impact: A local user may be able to elevate privileges

Description: A null pointer dereference was addressed through improved locking.

CVE-2016-4678: daybreaker@Minionz working with Trend Micro's Zero Day Initiative

System Boot

Available for: OS X Yosemite 10.10.5, OS X El Capitan 10.11.6, and macOS Sierra 10.12

Impact: A local user may be able to cause an unexpected system termination or arbitrary code execution in the kernel

Description: Multiple input validation issues existed in MIG generated code. These issues were addressed through improved validation.

CVE-2016-4669: Ian Beer of Google Project Zero

It is strange, I'm using Chrome on iPad mini 4, but this commmunity identifies me using "Windows Software".

Anyway, luckily that I've two MBs, I still can use Win10 on 2016 MB. Wish to see 10.12.2 can be released very soon.

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.