[SOLVED] Windows server 2016 [1607] fails sfc / dism / updates

stergios99

Member
Joined
Oct 25, 2024
Posts
15
Hello All,
I am having some issue with updates ,sfc and dism .
Update KB5044293 has numerous fails. After the restart that is required , it shows up as failed and again as an available update to start again.
Sfc /scannow fails at 40% , Windows Resource Protection could not perform the requested operation.
Dism /online /cleanup-image /restorehealth finishes to 100% with the error "The source files were not found". 0x800f081f
I saw from another similar post that components folder was needed so i have uploaded those also. Components
Does anyone have an idea what i can check next?
 

Attachments

Hi @stergios99,

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

My dism took forever ...
Attached i have the scfix and CBS.log after my actions.

my error 0x800f081f
 

Attachments

Did you create the previous fix by yourself or have you used a fix from another thread! It's not recommended to use other fixes because it may damage your machine!
Looking at the COMPONENTS hive is it almost 1GB in size, so the WinSxS folder should be pretty big too, and that's the reason why DISM needed so much time to complete.

Do you have a similar server with the same language packs installed, if so I would run the following command with that server as source. Replace "ServerName" with the correct name of that server.
Code:
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess
 
I sadly not have another system available to get a healthy state from there.
I did try the fix by myself :ashamed: (hoping the fix would be easy...) . After that i tried your way
 
Here's the next fix, but do you have recent backups of this server?

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

Recent backups No .
There are the results after the latest sfcfix and dism (dism ended with same error 0x800f081f at 80% )
 

Attachments

Here's the next batch with replacement files.

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

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

Just one component reported this time, so 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

Last message from dism was that the recovery and operation was completed successfully !
Should i try an install and restart ?
 

Attachments

Great, but please run the System File Checker first and post the result and the CBS logs if it fails.
Code:
SFC /Scannow
 
sfc /scannow failed on 40% with message Windows Resource Protection could not perform the requested operation. :(
 
Rich (BB code):
2024-10-29 16:07:42, Info                  CSI    00002be5 [SR] Beginning Verify and Repair transaction
2024-10-29 16:07:43, Error                 CSI    00002be6@2024/10/29:15:07:43.597 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): 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 a minute after as it fails. 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.
 

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

Back
Top