If it is telling you it cannot configure some component, there are things you can try to disable that component or disconnect and external device which might be causing a problem.
In the Bios, you may be able to turn off some things, like Bluetooth, to see if it helps. You don't even need to have the system online if you have the media to install it. If you tell it not to look for updates, that might even help.
If it is rolling back, you should have a $Windows type folder which may be hidden. If you open it and look for a Panther directory, there should be a setupact.log file which was generated during the last failed attempt to install.
You might be able to go through it and follow the percentages and find where it stopped and see if it gives any info regarding the device it had a problem with. The percentages will usually show three separate numbers so you would need to find the correct one which is showing a number just below 51%.
The logs can be long and not that easy to understand. You might start by going to the bottom of the log then doing a search up for the term Fatal.
If you wanted to place the file on your OneDrive and give us a link, we could check it but there may be information which could be personal.
I checked the logs, lots of errors, none "Fatal" . Couldn't find the percentage figures. I am looking to source a backup laptop before i do a clean install. Thank-you for your help. Regards.
Even i tried all the things mentioned above, finally found a fix.
Machine: Dell Inspiron 7520 SE (3rd gen i7)
I also had the problem with updating Windows 10 1803 (last version) to 1809 and the standstill at 52%, then rebooting and restoring the old version. Even when I have not setup any IIS config on my system, I do get the error in the log for the same.
I proceeded like this:
1. Navigate to "c:\windows\system32\" and rename the folder "inetsrv" to "inetsrv.old" [you'll need to change permissions for the folder. Google it if you are not aware of how to]
2. Navigate to "c:\windows\winsxs" and move all files as mask "xxxxxxxxxxxxx-windows-iis-xxxxxxxxxxxx" to another location, preferably another drive [individual folder permissions change needed again]
3. Restart the machine.
4. Using media creation tool, start the installation on the machine.
5. [Grab a HUGE pizza] After the first boot, the installer proceeds up to 52% and appears stuck like before; and then again falls back to 46% and starts building the required files. Depending on the processor, this may take a good part of your evening.
Thank-you for your input. I have now sourced a "back-up" laptop allowing me to do a complete fresh Windows install on the problem laptop, which is now running 1809 without a problem. I then updated my "back-up" laptop to 1809 without any fuss. I have no idea what caused the original problem, but thank-you to all who responded to my SOS :)
speedstep
9 Legend
•
47K Posts
0
March 8th, 2019 09:00
I had no issues using a dual layer USB dvd drive and an 1809 OEM System builder DVD disk.
Clean install had zero issues.
0xC1900101 - 0x30018
The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation
The most likely causes of this error are:
Incompatible antivirus or other security program or utility software
Incompatible driver or hardware
The following hidden log files may offer some insight:
$Windows.~BT\sources\Panther
$Windows.~BT\sources\Rollback
You could try Disabling The Onboard Sound In The Bios or
Press Windows key + X
Click Command Prompt (Admin)
Type the following command:
rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
Hit Enter on your keyboard
Exit command prompt
Restart
Try updating again.
MartynZA
10 Posts
0
March 9th, 2019 07:00
nyc10036
4 Operator
•
5.6K Posts
0
March 9th, 2019 14:00
If you are game for it, do a clean installation instead of an upgrade.
speedstep
9 Legend
•
47K Posts
0
March 11th, 2019 09:00
Clean install of 1809 from DVD overcomes USB issues.
MartynZA
10 Posts
0
March 12th, 2019 07:00
I do not have a Service Request (SR) Number
speedstep
9 Legend
•
47K Posts
0
March 14th, 2019 08:00
You will have to do a clean install from 1809 media.
Saltgrass
4 Operator
•
4.3K Posts
0
March 15th, 2019 07:00
If it is telling you it cannot configure some component, there are things you can try to disable that component or disconnect and external device which might be causing a problem.
In the Bios, you may be able to turn off some things, like Bluetooth, to see if it helps. You don't even need to have the system online if you have the media to install it. If you tell it not to look for updates, that might even help.
If it is rolling back, you should have a $Windows type folder which may be hidden. If you open it and look for a Panther directory, there should be a setupact.log file which was generated during the last failed attempt to install.
You might be able to go through it and follow the percentages and find where it stopped and see if it gives any info regarding the device it had a problem with. The percentages will usually show three separate numbers so you would need to find the correct one which is showing a number just below 51%.
The logs can be long and not that easy to understand. You might start by going to the bottom of the log then doing a search up for the term Fatal.
If you wanted to place the file on your OneDrive and give us a link, we could check it but there may be information which could be personal.
MartynZA
10 Posts
0
March 20th, 2019 00:00
AltafParkar
1 Message
1
May 5th, 2019 09:00
Even i tried all the things mentioned above, finally found a fix.
Machine: Dell Inspiron 7520 SE (3rd gen i7)
I also had the problem with updating Windows 10 1803 (last version) to 1809 and the standstill at 52%, then rebooting and restoring the old version. Even when I have not setup any IIS config on my system, I do get the error in the log for the same.
I proceeded like this:
1. Navigate to "c:\windows\system32\" and rename the folder "inetsrv" to "inetsrv.old" [you'll need to change permissions for the folder. Google it if you are not aware of how to]
2. Navigate to "c:\windows\winsxs" and move all files as mask "xxxxxxxxxxxxx-windows-iis-xxxxxxxxxxxx" to another location, preferably another drive [individual folder permissions change needed again]
3. Restart the machine.
4. Using media creation tool, start the installation on the machine.
5. [Grab a HUGE pizza] After the first boot, the installer proceeds up to 52% and appears stuck like before; and then again falls back to 46% and starts building the required files. Depending on the processor, this may take a good part of your evening.
6. Upgrade to 1809 done.
MartynZA
10 Posts
0
May 7th, 2019 00:00
Thank-you for your input. I have now sourced a "back-up" laptop allowing me to do a complete fresh Windows install on the problem laptop, which is now running 1809 without a problem. I then updated my "back-up" laptop to 1809 without any fuss. I have no idea what caused the original problem, but thank-you to all who responded to my SOS :)
speedstep
9 Legend
•
47K Posts
0
May 24th, 2019 10:00
1809 is now old news.
Current windows is now 1903.