Windows Server 2016 2025-03 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5053594). Roll's back

Please do following.

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
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

FRST Scan:
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Restart the machine.
Try the upgrade again and report the result.
 
Right-click on the Start button and click Run.
Typ POWERSHELL in the input field, then click OK.
A blue window appears.
Typ in the blue window Get-WindowsUpdateLog and press the enter key.
Some text will appear in the blue window. Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
Close the blue window.

Attach the file C:\Users\<username>\Desktop\WindowsUpdate.log to your next reply.
Attach the file C:\Windows\Logs\CBS\cbs.log also.
If the files are too big, zip them first.
 
Just letting you know I had a look at the log and it seems it might be uaspstor.inf causing the issue however im not sure how to fix it...

2025-05-22 04:38:05, Info CBS Doqe: [Forward] Installing driver updates, Count 99
2025-05-22 04:38:06, Info CBS INSTALL index: 59, phase: 1, result 0, inf: miradisp.inf
2025-05-22 04:38:06, Info CBS INSTALL index: 129, phase: 1, result 0, inf: UcmUcsi.inf
2025-05-22 04:38:06, Info CBS INSTALL index: 130, phase: 1, result 1359, inf: uaspstor.inf
2025-05-22 04:38:06, Info CBS Doqe: Recording result: 0x8007054f, for Inf: uaspstor.inf
2025-05-22 04:38:06, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]
2025-05-22 04:38:06, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x8007054f - ERROR_INTERNAL_ERROR]
2025-05-22 04:38:06, Info CBS Perf: Doqe: Install ended.
 
The logs on May 12 don't contain those lines.
Please attach the complete CBS.log
 
Here is The most recent CBS log which contained those lines. not sure why it would be different to the one I sent last time as I have changed nothing.
 

Attachments

Attach the file C:\Windows\INF\setupapi.dev.log to your next reply.
 
FRST Scan:
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

FRST Scan:
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

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

Back
Top