golden_ADP
New member
- Jan 28, 2025
- 2
Hello Sysnative!
Im really hoping someone here can help me out as my only other option here is to rebuild from scratch. I have been dealing with a Windows Update issue on 3 of my Windows Server 2016 Std servers since the December 2024 CU update (KB5048671). We use N-Able to push updates and that alerted us that patching was failing. The updates will "install", but when the server reboots to finalize and apply the updates it always has to revert due to failure. See below for troubleshooting steps and logs:
Im really hoping someone here can help me out as my only other option here is to rebuild from scratch. I have been dealing with a Windows Update issue on 3 of my Windows Server 2016 Std servers since the December 2024 CU update (KB5048671). We use N-Able to push updates and that alerted us that patching was failing. The updates will "install", but when the server reboots to finalize and apply the updates it always has to revert due to failure. See below for troubleshooting steps and logs:
- Tried in-place upgrade to 2019 and 2022
- Both fail with SAFE_OS error
- 0xC1900101 - 0x20017
- Both fail with SAFE_OS error
- SFC Scan Results:
- C:\Windows\system32>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.
The system file repair changes will take effect after the next reboot. - Rebooted to repair the issues found but still same results
- C:\Windows\system32>sfc /scannow
- DISM Results:
- Never seen this error before and attaching a Windows Server 2016 Std does NOT fix anything
- PS C:\Windows\system32> DISM /Online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.4169
The component store is repairable.
The operation completed successfully.
PS C:\Windows\system32> DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.4169
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
PS C:\Windows\system32> DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.4169
[===========================97.7%======================== ]
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 informat
ion 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
- CBS log attached
- Component Scanner log attached