Windows 10 1709 to 1803 Update Failure - 0xc1900101 - 0x30017

CaptainCWA · Oct 21, 2018

Hello, I am having issues with my laptop upgrading Windows 10 Professional 64-bit version 1709 to 1803. While routine monthly Windows 10 updates work fine, I have been unable to get 1803 to apply despite multiple tries. I found some threads in this forum through searches where you were able to help them resolve it, and was hoping you can help me identify what exactly the problem is. I see messages in the update’s log files at the time of the error, but I have no idea what they mean.

I tried using the Update Assistant and then creating a USB thumb drive with the Media Creation Tool, and neither succeeded. However, using the ISO at least gave me an error message when it rolled back.

So when I run the ISO, the main update process starts and runs normally at first. Windows then restarts, and you get the “Working on Updates” screen. When it reaches 30%, it reboots. That’s when I expect the special main section of the Feature Update to start. As soon as Windows tries to start, you get a BSOD as shown in the photo attached that says “STOP CODE: REFERENCE_BY_POINTER”. If you manually try and reboot, Windows tries again, and you either get the BSOD again, or the computer just freezes totally. After a few reboot attempts, Windows reverts the update and goes back to running 1709. When you log in, you get the error screen attached with the code: 0xc1900101 - 0x30017.

The reboot occurred at 2:05 pm. In the log files I see various messages at 14:05, but I have no idea what they mean. I found two other threads on this forum with similar issues:
https://www.sysnative.com/forums/wi...pdate-1703-1803-fails-0xc1900101-0x30017.html
https://www.sysnative.com/forums/windows-update/25636-windows-10-pro-unable-update-1803-a.html

Following the ideas in one of them, I uninstalled Veracrypt. (I use it with thumb drives, not on any internal drive.) I have no other encryption program installed. I also turned off the special caching driver my SSD manufacturer (Crucial) provides to speed up my SSD hard disk. (When you turn that off, it says the driver is removed.) It made no difference. I have seen posts online where people spend days trying to sort this out with trial-and-error driver uninstalls, etc. I don’t have time for that, so I am hoping you guys can give me some specific direction.

I wrote down the time when various steps in the update happened:
Started ISO at 1:48 pm
Main prep phase at 1:49 pm
Restart 2:05 pm. Quickly get to 30%, reboot again.
BSOD 2:05 pm

Thanks.

Sysnative Windows Update · Oct 22, 2018

Hello and welcome!

Please copy your C:\Windows\Minidump folder to Desktop and zip it up. Attach it with your next reply.

Also, do the following:

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.

CaptainCWA · Oct 22, 2018

Thanks.

There is no C:\Windows\Minidump folder. I do have memory dumps enabled, but it does not seem that Windows generated one during the problem.

I cannot run SFC tonight. I will run it tomorrow or Wednesday when I am not in the middle of something important. I can't take a chance tonight of any repair breaking something else. I will post the log as soon I do run it.

Sysnative Windows Update · Oct 22, 2018

No problem. Take your time.

CaptainCWA · Oct 24, 2018

So I ran SFC, and this was what it displayed in the command prompt window:

Microsoft Windows [Version 10.0.16299.665]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>

Attached is the CBS log file. Please let me know if you need any further information from me, and if any of the errors detected are anything I actually need to worry about.

Sysnative Windows Update · Oct 24, 2018

Let's fix these errors:

SFCFix Script

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 file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put
Code:
tags around the log to break up the text.

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.

CaptainCWA · Oct 24, 2018

Thank you for your help so far.

Can you please explain what that utility does exactly? I looked in the ZIP, and it looks like source files for the missing DLLs. Where did those come from?

No offense intended, but I work in IT, so I'm leery of programs and downloads where I'm not fully sure where they came from.

Do you believe that fixing the SFC issues via this utility will cure my update problem, or this just a step along a longer process?

Thanks.

Sysnative Windows Update · Oct 24, 2018

It copies the files I provide (I check the logs to verify which files are missing and then source good copies from the VM).

Unfortunately, I don't have enough information to give you a definite answer if fixing SFC is enough. Upgrade cases can be tricky.

CaptainCWA · Oct 24, 2018

I want to take a full backup before I do this, so I'll try it sometime in the next few days. I'll post the results once done.

Sysnative Windows Update · Oct 24, 2018

No problem. Take your time.

Sysnative Windows Update · Oct 24, 2018

And worry not, SFCFix is 100% safe. I guarantee it.

CaptainCWA · Oct 28, 2018

My apologies, there will be a delay in my completing SFCFix. I had planned to take care of this over this weekend, but I managed to get injured early this weekend, and thus I have some much more important priorities to deal with. Please don't close this thread, I am very much still interested in your help. I will complete my backup and the fix when I can soon.

Sysnative Windows Update · Oct 28, 2018

I'm sorry to hear that. Hope you feel better soon. We don't close threads here. Take your time.

CaptainCWA · Nov 27, 2018

Sorry for the delay of several weeks, but I had to deal with some more immediate personal issues. However, I'm better now, and ready to look at this again.

So since it has been several weeks and I had to apply various software updates since the previous batch of posts, I thought it would be safer to repeat SFC fresh now and have you generate a new, fresh ZIP package for SFCFix. Just in case anything has changed.

Please find attached the new CBS log, and the output shown in the command prompt window.

Thanks.

CaptainCWA · Nov 27, 2018

I just realized the new CBS.txt is significantly smaller this time. Maybe the latest round of updates cleaned up some of it?

Sysnative Windows Update · Nov 27, 2018

There are still corruptions. I'll get you the files tomorrow. Good night.

CaptainCWA · Dec 3, 2018

No rush, but just wanted to remind you this is still outstanding.

Sysnative Windows Update · Dec 3, 2018

I know. Sorry. Had some personal stuff going on :)

Sysnative Windows Update · Dec 3, 2018

As there were BSODs, please do the following:

GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

Download GSmartControl and save it on your Desktop;
Execute gsmartcontrol.exe; Let the install complete and launch the programme.
Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;

CaptainCWA · Dec 3, 2018

It's an SSD. It's also quite new. My Windows installation was migrated over by Acronis TrueImage from a standard hard drive the laptop came with. I have the management utility from the manufacturer, and it shows the drive as working normally, no malfunctions.

Windows 10 1709 to 1803 Update Failure - 0xc1900101 - 0x30017

Member

Attachments

Inactive

Member

Inactive

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Inactive

Inactive

Member

Inactive

Member

Attachments

Member

Inactive

Member

Inactive

Inactive

Member