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
Question marked as Top-ranking reply

Posted on Oct 31, 2016 6:20 PM

For those of you continuing to struggle with this issue, I wanted to provide you with the specific fix that worked for me, which is a variation on the theme. I did not end up having to reinstall Windows, which would have been a nightmare. Hopefully, Apple addresses this issue soon!


I was finally able to boot into my system after a god-awful number of tries. For some reason, it only occasionally works, with seemingly no rhyme nor reason. I tried variations of holding "option" at boot and selecting the boot camp partition, and booting into safe mode on the rare occasion that I was presented with recovery options. It also seemed like variations of having an external monitor and power hooked up seemed to help it boot – I never did get it to boot into Windows without being “docked.” Anyhow, all speculation… but if you can achieve a boot or safe mode of some kind:


In Windows Device Manager, I attempted to disable the Bluetooth adapter as mentioned in other threads, but it did not do anything – the same problem persisted. After trying many other solutions/restores/etc., I looked at the “devices by connection” view of device manager and noticed that Bluetooth was a child of “Broadcom Serial Bus Driver over UART Bus Enumerator.” I tried disabling that parent device (it is under “System devices”), and lo and behold, everything is rock solid again with multiple reboots.


While I have to live without Bluetooth connectivity, I think this is better than reinstalling the whole setup… hopefully we just have to live with that limitation until Apple issues a real fix and then we can re-enable Bluetooth.

213 replies

Nov 27, 2016 4:43 AM in response to AAminoff

AAminoff wrote:


Diligence? Are you serious? Bootcamp and Win 10 were working fine for the 6 months or so I had it installed until Apple went and broke it with Sierra. It is one thing if Apple officially stops supporting Bootcamp, and another if they break working installs with crappy updates.

Why are you unable to rollback such 'crappy' updates? Apple has already stopped supporting cross-OS readability of HFS+ and NTFS. I think you are missing the point of what I have suggested. The first order of the day should be a stable working system. Non-critical systems are just that. Sierra breaks a lot of stuff, not just this.


If you can, rollback to a stable system, or find an alternative (VM). The AppleHFS broken link is already 3+ months old. Try installing W7/W8.1 on a Sierra+2011 Mac. If you want a list of what is broken in Sierra, there is plenty to go around, whether it is 10.12 or 10.12.x.

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 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

Dec 10, 2016 4:19 PM in response to cmxela

cmxela wrote:


Loner T, thanks for your response, my Mac is a MacBook retina early 2015, I've not found instructions on how to create a USB installer manually. Bootcamp is creating automatically a partition to copy the windows installer.

On Macs which use OSXRESERVED, you can manually create a installer using


1. BC Assistant Action -> Download... to a FAT/MBR-formatted USB Flash drive.

2. Copy the contents of the Windows 10 ISO to the USB drive's root folder.



What I do not understand is that the installer was not having this problem in the 10.12.1, the system was breaking later when installing the drivers. in the 10.12.2 beta the installation breaks just after the installation starts after entering the license code.

You may want to check AutoUnattend.xml to check the order of drivers in 10.12.1 vs 10.12.2 Beta. Strictly, Beta discussions are off-limits on the ASC. 😉

Oct 26, 2016 9:07 AM in response to Loner T

Apparently no way to downgrade once updated. I don't believe it's a Windows driver problem, as I stated, I booted to Windows, installed updates, and rebooted Windows several times with no issues. I then rebooted to Sierra, updated, and when going back to Windows the problem was there. I've had problems in the past with Bootcamp when upgrading the Mac, so am now planning to revert to El Capitan where I never had a problem with Bootcamp.

Oct 26, 2016 9:36 AM in response to agonzalez1010

I'm a full-time student plus studying a lot for the A+ exams so I can't reinstall or downgrade this Mac during Fall term. If a solution can't be found I will have to continue fighting with Windows on the MacBook and/or use my backup MacBook Air. I'm currently only using Windows for my C# Database Programming class.


I reported Boot Camp feedback to Apple last night and may file a bug and point to this thread if I have time.


I will also be buying the new MacBook Pro in the next month so let's hope Apple tested Boot Camp on them and Windows works better...

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.