Unable to patch server 2016 w/KB5053594

S

Sullie

Member
Joined
Apr 2, 2025
Posts
5
Hello,

Background:

VM is about 18 months old? After running perfectly for 18 months or so, this month, this VM refuses to allow monthly patches. I see nothing wrong with the machine and I would prefer not to rebuild it because installing the purpose software (I mean the reason the server was created) was painfully difficult and I don't want to have to go through that again if I don't need to.

Virtual machine running KVM flavor of hypervisor. Machine is Windows Server 2016 64-bit, 1 proc, 16gb ram, 1 hard drive (185 gb capacity with 86 gb used, 98 gb free) - zero previous issues.

Things I've done to try to remediate have been reboot, power off/power back on, download this month's KB and tried to install manually, shut off windows update service + renamed c:\windows\softwaredistribution folder to *.bak, turned windows update service back on then tried to update the KB manually w/downloaded KB file and some other tricks from the past I'm forgetting I'm sure.

1.) Run SFC Scan - after running I receive the following:

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.) Run dism /online /cleanup-image /restorehealth

C:\>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

The component store is repairable.
The operation completed successfully.

C:\>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[===========================80.0%============== ]
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

C:\>dism.exe /online /cleanup-image /restorehealth /source:\\*servername*\c$\winsxs /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[===========================72.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 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

*I put the actual server name in that spot, but I also tried mounting the iso to a drive letter which I used to build the machine with originally, I also tried downloading the iso from this link from MS, etc."

3.) Run ComponentsScanner - done - see attachment.

4.) Export CBS Folder - done see attachment.
 

Attachments

Hi @Sullie,

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
 
Hello and welcome,

Remove Update Manually
  1. Right-Click the Start button and click Command Prompt (Admin) on the list.
  2. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:4054590
  3. Let me know if it says it was successful or if there are any errors.
 
Hello,

@PeterJ - I tried this, it did remove that KB but then I went back and tried to apply this month's updates but they fail again.

Thank you!
 
I don't have 5 messages accumulated yet so I cannot reply directly to PM's just yet.

However someone sent me the following PM:

Hi Sullie

Do you still need assistance with your Windows repair? If so:

Can you please run
Repair-WindowsImage -Online -RestoreHealth
in elevated PowerShell window and after completion, attach these files here
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\dism.log


Yes, so I did try that already and I've attached those logs to this post up at the top.

Thank you.
 
As this is a public thread you should not receive a PM with some steps to perform.
Who send you you that PM ?
 
I may have misstated; it was a direct message sent by garegin, I'm not sure if PM and DM are considered the same thing here. I don't want to get anyone in trouble especially if they were just trying to assist.
 
Thank you for reporting this. It shouldn't have happened. All messages in this thread should be visible to read and provided by one helper. Another helper may post on request and post on prior notice only.
Please do following.

FRST Registry Search
  1. Click the Start button and in the search box, type CMD
  2. When you see cmd.exe on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, press enter afterwards.
    Code: 
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

    Note: This loads your components hive which is what we want. Please keep the command prompt window open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  4. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB4054590 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
@PeterJ - thank you for the heads up.

So, I'm running 2 forms of protection on this server and corporate policy dictates we can never turn off protection. So, I will reach out to my protection services and see if I can get a one-hour exception to run this software. When I try to run this software it's flagged, alerts are sent, emails are generated, the software is killed/blocked immediately. I've tried twice now, and I've gotten several emails from our security teams just trying to keep our environment safe which I appreciate. Again, I will reach out to our service providers and see if I can get a temporary exception. I'm happy to see they're protecting us, but it can be a bit restrictive at times.
 
Okay, please note that the tool FRST is completely save to use.
 
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