[SOLVED] Windows Server 2019 - KB5040430 - error 0x80070057

Updating:
sfc /scannow - 98%

dism /online /cleanup-image /restorehealth - 100%
Error: 0x800f0950

New logs files in attachment
 

Attachments

Hi and welcome to Sysnative,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.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.
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

Hi!
I have completed your steps 1-2, log files attached
Step 2: Recovery Successful

Code:
C :\Windows\Logs\CBS > sfc/scannow
System scan started. This process may take some time. Starting scan phase of system scan.
98% verification completed.


Windows Resource Protection cannot perform the requested operation.
 

Attachments

Rich (BB code):
2024-08-01 17:51:38, Error                 CSI    000061b3@2024/8/1:10:51:38.896 (F) onecore\base\wcp\componentstore\deltastore.cpp(3065): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed
[gle=0x80004005]

Please run the System File Checker again with Process Monitor running.

Step1. Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the System File Checker just like you have in the past.
3. Stop Process Monitor two minutes after SFC failed to be sure everything is logged.. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.

Step 2. Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
No problem at all, every other file sharing site is fine for me.

Here's the next fix.

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 System File Checker again with Process Monitor running. If it fails send me the latest CBS logs and the ProcMon trace file.
Code:
SFC /Scannow
 

Attachments

Code:
C:\Windows\Logs\CBS>sfc /scannow
System scan started. This process may take some time. Starting scan phase of system scan.
98% verification completed.


Windows Resource Protection cannot perform the requested operation.
 

Attachments

Please share also the trace file of Process Monitor as requested after running the System File Checker [Step 2.]..
 
Here's the next fix for another corrupted component.

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 System File Checker again with Process Monitor running. If it fails send me the latest CBS logs and the ProcMon trace file.
Code:
SFC /Scannow
 

Attachments

Hi,

Here's the next fix.

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 System File Checker again with Process Monitor running. If it fails post the latest CBS logs and the ProcMon trace file.
Code:
SFC /Scannow
 

Attachments

Hi,

Code:
C:\Windows\Logs\CBS>sfc /scannow
System scan started. This process may take some time. Starting scan phase of system scan.
98% verification completed.


Windows Resource Protection cannot perform the requested operation.
 

Attachments

Still the same issue, so please provide the latest Process Monitor trace.
 

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

Back
Top