[SOLVED] Windows Server 2019 - 0x800703F1 - sfc dies at 30%

R

rawwrr

Active member
Joined
Aug 2, 2023
Posts
26
Hi,

I have a Windows Server 2019 on which I'm struggling to install Windows Updates. It gives an error 0x800703F1 on some updates. When some others successfully install in Windows, the changes are reverted during the reboot phase.

Initially, both "Dism.exe /online /Cleanup-Image /RestoreHealth" and "Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase" failed saying ERROR_BADDB. The timestamp on the COMPONENTS file in "C:\windows\system32\config" dated back to 2022.

I ran ComponentsScanner.exe and it did seem to repair the database.

VV2VXb1Km2.png

31IFcTKXzY.png

I did also recover some (200+) registry files from a working COMPONENTS hive I took from an other server (from this thread)

After that, both DISM commands above were working successfully, however I still had the same issues installing the updates. I tried "sfc /scannow" which stops at 30%. This is where I'm currently stuck.

Attached is the CBS folder as well as the ComponentsScanner.txt which reports no errors.
 

Attachments

I know you guys are busy. Just bumping my post to see if anyone's available to help.
 
Rich (BB code): 
2023-08-02 15:49:24, Error                 CSI    00001a4e@2023/8/2:19:49:24.747 (F) onecore\base\wcp\componentstore\deltastore.cpp(3065): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed
[gle=0x80004005]

Hi and welcome to Sysnative,

Note and warning: don't use any fixes from other threads, this may cause more irreparable issues on your system!

Please run SFC /Scannow again with Process Monitor running to see what happens.

Step#1 - 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 as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



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 as well as a new copy of the CBS logs.
 
The WeTransfer link is the same file you have attached, could you please provide a new link for the Process Monitor trace.
 
This is a copy of the CBS folder again, not the *.PML file of Process Monitor.
 
Rich (BB code): 
5:16:58.6297377 PM    TiWorker.exe    16720    RegQueryValue    HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-b..-bcdtemplate-server_31bf3856ad364e35_10.0.17763.1_none_f3c0a9d7854d4403\f!bcd-template    SUCCESS    Type: REG_DWORD, Length: 4, Data: 33

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.
 
Step 1. Download
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.
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 and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

Please run SFC /Scannow again with Process Monitor running and attach the *.PML file.
 
Here's the next fix:

Step 1. Download
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.
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 SFC /Scannow again with Process Monitor running and provide the *.PML trace in your next reply.
Code: 
SFC /Scannow
 

Attachments

Hi,

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 SFC /Scannow again with Process Monitor running and provide the *.PML trace in your next reply.
Code: 
SFC /Scannow
 

Attachments

That's quite complicated to describe in a single post, but I look at the PML file when the trace is stopped and check the latest registry keys, including some set of filters each time. Then I compare those keys in your COMPONENTS hive with a similar installation on a VM.

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.
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 SFC /Scannow again with Process Monitor running and provide the *.PML trace in your next reply.
Code: 
SFC /Scannow
 

Attachments

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