[SOLVED] Win11 23H2 update fails with 0x800700c1 error

chajath

New member
Joined
Feb 9, 2025
Posts
4
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).

Step #1 - Run SFC Scan​

sfc /scannow

Windows Resource Protection could not start the repair service.

Step #2 - Run SURT/DISM​

Dism /Online /Cleanup-Image /RestoreHealth

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

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!
 

Attachments

Hi @chajath,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi and welcome to Sysnative,

Step 1. Download
67139f7e69a58-SFCFix-ico.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thanks! Unfortunately DISM run failed:

Code:
C:\Windows\System32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.4460

[===========================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 https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I'm attaching logs as directed.
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thanks! DISM took a lot longer to run, but ended with the same error message:

Code:
C:\Windows\System32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.4460

[===========================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 https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Windows\System32>

I'm attaching new logs. Thanks!
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

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

Back
Top