[SOLVED] Windows Server 2016 Standard (VM) -

[HamUser123]

Another Windows Server 2016 Standard VM is having issues installing:
2025-02 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5052006)

1) sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

2) Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

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

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Windows Update Bot]

Hi @HamUser123,

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

 

[PeterJ]

Hello,

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[HamUser123]

I did this fix, but the Window update is pending a reboot, and this server is a weekend reboot server.

I'll reboot server, let update fail&rollback, then retry the SFCFIX.zip, on Saturday (8 mar) this week.

Apparently, someone already rebooted it, but the 2025-02 auto installed again, so it'll most likely need another reboot.

Would any CBS logs help at this point?

 

[HamUser123]

2025-03-08 at 0600AM is when I'll reboot. The 2025-02 culmative update will fail on reboot, and get rolled back out of the system.

At that point, my current plan is to retry your fix, reboot, get new CBS.log files, and hopefully you can give me an all clear or another fix i'll roll out at night.

Please let me know if you want me to do anything different.

 

[PeterJ]

Provide the log from step 1 (SFCFix.txt) and the file C:\Windows\Logs\CBS\cbs.log

 

[HamUser123]

Sorry for taking so long to get back to this.
The updates went through.

Here's the SFCFIX.txt for your records.

I'm not sure the CBS logs are relevant now, they're too old...

Thank you again!

 

[PeterJ]

Sorry for taking so long to get back to this.
The updates went through.

No problem on the delay. Thanks for the feedback.
If the issue is resolved I'll mark this thread as solved.

Take care.