Hi!
Thanks for this amazing tool and forum and offering support for us mere mortals :). I've been seeing update issues since Feb 5th, with error code 0x800700c1. I've tried everything I could find online, including running SFCFix (without custom script) and trying in-place repair upgrade (resulted in Windows 11 Installation Failed).
Windows Resource Protection could not start the repair service.
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.4460
[===========================62.3%==== ]
[===========================84.9%================= ]
[==========================100.0%==========================]
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.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
I'm attaching dism.log to this thread
Loading registry hive from C:\WINDOWS\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 266,986 keys and 297,200 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Found 2 inconsistencies between WinSxS and COMPONENTS hive
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
2 warnings detected
Generating report
The corruption scan completed after 18.79 seconds.
No corruptions were detected, but 2 warnings were found in the COMPONENTS hive.
If you are not experiencing issues with Windows Update, these warnings can likely be ignored.
A report has been saved to C:\Users\chaja\OneDrive\Desktop\ComponentsScanner.txt. Please review this report for more information.
If you require assistance repairing these warnings, seek advice from sysnative.com or your favourite support forum.
Adding generated text to this thread!
Attaching log zip
Thanks in advance for the help!
Thanks for this amazing tool and forum and offering support for us mere mortals :). I've been seeing update issues since Feb 5th, with error code 0x800700c1. I've tried everything I could find online, including running SFCFix (without custom script) and trying in-place repair upgrade (resulted in Windows 11 Installation Failed).
Step #1 - Run SFC Scan
sfc /scannowWindows Resource Protection could not start the repair service.
Step #2 - Run SURT/DISM
Dism /Online /Cleanup-Image /RestoreHealthDeployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.4460
[===========================62.3%==== ]
[===========================84.9%================= ]
[==========================100.0%==========================]
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.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
I'm attaching dism.log to this thread
Step #3 - Run ComponentsScanner
Loading registry hive from C:\WINDOWS\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 266,986 keys and 297,200 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Found 2 inconsistencies between WinSxS and COMPONENTS hive
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
2 warnings detected
Generating report
The corruption scan completed after 18.79 seconds.
No corruptions were detected, but 2 warnings were found in the COMPONENTS hive.
If you are not experiencing issues with Windows Update, these warnings can likely be ignored.
A report has been saved to C:\Users\chaja\OneDrive\Desktop\ComponentsScanner.txt. Please review this report for more information.
If you require assistance repairing these warnings, seek advice from sysnative.com or your favourite support forum.
Adding generated text to this thread!
Step #4 - Export CBS Folder
Attaching log zip
Thanks in advance for the help!