BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

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.

Hi clonalvex,

Thanks a lot for your great efforts. Also, I'm fully understand the painful on error testings and backup & restore (data & restore point).

In this thread, I'm afraid that Apple should have enough reports and customers' testing results for them to fix the problem which they created in the newest 10.12.1. They shouldn't wait or rely on customers to do more testings but they must work on their professional lab tests.

Re you issue on Windows auto recovery. I plug my Logitech Unifying USB receiver then I can use my Logitech wireless keyboard & mouse.

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.

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.

@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. :-)

Thanks mmmike! Nice to know that the downgrade didn't adversely affect Windows 10, but like you, I'll make sure to back up both next time. I hadn't been in the habit of backing up either as there is nothing critical on either. Any important files are always backed up to an external, but it would sure save a lot of time!

Best regards,

David

Hi twl123,

I have both 2015 and 2016 Macbook Retina 12". I can tell this bug only cause 2015 MBR has ACPI.sys error. My 2016 MBR has no issue at all that I still can use Win10.

I really hope to have the bug fixes 10.12.2 can be released soonest.

maserluv wrote:

IIt's NOT True about the Security Update being the candidat. My 2012 iMac does not not have this issue.

Regards Wayne

A 2012 iMac and a 2015/2016 Mac have significant differences in the ACPI layer. Can you check if the security update was applied to the 2012 Mac and what is the ACPI driver version on the 2012 and 2015/2016 Macs? The 2012 Macs are preUEFI Macs and use a BIOS-emulation layer, while 2015/2016 Macs do not.

Comparing two different models will lead to erroneous conclusions.

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.

OMG thank you! I have booted Windows 5 times in a row with no blue screen. I don't use bluetooth with Windows so I should be good until I can get my hands on a new MacBook Pro with Touch Bar 🙂 Well, I'm trying to hold out for a month or so to avoid getting one of the first ones manufactured.

I just ran into the same issue only on my MacPro. I have a windows partition specifically for an MMORPG game which I have never had issues booting into until today after installing the macOS Sierra vs 10.12.1

The Bootcamp icon in startup disk isn't even highlighted for me to utilize. Can't even click on it.

see screen shot.

Has anyone figured out how to get Bootcamp to startup yet? This is ridiculous.

jgiagirl wrote:

The Bootcamp icon in startup disk isn't even highlighted for me to utilize. Can't even click on it.

see screen shot.

Do you see a little lock icon at bottom left of your Startup Disk screen like ...

If yes, can you click on it and enter your password, when prompted and test?