BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

I thought i was a Martians weeks ago. I'm NOT alone.

REgards Wayne

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

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

Regards Wayne

I've got the 2015 Macbook 12" and am suffering the same issue.

Looks to to be MacBook 12" specific.

No backup so can't revert to 10.12.0 .. Apple, please fix this.

I also have the exact same issue which occurred after updating the OS.

I have an early 2015 Macbook.

Have spent hours trying to get Windows to boot.

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.

Thanks vanyue.

Make it quick Apple. That Surface pro's making eyes at me.

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.

You are right. Suggesting the security update will to erroneous conclusions.

Can you check the ACPI Driver Version on MacBook Retina 2015 and 2016?

REgards Wayne

I reported bug 29019510 with Apple in case they have not seen this forum and directed them here.

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.