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 22, 2016 3:53 AM in response to Loner T

Yes and no. No because I am not prepared to spend basically a full working day doing a full reinstall, resyncing etc. I simply do not have the time for this, which ironically was one of the reasons why I again got a Macbook. I have been running Windows in VMware on my old macbook pro for years without any issues, but decided to get the 12 inch macbook because of the low weight/screen/battery life and just run Windows 10 natively. Everything was working perfectly until the Sierra update came along.

Nov 22, 2016 8:21 PM in response to speakElvish

You can try the WidComm stack (https://www.broadcom.com/support/bluetooth) , which is a generic BT stack. Do not download it from anywhere else, because there are many unauthorized and suspicious variants floating around at different web sites. Create a Windows System Restore point, before you install anything on your Mac. If possible, backup OS X using Time Machine (or any other tool of your choice).

Nov 22, 2016 8:22 PM in response to speakElvish

Thanks speakElvish,

Nice to know you've tested beta 3, but sad to know still not fix the problem.

Back to few weeks ago, I reported that my 2015MB12 was failed Bootcamp but my 2016MB12 was running fine. However, since last weekend, I found my 2016MB12 also has no Bluetooth which disabled. It is strange that the Bluetooth is back in these 2 days.


The Sierra 10.12.1 is buggy on both 2015 & 2016 of Macbook 12" Retina.

Nov 27, 2016 12:51 AM in response to lsauerMac

Full agreed with you! LonerT here keeps advise this and that, but never has a solution provided. Some users in this thread and me have told that we have no time and worry about data lost, and we also have told busy & don't have time. This guy still keep advise use Time Machine then test & try & test & try rebuild Bootcamp or try VM.

This guy doesn't has risk sense and never consider our painful & technical skill (has advise different methods to test but no solid solution). I'm very sure he didn't test to reproduce our problem, at least I couldn't find any of his reply shows he has the same scenario and has worked out solution........

In this case, with more and more users' reports, it is now very sure due to the Sierra updates 10.12.1 which causes 2015MB12 can't load Bootcamp Win10 and causes 2016MB12 has Bluetooth failure problem. Why Bootcamp Windows 10 in other MB & iMac models are no problem? It is definitely due to the 10.12.1 updates made by Apple. However, this guy still advise everyone (newer reporters too) to test and to try.....

Nov 27, 2016 3:10 AM in response to lsauerMac

lsauerMac wrote:


you are not helping at all within this forum thread - concerning the MacBook 12".

Nothing taken personally, but knowing the history of W10 and newer Macs, this discussion is not a surprise. I have W7/W8.1 on 2012/2013 Macs which are stable and running without any issues. I do not use Sierra either.


Intel and AMD GPUs on Macs do not function very well under BC, and Broadcom is now a late comer to the same party. See Touch-bar MacBook Pro bootcamp Issues as an example.


Consumers who buy Macs without adequate diligence and testing should be forewarned that running Windows is a fringe benefit, not the main show. I am more than happy to wait for the next nVidia MBP with touch-bar.

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

AAminoff wrote:


Hardly bleeding edge, Bootcamp technology. It has been around for a while.

The name Bootcamp has been around, but the GPU/WiFi/Ethernet drivers are specific to each model, and have no relationship to previous versions/releases. Unless Apple sees a significant revenue dependency on this combination, it is unlikely to see any further attention from the Engineering side of Apple.

Nov 27, 2016 4:56 AM in response to lsauerMac

I did see your response which was removed. I understand the pain that this issue causes. My recommendation is to protect yourself and maintain a functional environment. There should be adequate backups and the ability to rollback and recover a system to a previously stable state based on your definition of stability. It is in your interest.

Nov 27, 2016 5:20 AM in response to Loner T

Thanks for your reply. Do you forget what I've reminded you? I'm an IT man. I can tell you more, I worked in IT field for more than 20 years and now is a Team Lead or say an Operation Manager in my company. You are no need again and again to show off what technical knowledge you know.

I also have said couple times, especially has been replied you. If this problem (bugs) is created by Apple, why I need waste my time to keep doing tests? Why not the creator to test and reproduce the problem in their lab (they should have hundreds of development machines, but we have only 1 or 2 and cannot be rebuilt always). Please don't keep actively reply us for more points. You show that higher level member here is not that helpful. THANK YOU.

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.