[SOLVED] Unable to Install Cumulative Update(s) on Windows 10 1803.

Klownicle · Oct 15, 2018

In the process of installing Windows Updates on an 1803 recently setup Dell Laptop. Latest BIOS Installed. PC is UEFI.

First attempted;
•Installation Failure: Windows failed to install the following update with error 0x800F0922: 2018-10 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4462919).

Then attempted to install an update from the update catalog prior to the above failing update and got the same message;
•Installation Failure: Windows failed to install the following update with error 0x800F0922: Update for Windows (KB4346783).

Appears to be related to cumulative update formatted updates, tried Delta updates vs Cumulative as well with the same failure.

Step 1.
> Good
Step 2.
> Good.
Step 3.
> Fail

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.228
[===========================81.9%=============== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>

Step 4.
-> Good.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-15 11:22:53.668
Microsoft Windows 10 Build 17134 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-10-15 11:30:33.130
----------------------EOF-----------------------

Step 5.
> See attached.

Appreciate any help! Thanks!

Sysnative Windows Update · Oct 16, 2018

Hello and welcome!

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 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.

Klownicle · Oct 16, 2018

Thanks, as requested.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-16 18:32:56.045
Microsoft Windows 10 Build 17134 - amd64
Using .txt script file at C:\Users\Amynta\Desktop\SFCFixScript.txt [0]
 

Trace::
Successfully traced component amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f.
    Package_1_for_KB4457146~31bf3856ad364e35~amd64~~10.0.1.0.4457146-1_neutral2
Failed to trace component amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a with return code -3.
Trace:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-10-16 18:32:56.514
Script hash: R/pvUWSbKsPcG6AltBwlm/0dKimuPFSLu8YwD/e6A78=
----------------------EOF-----------------------

Sysnative Windows Update · Oct 17, 2018

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.

Klownicle · Oct 17, 2018

As instructed, see below.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-17 08:48:24.848
Microsoft Windows 10 Build 17134 - amd64
Using .zip script file at C:\Users\Amynta\Desktop\SFCFix.zip [0]
 

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\activex.vch
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashplayerapp.exe
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.dll
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.exe
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.345_none_f2e211134632353c\emodel.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.exe
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\activex.vch to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\activex.vch.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashplayerapp.exe to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashplayerapp.exe.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.dll to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.dll.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.exe to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.exe.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.345_none_f2e211134632353c\emodel.dll to C:\Windows\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.345_none_f2e211134632353c\emodel.dll.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.dll to C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.dll.
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.exe to C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.exe.
Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\activex.vch
Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\activex.vch
Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashplayerapp.exe
Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashplayerapp.exe
Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.dll
Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.dll
Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.exe
Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_17739f61f423837a\flashutil_activex.exe
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.345_none_f2e211134632353c\emodel.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.345_none_f2e211134632353c\emodel.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.exe
Successfully restored permissions on C:\Windows\winsxs\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.17134.285_none_0d1ef50fbfc2c17f\flashutil_activex.exe
PowerCopy:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2018-10-17 08:48:25.841
Script hash: rMfUIIEpCj+ZFe1ZeQpSE6FXpIRLH2lZocTtqQIsKFk=
----------------------EOF-----------------------

Sysnative Windows Update · Oct 17, 2018

Run DISM again and attach CBS.log.

Klownicle · Oct 17, 2018

I want to preface, these updates keep attempting to apply so it sometimes mucks up the process of restarting/booting. Just so you're aware. Not sure if that's a concern. Really appreciate your help. See as requested.

Code:

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.228
[===========================82.4%===============           ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see [url=http://go.microsoft.com/fwlink/?LinkId=243077]Configure a Windows Repair Source | Microsoft Docs[/url].
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>

Sysnative Windows Update · Oct 17, 2018

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.

Klownicle · Oct 17, 2018

https://file.io/3DqtTX

As requested.

Sysnative Windows Update · Oct 17, 2018

Bad link.

Klownicle · Oct 17, 2018

softwaremaniac said:
Bad link.

I see.

2018-10-17_gb2a2zdc | Files.fm. Try that.

Sysnative Windows Update · Oct 17, 2018

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

Klownicle · Oct 17, 2018

As requested.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-17 17:59:30.738
Microsoft Windows 10 Build 17134 - amd64
Using .zip script file at C:\Users\Amynta\Desktop\SFCFix.zip [0]
 

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a\professional-volume-csvlk-5-ul-phn-rtm.xrm-ms
Successfully copied file C:\Users\Amynta\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a\professional-volume-csvlk-5-ul-phn-rtm.xrm-ms to C:\Windows\winsxs\amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a\professional-volume-csvlk-5-ul-phn-rtm.xrm-ms.
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a\professional-volume-csvlk-5-ul-phn-rtm.xrm-ms
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..rofessional-license_31bf3856ad364e35_10.0.17134.254_none_5d8bda4a4bfd796a\professional-volume-csvlk-5-ul-phn-rtm.xrm-ms
PowerCopy:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2018-10-17 17:59:30.972
Script hash: Ns6VwUwWndJ1RiNcnrDK6HERwNCIcVWNX6Jd5bXDLzs=
----------------------EOF-----------------------

Sysnative Windows Update · Oct 17, 2018

Please run DISM again and attach CBS.log.

Klownicle · Oct 17, 2018

So this is good right? Lol

Code:

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.17134.1
Image Version: 10.0.17134.228
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\Windows\system32>

Sysnative Windows Update · Oct 17, 2018

Yup. Try installing updates now, and attach CBS.log if any fail.

Klownicle · Oct 17, 2018

Well Hot DAMN! It worked.

Most impressive, very much so.

So, working in IT, can you provide some insight into the cause and the method of solution for my own curiosity of future issues? I'm guessing it was the .xrm-ms that did it mainly? I realize this is a Microsoft Software Licensing certificate, if this was the cause how could this have been affected?

Secondary to that, can you point me or describe in a crash course of this method of resolution and/or Why the RestoreHealth was failing and Why the WinSXS files restored in this guide were important enough to cause the updates to fail?

How did you recover the files to allow for this fix?

I'm VERY curious about this and to learn so anything you can guide me would be very much appreciated.

Sysnative Windows Update · Oct 17, 2018

Thanks for the kind words. It's very simple actually, DISM was failing because some files were missing, so I checked my machines and found good copies of them, then gave them to you and when all was in place, it worked. Microsoft started releasing Quality Rollups, so it's in a way dependent on some files in order for updates to be successful.

These issues can occur if there's a power loss, if an update is interrupted, etc...

As for learning, we have a private academy here at Sysnative for those interested.

Klownicle · Oct 17, 2018

Absolutely. Although I understand the process to which you went through, going through this with you was like waking up from a quick session in the memory loading chair of the Matrix. Lol.

Is this the "private" academy? https://www.sysnative.com/forums/sysnative-tutorials/ Or is it something else more... private...

Funny enough, I have another PC in the similar standpoint of this Update failing on the .255 version of this windows. So I'll peak around and see if I see similar situations based on our conversation here.

Sysnative Windows Update · Oct 17, 2018

Something more private. If you are interested in potentially being a trainee, please send me a Personal Message.

[SOLVED] Unable to Install Cumulative Update(s) on Windows 10 1803.

Member

Attachments

Inactive

Attachments

Member

Inactive

Attachments

Member

Inactive

Member

Attachments

Inactive

Member

Inactive

Member

Inactive

Attachments

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive