Windows 10 Pro v1709 won't update to v1903, error 0xc1900101

Slammer · Jan 4, 2020

Win 10 Pro v1709 won't update to v1903, error 0xc1900101. Have tried multiple times & disconnected all non-essential USB peripherals. No corruption errors. Please see attached CBS.zip & advise.

Thanks in advance!
~Slammer

Sysnative Windows Update · Jan 4, 2020

Hello and welcome!

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

Slammer · Jan 4, 2020

Attached.

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

Please uninstall the following:

µTorrent
Cisco AnyConnect Secure Mobility Client
ESET Security
HP Update
I.R.I.S. OCR

Afterwards, reboot and run fresh FRST scan for me.

I would recommend using this to remove ESET: Uninstall ESET manually using the ESET uninstaller tool

Slammer · Jan 4, 2020

Completed, without ESET manual uninstaller, for now. Please see attached.

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
Accept the License Agreement
Download the ISO file to your desktop.
Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.

Slammer · Jan 4, 2020

Unfortunately it still hangs after 1st reboot on windows logo. A reset rolls back to v1709 again, but this time there's an error post login:

"0xc1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation"

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

SFCFixScript.txt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

Slammer · Jan 4, 2020

softwaremaniac said:
Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.

Accept the License Agreement

Download the ISO file to your desktop.

Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.

Slammer · Jan 4, 2020

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-04 20:24:42.071
Microsoft Windows 10 Build 16299 - amd64
Using .txt script file at C:\Users\Sam\Desktop\SFCFixScript.txt [0]



FileScan::
WARNING: There may be further unlisted copies of some of these files on the system.

[0: 1] C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log
File is untraceable.
 Found: HnMdSsDVkFXxQxtNJouH1NSzXkzVN72Noa7RaaNAmJ0=
 Version number not available.
Trace not available.



[1: 1] C:\$WINDOWS.~BT\Sources\Rollback\setupact.log
File is untraceable.
 Found: wnd3nOqJ/iGz1toOil0CG9ead7j/aZYDkH5TnQV8wTU=
 Version number not available.
Trace not available.



[2: 1] C:\Windows\Panther\NewOs\Panther\setupact.log
File is untraceable.
 Found: 1F43RGzpPhFA03uQ69YfLvTHnWX2zd1yy7DgzLJAfpE=
 Version number not available.
Trace not available.



[3: 1] C:\Windows\Panther\NewOs\Panther\setuperr.log
File is untraceable.
 Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
 Version number not available.
Trace not available.



[4: 1] C:\Windows\setuperr.log
File is untraceable.
 Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-01-04 20:24:46.579
Script hash: dGVyH1knFwCO/A9Xqhjqle2YgKUshOPnySE9GOhfapE=
----------------------EOF-----------------------

Sysnative Windows Update · Jan 4, 2020

Please zip up the listed files and attach them to your next post.

Slammer · Jan 4, 2020

Zip archive names are log file path names (roughly).

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Right-click on the Start button and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Slammer · Jan 4, 2020

Attached...

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Slammer · Jan 4, 2020

Attached...

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

Please do the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Slammer · Jan 4, 2020

Attached...

Thanks,
~Slammer

Sysnative Windows Update · Jan 4, 2020

Thank you. It appears there is a new BIOS update available for your motherboard: Motherboard: ASUSTeK Computer INC. P6T

Please flash your BIOS to the latest version, but be careful, because you can damage your system if you do this incorrectly.

P6T BIOS & FIRMWARE | Motherboards | ASUS Global

Let me know when done.

Slammer · Jan 4, 2020

OK, BIOS updated. Shall I try to upgrade from Win ISO again now?

Thanks,
~Slammer

Windows 10 Pro v1709 won't update to v1903, error 0xc1900101

Member

Attachments

Inactive

Member

Attachments

Inactive

Member

Attachments

Inactive

Member

Inactive

Attachments

Member

Member

Inactive

Member

Attachments

Inactive

Member

Attachments

Inactive

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Member