BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

After upgrading my MacBook (Retina 12-Inch, Early 2015) to the newest version of MacOS Sierra 10.12.1, my Windows 10 Bootcamp won't boot and throws off an ACPI.SYS error. Since the keyboard and mouse does not work in Recovery Mode, I plugged in a keyboard. I did a "Reset Files" and nothing. Before I wipe out my BootCamp partition and start over I wonder if anyone else encountered this problem after updating from MacOS Sierra 10.12.0...

MacBook, macOS Sierra (10.12.1), Macbook 12-inch (Early 2015)

Posted on Oct 25, 2016 6:45 PM

Reply
213 replies

Nov 27, 2016 6:15 AM in response to RobjDerby

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.

Nov 27, 2016 6:47 AM in response to RobjDerby

RobjDerby wrote:


When you say boot from the USB drive, will it enable me to repair my current bootcamp install ? or get into safe mode to remove the driver or disable the device?

Look for a binary called rstrui.exe . This is the command-line version which starts the System Restore. Please also see https://neosmart.net/wiki/rstrui-exe-not-recognized/ .

$ pwd

/Volumes/BOOTCAMP

$ find . -name rstrui.exe -print

./Windows/System32/rstrui.exe

./Windows/WinSxS/amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10. 0.10586.0_none_d36568405d96315a/rstrui.exe

./Windows/WinSxS/amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10. 0.10586.71_none_cb0e7b3963dcd236/rstrui.exe


Nov 27, 2016 7:18 AM in response to RobjDerby

Okay. When my 2015MB12 failure to boot from Bootcamp after upgraded to 10.12.1. I've tried interrupted the Win10 boot up before display the ACPI.sys error, then Win10 will display the boot option menu instead of load the Win10 normally. I switched to vary Safe mode (i.e. with Command prompt, with Network, etc.) but still hit ACPI.sys error. I tried F10 for More Option then tried System Recover and many other options for try to fix problem.

How to go into Safe Mode while Win10 boot up:

Plug in an USB keyboard (I used Logitech Unify USB nano receiver for wireless keyboard and mouse). Then power on MB12 and hold the alt button, choose Bootcamp drive to boot Win10. When Win10 logo shows, press the power button to power off the MB12. Repeat the above steps again to power on, boot, power off. After couple times of this interruption, Windows will boot to open a boot option menu.


PS. Highly recommended you boot from macOS normally, open the Bootcamp partition, backup all your working files in your Win10 drive before try to repair the Bootcamp Win10. Just in case the repair methods may crash the Bootcamp partition.

Nov 27, 2016 8:16 AM in response to agonzalez1010

In delaying my morning run, I decided to see if anyone had a [real] solution to this wide problem, as I have spent hours trying all variation of reset to a version of this issue. I have a MacAir Mid 2012 , also updated to latest OS update.
I too installed the OS update, maybe about 4 weeks ago, and i didn't see any problems, on either the Sierra 10.12.1 side, or the Bootcamp Windows 10 side. THEN, and nobody that I saw within, mentioned, Windows rolled out a small
Win 10 update! This is when it all went to crap! Now, I have ZERO Bootcamp side, or I should say, I can't even get the 'blue screen of death', just a message to the effect of "windows can't boot, please install a bootable file or drive and press any key". Something to that effect. Now, to preface my experience, I am not an IT professional, but a person who started in the world of DOS, and writing things out in script...and still do, on occasion for control codes in the electronics world where I reside. I am not IT, but more competent in computers that I am certain, that level 1 & level 2 support from any of the firms, we unfortunately have to call, and some level 3. WASTING MY TIME trying to fix this is my business decision as opposed to wasting my time talking to Level 1, then Level 2, then level 3 techs, and I am happy to do this, as I am in tech. I do not though appreciate wasting anytime, where and when I know the fault is due to a third party doing something that effects me. In this case it is APPLE. Bottom line, "Does APPLE have a fix?". Forget this total thread, forget all the back & forth with wiping a system clean & starting from scratch. Apple, what is the solution? Ok, I know someone here will waste more of my time, which I will not spend another minute replying to, so here is what I tried; " 1) I went into Bootcamp setup to check if any evident abnormolies, or comments within Mac side hardware screen (sorry, but exact verbiage of MAC isn't my specialty, PC world is).
2) I tried to FORCE a Bootcamp start. SAME BLACK screen, with seemingly a DOS message to push any key, when "bootable file is connected". 3) I copied my ISO file from Win 7, updates, and windows 10 files, that I had resident in a folder on my MAC desktop to a USB key I had. I verified the validity of the files, by plugging the USB file into my PC.

4) I then repeated steps on Mac Air, with USB key pre-installed, pushed a key, another key, another key, space bar, enter key, and every key I could & the blinking 'dash' after "Push any key", kept blinking.

5) I went back into Mac hardware (& software ) menus to look for any abnormality. Nothing apparent.

6) I wiped USB clean, reformatted it (Lexar 32), and then painfully wasted more time, downloaded a clean ISO file from MS. Repeated all steps, and got same results!

7) I tried to force system (PC side ) into SAFE MODE, some how...impossible!

8) I went the extra step of purchasing a brand new, Samsung 32 USB key, and installed a brand new ISO file, and a file of Win7. Repeated all steps, and ZIP, Nada, Nothing but a black error screen.

So whether this is due to Sierra Update, or Windows 10 update, or a combination of both on Bootcamp, Parallels or other is a moot point. All I know is that on a PC, running Windows you can always roll back to a 'working state'! Not saying MS doesn't have issues with their OS, but time aside, you can always roll backward.

In the binary world of computer language, the answer should be black & white, not a trial by shades of grey. Apple is losing more clients with things like this. Apple, what is the fix ? (Obviously I can reformat the Bootcamp side, reinstall all of my third party programs, passwords & drivers, but to what point ? Waste 3-4 more hours to TRY to see if it works ? NOPE! And the new Mac Pro that i saw yesterday, looking for a new business computer is a joke, so that is not going to happen. What idiot would gamble on running his business (Windows dependent) on a system where not even the factory seems to care about a solution anymore? I have less issues with and immediate results with software engineers writing out Linux code for control than this Mac. APPLE ?

Nov 27, 2016 8:26 AM in response to AudioSavant

AudioSavant wrote:


Apple, what is the solution?

You are talking to fellow Users, not Apple. If you want to talk to Apple, then


1. https://www.apple.com/feedback/

2. https://www.apple.com/contact/

3. https://bugreport.apple.com/problem/viewproblem


Hopefully, binary (10) folks can understand three (11) choices. 😉. I am certain you understand interactions between various components of a computer system.

Nov 27, 2016 9:04 AM in response to AudioSavant

Per my few tests (I'm really busy that can't keep proceed testings and I don't accept to pay my time for fix Apple's fault). I can tell that the Bootcamp fail is 100% due to 10.12.1 updates.

I've reported in few weeks ago, but I will summaries it again :

I have 2015MB12 and 2016MB12. Both were running El Captain and Sierra with Bootcamp Win10 1607 without any problem. Until Apple launched 10.12.1 updates for Sierra, my 2015MB12 has core dump with ACPI.sys error when boot from BC Win10. Luckily that my other 2016MB12 was running fine (until last weekend which Bluebooth was disabled but suddenly the BT works again on Wed til now).

After tried couple of "solutions", I still couldn't fix BC Win10 on 2015MB12. Then I deleted the BC partition and rebuilt Bootcamp. I used the same Win10 1607 ISO file (for El Captain & Sierra 10.12.0 too), but ACPI.sys error again after all the BC drivers installed then restarted Windows. I didn't apply any Windows updates yet ! I've tried rebuilt 3 times but still had the ACPI.sys error, I gaveoff. When I found some members here shared their findings that due to BC BT drivers. I rebuilt the BC on my 2015MB12 again and skip not install the BC BT driver. This time, Windows loaded normally !! I immediately run Windows Updates, still no problem, Follow by installed MS Office and run Windows Updates for Office Updates. Still no any problem even tried reboot many times. I'm using BC Win10 1607 without Bluetooth without any problem for more that 2 weeks.


Conclusions :

OK 2015MB12 El Captiain + Bootcamp Windows 10 1607

OK 2015MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

FAIL 2015MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 (core dump, Win10 can't be loaded)

OK 2015MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 with NO Bluetooth driver or disabled


OK 2016MB12 El Captiain + Bootcamp Windows 10 1607

OK 2016MB12 Sierra 10.12.0 + Bootcamp Windows 10 1607

OK** 2016MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 (sometimes Bluetooth driver will fail)

OK 2016MB12 Sierra 10.12.1 + Bootcamp Windows 10 1607 with NO Bluetooth driver or diabled

Nov 27, 2016 12:24 PM in response to RobjDerby

So - the Windows 10 iso is 4.38gb which is too large (4gb limit) for a FAT32 USB so I can't copy it.

Even if I extract the content the "sources" folder fails to copy and I have to start it again and again.


Why doesn't apple let you uninstall an OS 10.12.1patch ?


This issue is so frustrating, no point in doing a new Bootcamp install as the same issue will just reccur.


I don't even have any real data on the Windows10 partition, just a few apps. Its more the principle of being able to fix it if Im honest.

Nov 27, 2016 12:51 PM in response to RobjDerby

BOOT from USB Win 10 ISO

Is possible? Yes

Does it work - No, cant progress passed the first menu (language) options as have no control over Keyboard & mouse on MB2015Retina

yes, I have a USB Adapter for a USB Keyboard but that USB space is already used for the USB boot key. BRILLIANT


"Keep powering off Windows when the logo shows" someone said

Doesn't work either, Same problem, no different at all. Still in the loop

NO SAFE MODE

Nov 27, 2016 2:52 PM in response to RobjDerby

Run BC Assistant, under Action -> Download.... Get the BC Drivers to USB drive 1. Mount single 64-bit ISO and copy the contents to Usb drive 2. Do not copy the ISO file directly to a USB. Copy the BC drivers to the root of Usb drive 2.


This is your USB W10 installer. If there is a file larger than 4gb, provide the filename which is larger than 4gb.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.