[SOLVED] SFCfix crashes

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

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.
 

Attachments

It seems some files we've just replaced are missing again. Here's the next fix, but after the fix reboot the server and then run DISM.

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

1) Fix
2) Reboot
3) DISM

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.
 

Attachments

Let's try this fix again without a reboot.

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

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.
 

Attachments

I've found the issue with this fix, the system is expecting the uncompressed payload files and I provided the compressed files. So I'll need to create a fix with all the uncompressed files.
 
Thanks, I will consult some colleagues to figure out the quickest way to decompress all these files automatically.
 
Do you have access to the server you used the COMPONENTS hive from as replacement for this server with the issues?
 
Code: 
2023-04-07 14:16:02, Info                  CSI    000000a3 Hashes for file member [l:10]'dnsetw.mof' do not match.
 Expected: {l:32 ml:4096 b:53440e25ab62173d4c7d0a45ad0c0b623cfc0bc7df0d7ccf6f2d736b25941c2d}.
 Actual: {l:32 b:8a5668ac0cf0961f379412c8eef7c87c1d65a19db351df4040041a018e62392a}.
2023-04-07 14:16:02, Info                  CSI    000000a4 Warning: Unable to repair payload file ([l:10]'dnsetw.mof') for component ([l:97 ml:140]'amd64_microsoft-windows-dns-server-etwlogging_31bf3856ad364e35_10.0.17763.1_none_38ea3aa4a0c3f839') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

Perfect, could you please provide a copy of the following folder from that server to check the hash values.

C:\Windows\WinSxS\amd64_microsoft-windows-dns-server-etwlogging_31bf3856ad364e35_10.0.17763.1_none_38ea3aa4a0c3f839
 
Great, that is the expected file. Are you able to run DISM with that server as source with the following command?

Code: 
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess
 
Yes, please. Hopefully it will fix all the payload files in the latest CBS log.
 
Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 
This looks much better... :-)
I would suggest to attempt to update and see what happens...
 
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