[SOLVED] Windows update failure ERROR: 0x80073701, Windows 10 Home ver.2009

K

kry3er

Contributor
Joined
Aug 19, 2022
Posts
16
Hello everyone!

A couple of days ago i've had an issue where my OS wouldn't boot and appeared to be stuck at the initial loading screen. After running windows repair tool i have managed to revert the latest windows update and boot into the system with no apparent issues.
Earlier today i have attempted to install "Windows Subsystem for Linux" for my upcoming CS50x final project. After downloading the necessary files and running the wsl --install command in the windows powershell terminal i have received a following error:
An unrecoverable error occurred during installation. Component: 'Virtual Machine Platform' Error Code: 0x80073701 The referenced assembly could not be found.

after checking a few articles online, I have then decided to run the windows update for KB5016616 cumulative update, and stumbled upon exactly the same error code when checking for latest updates. Error Code: 0x80073701

Consequently i tried:
  1. Dism /Online /Cleanup-image /Startcomponentcleanup,
  2. Dism /Online /Cleanup-Image /AnalyzeComponentStore,
  3. sfc /scannow,
  4. flushing the software distribution folder,
  5. running clean boot,
  6. uninstalling and reinstalling the already installed windows updates,
  7. checking CBS.log for "ERROR_SXS_ASSEMBLY_MISSING," and not finding the any such lines in the log,
  8. Dism /Online /Cleanup-Image /ScanHealth,
  9. Dism /Online /Cleanup-Image /RestoreHealth,
  10. creating an ISO with a new windows installation and using it's install.esd as a /SOURCE for DISM commands.
None of the steps mentioned about have yielded any results, suggesting that there must definitely be corrupt, or missing assemblies after the failed windows update event.

  1. sfc /scannow returns no identified integrity violations.
  2. BOTH(!) Dism /Online /Cleanup-Image /RestoreHealth AND Dism /Online /Cleanup-Image /ScanHealth return ERROR:3 "cannot find the path specified"
  3. SFCFix returned a catastrophic failure error and have not finished the checkup at all.
Capture.JPG

all the logs are attached to the post as per "Create topic" manual.

Earlier today i have stumbled upon this forum and saw someone experiencing a very similar issue here:
[SOLVED] - DISM /ScanHealth file not found stopping windows update

I was hoping someone would be able to provide the same level of assistance and save me from having to fresh-install the whole system.

Thank you in advance!!
 

Attachments

A small update: I have downloaded and ran the ComponentsScanner.exe and generated the report. It found one corrupted key value.
Please see attached, and also printed as a screenshot.
Capture.JPG
 

Attachments

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. Examples of services to upload to are Dropbox or OneDrive or WeTransfer and then just provide the link in your reply.
 
Hi! Thank you so much for answering! Please see attached. The file is around 8Mb compressed, so it fits fine.
 

Attachments

Please create a backup of your current COMPONENTS hive and then replace it using the one attached. I've loaded the hive into Regedit and ran it through the ComponentsScanner tool, both appear to load the hive with no problems.
 

Attachments

When i've run your provided COMPONNENTS through ComponentsScanner, it also haven't found any corruptions.
Then i try to run the installation for windows update and, unfortunately, no bueno.
Screenshot of update error:
Capture.JPG

After running "DISM componentcleanup" I get Error: 5. DISM Log attached.Capture1.JPG

DISM /scanhealth returns Error 3:
Capture2.JPG

Corrupt files detected after /scannow. See log and screenshot attached.
Capture3.JPG

I would like to say that i have changed my user's "username" about a month ago. Does windows update or any of these other tools perhaps use the old username's path to access some files that have a different path now? Could it be that some paths just have to be updated? and if so, then how?
 

Attachments

kry3er said:
Does windows update or any of these other tools perhaps use the old username's path to access some files that have a different path now? Could it be that some paths just have to be updated? and if so, then how?
Click to expand...
No, Windows Update is entirely separate to the user profile and any user specific information. It only relies on the %systemroot% and ProgramFiles directories remaining untouched.

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

Please do not run any other commands.
 

Attachments

Thank for quick reply! Please see Fixlog.txt attached.

By the way. I don't see the fixlist.txt file anymore. Does it get automatically deleted?
 

Attachments

Thanks, please follow these instructions:

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. 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.

Afterwards, please attempt to run the following DISM command again:

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth

If it fails, then please provide the latest DISM log, along with, the latest CBS log(s).

kry3er said:
Does it get automatically deleted?
Click to expand...
Yes it does.
 

Attachments

Thanks!

Here's the SFCFix log:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-28 11:58:30.506
Microsoft Windows 10 Build 19044 - amd64
Using .txt script file at C:\Users\Mikhail\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version.
RegistryScript:: directive completed successfully.




Delete::
Failed to delete all files and folders matching pattern C:\Windows\servicing\version\10.0.19041.1790 with result code 2.
Delete:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-08-28 11:58:30.678
Script hash: hmtr0dgxpdSxKadiD1j1zFxesACwgvu2H/b/4+E1ghM=
----------------------EOF-----------------------

DISM /RestoreHealth failed with Error: 3

Capture4.JPG

dism.log attached
CBS.log unchanged since the date of failed Win update event
 

Attachments

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.
 

Attachments

Thank you!
Here's the log:
Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 15-08-2022
Ran by Mikhail (28-08-2022 13:12:29) Run:2
Running from C:\Users\Mikhail\Desktop
Loaded Profiles: Mikhail
Boot Mode: Normal
==============================================

fixlist content:
*****************
RemoveDirectory: C:\Windows\servicing\version\10.0.19041.1790
CMD: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version" /s
*****************

"C:\Windows\servicing\version\10.0.19041.1790" => removed successfully

========= reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version" /s =========


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version
    10.0.19041.1852    REG_EXPAND_SZ    %SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858


========= End of CMD: =========


==== End of Fixlog 13:12:30 ====
 
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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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.

If it has been successfully replaced, then please run the same DISM command again.

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth

If it fails again, then we can investigate further.
 

Attachments

Here's the SFCFix log:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-28 15:42:17.052
Microsoft Windows 10 Build 19044 - amd64
Using .zip script file at C:\Users\Mikhail\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\amd64_installed
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsCore.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsMsg.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiadapter.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiaisupport.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\dpx.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drupdate.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drvstore.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\EdgeAI.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ExtendedSecurityUpdatesAI.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\GlobalInstallOrder.xml
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\msdelta.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\mspatcha.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\poqexec.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ReserveManager.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smiengine.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smipi.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiFileFetcher.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\turbostack.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\updateagent.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\WcmTypes.xsd
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wdscore.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wrpint.dll

Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\amd64_installed to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\amd64_installed.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsCore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsCore.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsMsg.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsMsg.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiadapter.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiadapter.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiaisupport.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiaisupport.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\dpx.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\dpx.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drupdate.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drupdate.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drvstore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drvstore.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\EdgeAI.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\EdgeAI.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ExtendedSecurityUpdatesAI.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ExtendedSecurityUpdatesAI.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\GlobalInstallOrder.xml to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\GlobalInstallOrder.xml.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\msdelta.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\msdelta.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\mspatcha.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\mspatcha.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\poqexec.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\poqexec.exe.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ReserveManager.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ReserveManager.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smiengine.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smiengine.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smipi.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smipi.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiFileFetcher.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiFileFetcher.exe.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\turbostack.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\turbostack.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\updateagent.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\updateagent.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\WcmTypes.xsd to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\WcmTypes.xsd.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wdscore.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wdscore.dll.
Successfully copied file C:\Users\Mikhail\AppData\Local\niemiro\Archive\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wrpint.dll to C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wrpint.dll.

Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\amd64_installed
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\amd64_installed
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsCore.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsCore.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsMsg.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\CbsMsg.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiadapter.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiadapter.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiaisupport.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\cmiaisupport.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\dpx.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\dpx.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drupdate.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drupdate.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drvstore.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\drvstore.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\EdgeAI.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\EdgeAI.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ExtendedSecurityUpdatesAI.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ExtendedSecurityUpdatesAI.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\GlobalInstallOrder.xml
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\GlobalInstallOrder.xml
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\msdelta.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\msdelta.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\mspatcha.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\mspatcha.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\poqexec.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\poqexec.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ReserveManager.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\ReserveManager.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smiengine.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smiengine.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smipi.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\smipi.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiFileFetcher.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiFileFetcher.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\TiWorker.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\turbostack.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\turbostack.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\updateagent.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\updateagent.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\WcmTypes.xsd
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\WcmTypes.xsd
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wcp.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wdscore.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wdscore.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wrpint.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1852_none_7de3b01c7cacf858\wrpint.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 26 datablocks.
Finish time: 2022-08-28 15:42:19.169
Script hash: uVFdhFcL3rpg57JOkh0BWaGWYu7GeHwMOD40VnYmCt0=
----------------------EOF-----------------------

All operations completed successfully, however after running DISM /RestoreHealth, i'm still getting Error: 3. New Dism.log attached.
 

Attachments

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running DISM /Online /Cleanup-Image /RestoreHealth just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

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. Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
Thanks, please find the fix script attached. Afterwards, please reboot the computer and then enter the same DISM command as before:

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth
 

Attachments

Hello! Here's the file link.

In two words, is there hope for me? Or is my future looking bleak? :D

Also, here's the log from after script execution.
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-29 11:11:29.444
Microsoft Windows 10 Build 19044 - amd64
Using .txt script file at C:\Users\Mikhail\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}\InprocServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}\InprocServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\AppID\{7006698d-2974-4091-a424-85dd0b909e23}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InProcServer32.

Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}\InprocServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}\InprocServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\AppID\{7006698d-2974-4091-a424-85dd0b909e23}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InProcServer32.

Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{b31c57ac-4a31-470f-bbee-dba1e5b246be}\InprocServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{3185a766-b338-11e4-a71e-12e3f512a338}\InprocServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\AppID\{7006698d-2974-4091-a424-85dd0b909e23}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{75207391-23F2-4396-85F0-8FDB879ED0ED}\InProcServer32.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 35 datablocks.
Finish time: 2022-08-29 11:11:30.646
Script hash: h0wcSGeczVbGOd1LgQIgIHcwtdZ9RHe2/iJTl3RnWpM=
----------------------EOF-----------------------
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top