[SOLVED] SFC has stopped at 74% (Windows Server 2019 essential)

T

tom1982

Member
Joined
Oct 23, 2022
Posts
11
Location
Germany
Hello, hoping for help,😥

SFC:

Code: 
C:\Windows\system32>sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 74 % abgeschlossen.

Der Windows-Ressourcenschutz konnte den angeforderten Vorgang nicht ausführen.

DISM:
Code: 
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.17763.1697

Abbildversion: 10.0.17763.1790

[===========================95.5%=======================   ]
Fehler: 0x800f081f

Die Quelldateien wurden nicht gefunden.
Geben Sie mit der Option "Quelle" den Ort der Dateien an, die zum Wiederherstellen des Features erforderlich sind. Weitere Informationen zum Angeben eines Quellorts finden Sie unter "http://go.microsoft.com/fwlink/?LinkId=243077".

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

SFC-Fix Crash

Creating SFC-Details:
createt scannow.cmd
Code: 
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\sfcdetails.txt"
type "%userprofile%\sfcdetails.txt


Thanks !!!
 

Attachments

Hi and welcome to Sysnative,

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

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

Hi
above fix executed, many Thanks.

C:\Windows\system32>sfc /scannow
make 100% with no errors.

Update Win Crashes.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
with no errors.

C:\Windows\system32>sfc /scannow
second one executed

Update Win Crashes at 100% - Fehlercode: (0x80073712).

New files uploaded.

Thanks for further support!!!
 

Attachments

Hi,

Could you please run the ComponentsScanner again, and upload a copy of the Component Based Servicing hive.

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


Step 2. Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.[/list
 
Last edited:
Hi,

Hmm, the ComponentsScanner is still reporting the same issues, could you please provide a new copy of the COMPONENTS hive as well.
 
Hi,

You have attached the Component Based Servicing hive as a REG file, not as a HIVE file. Please perform Step 2 in post #6 again.
 
Hi,

Thanks, in the meantime I've repaired your COMPONENTS hive.

Step 1. Replace Components Hive Manually.

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config


Step 2. Reboot the systeem and run ComponentsScanner again and post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

Hi,

This looks good, 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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.
 

Attachments

Please attempt to update again, but this time with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system 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.
 
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.
 

Attachments

Hi Maxstar,

update could now be executed successfully and Server is up to date !!!😅👏👏👏

So MANY THANKS.

The cbs.log contains further errors and failed lines.
Are they important or can they be ignored?

Any Idea what was the reason of the errors?
Bad Update?
I know that another software company installed SQL Server 2014 without SP3 in past, but MS says that only works on Server 2019 with SP3.
Which has made many SQL Problems, maybe that was the reason?
Luckily now SQL Server 2019 is installed.

How many time did you spend for me?
 

Attachments

Hi,

You're welcome. Glad to hear the server is up-to-date now! (y)

The CBS log is clean, however, the error messages shown by the CBS log I have also seen on newly installed systems (VM's), so they can be ingnored.
There are several reasons for this kind of corruptions, like forced shutdowns, system crashes, harddrive or memory corruptions. But, it is very difficult to ascertain what the exact cause was.

tom1982 said:
How many time did you spend for me?
Click to expand...

I didn't keep track of the time, but maybe a couple of hours - because I had to install a VM with an specific preview update (KB4601383), from last year to compare different subkeys with the provided hive's.
 
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