[SOLVED] SFC Scan Now and DISM Failure: cbscore.dll

Bean0

Bean0

Member
Joined
May 1, 2025
Posts
7
Hello Sysnative, I have been unable to update my Windows for a long time now. And it looks like I've finally figured out why, I appear to have some system corruption that prevents me from running sfc /scannow as well as dism /online /cleanup-image /restorehealth. I was hoping you guys could help me with it, I have attached the CBS.log output.
2025-05-01 21:51:13, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3
2025-05-01 21:51:13, Info CBS Failed to load Core DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0\\cbscore.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:51:13, Info CBS Failed to initialize CBS class factory. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:51:13, Info CBS Failed to load Core DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0\\cbscore.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:51:13, Info CBS Failed to initialize CBS class factory. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:51:13, Info CBS Failed to create a worker session [HRESULT = 0x800700c1]
2025-05-01 21:51:13, Info CBS Failed to create worker session. [HRESULT = 0x800700c1]
2025-05-01 21:51:13, Info CBS Failed to get worker session. [HRESULT = 0x800700c1]
2025-05-01 21:53:09, Info CBS Failed to load Core DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0\\cbscore.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:53:09, Info CBS Failed to initialize CBS class factory. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:53:09, Info CBS Failed to load Core DLL from path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1371_none_7e1bd7147c8285b0\\cbscore.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:53:09, Info CBS Failed to initialize CBS class factory. [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]
2025-05-01 21:53:09, Info CBS Failed to create a worker session [HRESULT = 0x800700c1]
2025-05-01 21:53:09, Info CBS Failed to create worker session. [HRESULT = 0x800700c1]
Click to expand...
SFC
PS C:\WINDOWS\system32> sfc /scannow

Windows Resource Protection could not start the repair service.
Click to expand...


DISM
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1348


Error: 193

%1 is geen geldige Win32-toepassing.
Click to expand...
Thanks in advance!
 

Attachments

Hi @Bean0,

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

Thank you so much for the reply!

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1348

[===========================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
Click to expand...

I'm not entirely sure everything succeeded, but I'm at least able to run the command now.
 

Attachments

Yes, looks good but in such cases we'll need to apply multiple fixes to resolve all the corruptions.

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1348

[==========================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
Click to expand...
 

Attachments

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! Looks like there's a bit more, I didnt know it wasa this broken 😅

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1348

[==========================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
Click to expand...
 

Attachments

And 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

This one seems to have done the trick, thank you!

C:\WINDOWS\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1348

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
Click to expand...
I have attached the SFCFix.txt and CBS log just to be sure. Should I be able to run the update installer now? Or should more precautions be taken
 

Attachments

This looks better, so please do the following first.

Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
This build Windows 10 21H1 x64 (10.0.19043.1348) is EOL since 2022 so please try to install Windows 10 22H2 using the following tool.

Download the
61c988c2082b1-updateassistent.png
Windows 10 Update Assistant to your desktop.
  • Right-click on Windows10Upgrade9252.exe and select the option: Run as administrator.
  • Press the Update now button, click after the compatibility check on Next.
  • The Update Assistant will now download the latest Feature Update.
  • After verifying the download, the Feature Update will be installed.
  • When this process is ready, click on the Restart now button to complete the installation.
 
Looks like the update succeeded! Had a bit of trouble in the midde with some bluescreens.. saying that the winload.efi was missing and BSD couldn't be found. But I'm pretty sure that was caused by a recent switch I did to UEFI only mode for my new graphics card, since switching back to CSM resolved the blue screens. Anyway, thanks a lot for the help! This can be marked as solved :)
 
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