Windows 10 Creators update fails

piku9000 wrote:

... regular users may be better off with the Windows version before Anniversary Edition, they would still have HFS+ read-only driver support to see all their hard drives.

You can also use Re: Windows 10 Anniversary + Boot Camp = no longer mounting Mac partition as a workaround for the HFS+ visibility. CS volumes are still not supported.

See my post:

Re: windows 10 creator update

Look this problem is only for mac mini 2014 hardware - intel drivers not work and got computer to BSOD.

But Anniversary update work fin on my mini, only problems is for Creator update.

I managed to get my MacBook working with Boot Camp. I was getting the same issue and I realized that it was a problem with the Boot Camp drivers themselves, but then I had issues with installing these drivers AFTER installing the update... it was a lot of trial and error, but this is what I did:

1. Download the latest Boot Camp drivers with the Boot Camp Assistant and put them in a USB drive.
2. Boot back on Windows and uninstall all of the Boot Camp drivers (You can leave the actual Boot Camp control panel)
3. Reboot on Windows and apply the Windows 10 Creators Update (Mine failed the first time I installed it, but then it worked flawlessly the second time around, not sure why)
4. Once the installation is complete, enable the System Restore function for your computer/installation hard drive for your computer and create one immediately.
5. Pop in the USB drive with the Boot Camp assistant and INSTALL THEM MANUALLY, ONE BY ONE. (This is the problem, there is a driver that causes failure on Windows and the reason why the installation keeps failing)
6. Once the required drivers have been installed, there should be no problems afterwards

PS: As far as I could troubleshoot, I was unable to identify the culprit driver that makes the installation fail. If you install a driver, restart your computer and find that it is stuck in a boot loop, get into the Windows boot menu and roll back to the most recent System Restore function.

PS2: I was able to get into the Windows boot menu by holding Control+Option+P+R while turning the computer on (I know this is not the correct sequence, because it looks like the Reset PRAM function, but it worked every time like a charm)

PS3: I can remember some of the drivers that worked:

• Apple Null Driver (Useful for the Thunderbolt ethernet adapters)
• Bluetooth drivers (both from $WinPEDriver$ folder and the BootCamp driver folder
• All of "Apple" folder drivers in the BootCamp folder, except for BCDriverMerge
• Broadcom drivers (Bluetooth, Card Reader, ComController, Ethernet)
• Cirrus Audio (I only installed CirrusAudioCS4208x64.exe)
• Intel drivers

For the rest of the drivers, I let Windows take care of it (including the graphic drivers)

It took me a couple days to troubleshoot completely and to figure out which drivers worked/didn't work. Let me know if it works!

Cheers

piku9000 wrote:

I managed to get my MacBook working with Boot Camp. I was getting the same issue and I realized that it was a problem with the Boot Camp drivers themselves, but then I had issues with installing these drivers AFTER installing the update... it was a lot of trial and error, but this is what I did:

1. Download the latest Boot Camp drivers with the Boot Camp Assistant and put them in a USB drive.
2. Boot back on Windows and uninstall all of the Boot Camp drivers (You can leave the actual Boot Camp control panel)
3. Reboot on Windows and apply the Windows 10 Creators Update (Mine failed the first time I installed it, but then it worked flawlessly the second time around, not sure why)
4. Once the installation is complete, enable the System Restore function for your computer/installation hard drive for your computer and create one immediately.
5. Pop in the USB drive with the Boot Camp assistant and INSTALL THEM MANUALLY, ONE BY ONE. (This is the problem, there is a driver that causes failure on Windows and the reason why the installation keeps failing)
6. Once the required drivers have been installed, there should be no problems afterwards

Removing BC drivers in step 2 is SysPrep (or Generalization of Windows). The Creators Update fails to do this as shown in the error message.

PS3: I can remember some of the drivers that worked:

• Apple Null Driver (Useful for the Thunderbolt ethernet adapters)
• Bluetooth drivers (both from $WinPEDriver$ folder and the BootCamp driver folder
• All of "Apple" folder drivers in the BootCamp folder, except for BCDriverMerge
• Broadcom drivers (Bluetooth, Card Reader, ComController, Ethernet)
• Cirrus Audio (I only installed CirrusAudioCS4208x64.exe)
• Intel drivers

For the rest of the drivers, I let Windows take care of it (including the graphic drivers)

1. The set of drivers varies by each Mac model, with some common ones.

2. BCDriverMerge.exe is not a driver, but program to merge drivers, which is part of the grand-fathering of drivers.

It took me a couple days to troubleshoot completely and to figure out which drivers worked/didn't work.

Very few users can do this trial/error and spend couple of days. The failure of automation in the Creators Update should be addressed by M$.

Glad to see that you managed to make it work.

I have the same issue as well! I always get this error message:

Error 0xC1900101 - 0x30018

The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation

Tried everything available online to resolve it but ended up with a total failure 😟

It can only be applied to the 1607 release. I assume you have that in place. The other link was to illustrate that an upgrade does work properly. If your progress bar is hung at 32% (or some other number), unless the logs can be analyzed, it is difficult to diagnose.

Hello.

Same issue here.

Mac Mini with OS X Sierra and BootCamp with MS Win 10 x64 Anniversary Update.

During the upgrade to the Creators Update, it fails and reverts back to Anniversary Update.

Error in the log =

Error 0xC1900101 - 0x30018

The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation

Regards.

Alessandro

I have i mac mini from 2014. And i solved this problem by uninstalling the intel iris graphics drivers. Then start the windows update. This worked but now i have to use windows basic display drivers. Everytime i try to install bootcamps display dirvers my computer crashes. So i think apple needs to update the GPU drivers.

Taaannn wrote:

Everytime i try to install bootcamps display dirvers my computer crashes. So i think apple needs to update the GPU drivers.

The Creators Update should grandfather already installed drivers or provide a warning and rollback the update. This 'abort' error is bad user experience with a M$ product. 😉

I would not blame it on Microsoft, but on Apple, because the driver support for the Creators update is bad - it's not like Microsoft has to cater to Apple devices exclusively... As long as there are supported drivers, then Windows will work correctly, right?

While troubleshooting this issue I found that drivers re-applied / forced to load / etc around 32%, and that's where the installation fails. Error 0xC1900101 - 0x30018 is related to driver errors on installation (https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/err or-when-upgrading-to-windows-10-0xc19001…)

I also agree that the drivers to be used vary from model to model, it requires a lot of tinkering and knowledge of your mac to be installing them manually... but then again, I am running windows in UEFI mode, and not Boot Camp haha...

Also, tried to keep technicalities at a minimum (not trying to explain driver merging and etc.)

Lastly, yes, a lot of people won't know how to proceed on this as this is very technical, but it's no excuse. I think ultimately Apple needs to provide better support for their drivers (e.g. Fan control is "lacking" for a better word, two-finger right click on trackpad only works after login, inconsistent audio/microphone switch from optical/headphones to regular speakers and vice versa, terrible keyboard layout implementation, etc... I could really keep going...) if they are going to promote Boot Camp as a worthwhile feature.

Really hoping this can help anyone with the Creators Update!

From the thread, I have asked folks to look for logs. The link you posted mentions the following locations, which can help identify specific drivers/software in general. The link started in 2015, but Creators Update is an April 2017 release, so the issues have existed since Anniversary Update and are not new.

$Windows.~BT\sources\Panther
$Windows.~BT\sources\Rollback

UEFI or BIOS still requires Apple drivers to be installed for appropriate support of Apple hardware.

There is no explanation from anyone at Microsoft on why a SysPrep is needed for a Windows Update. There is no such equivalent when you update OS X to Sierra on the Macs. Articles like Do NOT install Windows 10 Creators update download, Microsoft warns some users do not seem to help any user.

Apple's driver support on the Windows side seems to be a marketing/sales decision to keep some disparity and differentiation. Some vendors do a better job of uniform driver support than others - case in point is nVidia vs AMD on Macs.

For future readers, I suggest manually running a full backup of Windows, a manual SysPrep, followed by a Creators Update, and re-installation of BC drivers, instead of relying on the CU to run a SysPrep properly. Older Macs (2012-2014) which support W10 should be carefully updated with CU.

Hello.

Same issue at 32%.

I have updated the Intel graphic card drivers with the latest version, but the upgrade fails again.

On the German version of the Apple Forum, I have read that this problem is probably only with Mac Mini and not with MacBook.

Thank you.

Regards.

Alessandro