Windows 10 1903 updates won't install anymore

fwinter1 · Jul 28, 2020

I am running Win10 1903 and can't get updates. Through different imaging attempts, I have gotten errors 0x8007301 and 0x80244010.
I tried the series (net stop wuacserv, net stop... etc... rename softwaredistribution, then netstarting) and it didn't help.
Manually downloading different updates didn't help.
SFC /Scannow didn't help
THe Dism /online /cleanup-image /restorehealth didn't do anything
The SFCfix tool errors out with this:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-07-28 16:50:09.540
Microsoft Windows 10 Build 18362 - amd64
Not using a script file.
SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2020-07-28 16:50:15.726
----------------------EOF-----------------------

fwinter1 · Jul 28, 2020

I think it started when I accidently ran this command twice in a row:

install_wim_tweak.exe /o /c Microsoft-Windows-Holographic /r

Additionally, when I looked at the CBS log, I saw something that I think is related to the Holographic features:

(F) Can not identify matching versions for component Microsoft-Windows-Analog-Composition-HologramCompositor, version 10.0.18362.239, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

(F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]

(F) onecore\base\wcp\componentstore\storelayout.cpp(2107): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )

fwinter1 · Aug 4, 2020

I wanted to check in to see about a response? I posted this a week ago, and wanted to make certain something wasn't wrong with it?

Sysnative Windows Update · Aug 4, 2020

Hi!

Please export the following key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

fwinter1 · Aug 4, 2020

Here is the export you requested.
Fred

Sysnative Windows Update · Aug 4, 2020

Nothing was exported.

fwinter1 · Aug 4, 2020

Apologies! Let me try that file again!

fwinter1 · Aug 7, 2020

Just checking in on the status of this. I know you are all busy. Thanks for your efforts!
Fred

fwinter1 · Aug 11, 2020

Hello,
I wanted to know if there was a step I had missed? I tried to make certain I followed all protocols step by step.
Thank you,
Fred

fwinter1 · Aug 14, 2020

Good morning,
I am just checking in for an update. Is there something else I need to be doing?
Thank you,
Fred

fwinter1 · Aug 19, 2020

Good afternoon,
Is there something else I need to be doing at this point?
Fred

Sysnative Windows Update · Aug 19, 2020

Hello! I was on vacation. I will have a look at this today.

fwinter1 · Aug 24, 2020

Good morning,
Is there something else I need to be doing?
Thank you,
Fred Winter

Sysnative Windows Update · Aug 24, 2020

Hi!

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.

fwinter1 · Aug 25, 2020

Here is the Fixlog.txt. Do you want me to attempt to install updates again, or is it not ready for an attempt yet. I don't want to risk having to backtrack because I was premature.
Fred

Sysnative Windows Update · Aug 25, 2020

Not yet.

Please do the following:

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][/CODE] tags around the log to break up the text.

fwinter1 · Aug 25, 2020

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-08-25 11:43:47.014
Microsoft Windows 10 Build 18362 - amd64
Using .zip script file at C:\Users\fwinter\Desktop\SFCFix.zip []


PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_microsoft-windows-c..t-library.resources_31bf3856ad364e35_10.0.18362.1_en-us_36f2d54e146d27c8\credprovhost.dll.mui
Successfully copied file C:\Users\adminfwinter\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-c..t-library.resources_31bf3856ad364e35_10.0.18362.1_en-us_36f2d54e146d27c8\credprovhost.dll.mui to C:\windows\WinSxS\amd64_microsoft-windows-c..t-library.resources_31bf3856ad364e35_10.0.18362.1_en-us_36f2d54e146d27c8\credprovhost.dll.mui.
Successfully restored ownership for C:\windows\WinSxS\amd64_microsoft-windows-c..t-library.resources_31bf3856ad364e35_10.0.18362.1_en-us_36f2d54e146d27c8\credprovhost.dll.mui
Successfully restored permissions on C:\windows\WinSxS\amd64_microsoft-windows-c..t-library.resources_31bf3856ad364e35_10.0.18362.1_en-us_36f2d54e146d27c8\credprovhost.dll.mui
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2020-08-25 11:43:48.593
----------------------EOF-----------------------

Sysnative Windows Update · Aug 25, 2020

Thanks.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

fwinter1 · Aug 25, 2020

It did indeed fail again. I tried to stop the capture process as soon as it failed. Here is the link to the zipped log and CBS files. https://briljent-my.sharepoint.com/...&expiration=2020-09-25T19:54:01.000Z&e=pkNowi
Thanks,
Fred

Sysnative Windows Update · Aug 25, 2020

Hi!

The PML file appears to be corrupt.

Windows 10 1903 updates won't install anymore

Member

Attachments

Member

Member

Inactive

Member

Attachments

Inactive

Member

Attachments

Member

Member

Member

Member

Inactive

Member

Inactive

Attachments

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Inactive