Win10 1803 update frreezing at 43%, yep another one.....

OK, so I've also got this same -
"0xC1900101 - 0x30018 the installation failed in the FIRST_BOOT phase with an error during SYSPREP operation"

problem and have tried everything suggested and it's still not letting me get past that 43% mark.

I've even uninstalled and/or disabled as much hardware/drivers as possible, and services. Installed some patches (KB4057291, KB4090914 ), you name it. Used the media creation tool to do the upgrade/install from a USB stick. Even configured startup with pretty much everything possible disabled so that it is as bare and clean startup as possible.

[My poota is a DIY build, all listed in my profile. Windows 10 Pro 64-bit.]

I've tried all these:-
https://support.microsoft.com/en-au/...llation-errors
https://support.microsoft.com/en-au/...-update-errors
Done various scans and integrity checks, always comes up good, no issues.
Plenty of space on the C:\ drive which I don't keep any of my personal data on, just windows and programs.

The best progress I've made is that when it gets to 43% it manages to bail out itself instead of just freezing indefinitely.
I'm at a loss and need a definitive way to make it happen.
Hope someone is up for this challenging one!

Use DISM to Repair Windows 10 Image DSIM repaired my SSD allowing 1803 to finally run after several days of trying everything else.

Hi Clint, I ran both CheckHealth and RestoreHealth from Powershell, both came back healthy. Which is good of course but doesn't solve the problem. Thanks though.

"Used the media creation tool to do the upgrade/install from a USB stick. "

Are you trying to UPGRADE from 1709 to 1803 or trying to UPDATE 1803 with latest cumulative ? Hit Win+R type winver then OK and post your current version as a starting point. If using the usb created from MCT, I would disconnect the D SSD so there's no confusion as to where to install Windows.

mrgeek said:

Are you trying to UPGRADE from 1709 to 1803

Yes, currently have 1709 (OS Build 16299.371), trying to upgrade/install 1803 from USB created by MCT.

I'll try your suggestion, but I really don't think it is having any confusion with the D:\ drive. There is no system files on it, and it must be finding the existing installation on the C:\ drive and works on it a fair way before it stalls.

Perform the following steps:

1) Open disk management > widen two columns: status and volume > make sure that the characters in each row are in full view and that no letters are cut off > post an image into the thread

Disk Management - How to Post a Screenshot of

2) Run the BETA log collector and post a zip into this thread:
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)
Use the txt and images in this thread in case there are problems running the beta log collector: (post #5)
DM Log tool problem

3) Download and install: Everything: voidtools

4) Search for each of these and for any found post the files into the link using 7zip to organize the files and one drive or drop box to post into the thread:

setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup
Setupapi.offline.log

1) Disk Management screenshot


(Disk 2 is the USB stick with the 1803 that the MCT created)
I've got other drives but they're all disabled still from when I was trying to do this.

0xC1900101 - 0x30018 is typically an error code when there are problems with drivers.

Information may be available in the beta and panther logs.

2) DM Log
DJR-POOTA (2018-08-12 15 26).zip

It's rather large at over 1MB! My apologies now if it takes a while to sift through it.

[Edit] I'm questioning myself over this. At some point I may have deleted a bunch of logs with CCleaner and what we're looking for may not even be here. So I will use it again to clear everything out, try doing the 1803 upgrade again and hopefully this will leave us with a set of logs that are more relevant, which I'll upload again when done. Bear with me a while......

good morning
how old is your c drive ?