BootCamp fails to start after upgrade to MacOS Sierra 10.12.1

No because i didnt install Bluetooth - so Apple software update will not find it

I migrate Windows (via winclone) to another mac with disabled Bluetooth before and everything Works fine. Maybe i will watch this thread for solution or fix by Apple in higher versions of sierra.

I had the same, but kept rebooting from the BSOD and kept pressing F1, F8, Shift and Alt rapidly and repeatedly in random order until the Boot Options menu appeared (external USB keyboard/macbook early 2015). From there I chose Troubleshoot->Advanced-> Startup Settings and then "Safe Mode" (by pressing the number key 4 on the keyboard). After booting Windows 10 in safe mode, I uninstalled the DRIVER for the "UART enumerator" device in device manager to disable it, and then did a proper reboot into Windows to disable the device completely (cannot be physically disabled in Safe Mode). This worked for me, getting to the Boot options menu was the hardest part and seemed totally random.

This is great, I have been using Windows on my Macbook for work, invested in expensive software and can't fully trust that I will be able to use my (now crippled) system. So now I have to carry an extra PC laptop around wherever I go, just in case. Great QA Apple. Now do something about it!

If the Windows usage is not related to heavy graphics or gaming, switch to a VM engine like VirtualBox, Fusion or Parallels and test Windows with the VM drivers. You can import the Bootcamp partition into the VM engine as a first step.

Nope, cant get any options for restart.

Normal boot - "Your PC Ran into a problem ACPI.sys" etc. We collecting Info for you.

Then "Preparing Automatic Repair" which also leads to ""Your PC Ran into a problem ACPI.sys" etc"

Repeat to infinite loop.

To those of you stuck in the boot loop, what I ended up doing was creating a recovery disk using a USB thumb drive and another Windows 10 machine. I booted to that on the Mac and from there I was able to get the Mac to boot into safe mode. There are some "Advanced Options" available once you're booted off the USB device. One of those options is to boot to safe mode.

Thanks for the tip, I will try that next time!

Same here using a Macbook 2016. Whilst it will boot afterwards, Bluetooth is gone. Any option is futile even using older Bootcamp drivers that previously worked. That is the insight after several Windows installation runs.

I am very much disappointed in Apple and their "Testing" team.

Tested 10.12.2 Beta 3. The problem still exists.

P.S. I have a MacBook 12 Early 2016 — Windows boots fine but I can't use bluetooth. I think the issue crashes 2015 MacBook and disable bluetooth on 2016 MacBook according to earlier replies.

If anyone could report this problem to Apple Plz do so!!!

I actually dig that as first step (i.e. loaded the Bootcamp partition), apparently Windows 10 was stuck on an update, you know the ones that download automatically. Loading the Bootcamp image "solved" the updating problem, fixing the Windows installation.

However, I needed to deactivate a floating license in a piece software in Windows in order to be able to use it on my other PC, but the Bootcamp image in VMware got another CPU ID, so the software appeared unlicensed with no way to "return" the license to the vendor. That was very aggravating, since I depend on the software for my freelance work.

Also note that Windows is not activated if loaded as a Bootcamp image (30 days grace). But yeah, this method did solve the Windows *****updating issue.

How I eventually got the Windows boot menu eventually is a bit of mystery, I just kept on hitting combinations of F1/F8-keys and control/shift/Win, I think, until something happened. About 10 reboots. After that I disabled the Bluetooth driver/hardware, returned my software license, and rebooted a couple of times.

Everything seems OK, but I don't trust my Macbook (12 inch/early 2015) with Windows anymore. It used to be my daily driver, but is now pretty useless.

So thanks a heap Apple.

AAminoff wrote:

So thanks a heap Apple.

I wish Apple would stop following a Wall Street Product Calendar and rigorously test stuff before putting updates/upgrades out. Can you fall back to El Capitan?

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.

Time Machine can be left unattended for a restore, if so desired, but I understand the need for time and energy.

Yes, Time Machine is great, but since I rely heavily on Dropbox for syncing work files accross platforms I can not risk restoring a backup that potentially could mess things up on the other machines. I have serious trust issues after this Bootcamp problem. Will probably upgrade to macbook pro and just go back to VMware.

Apple please fix this ASAP!!!!!!!!!!

cyberprashant wrote:

Apple please fix this ASAP!!!!!!!!!!

Call Apple Technical Support. Posting this on ASC will not help you much.