Windows Update Failing

Steel Contributor

I have 8 Virtual Machines all running Windows Server 2016 Standard and all are setup with a Windows Update Group Policy to run on a specific night and time. However, I have one server that continues to fail on the same 2 Windows Updates. Not sure why this server is having issues with the updates, as all the servers are pretty much identical. Any ideas to help me troubleshoot? Here are the 2 updates that continue to fail:


2019-12 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4530689)

2019-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4507459)

19 Replies


2019-12 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4530689)

2019-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4507459)

For the 7/2019 update I'd try installing the prerequisite SSU


For the 12/2019 update I'd try installing the prerequisite SSU




@Dave Patrick 


Thanks for your quick reply. I downloaded both prerequisites and tried to install. However, it is showing that I already have both of them installed already. Any other thoughts or ideas? Thank you!!


Next step is to download and install;




@Dave Patrick 


The installation was successful. I just need to restart server now and see if there are any errors after restart. I will let you know tomorrow, as I wont be able to restart until after business hours. Thanks!

Sounds like success then. The older 7/2019 update won't be needed since updates are cumulative.


 (please don't forget to mark helpful replies best response)



@Dave Patrick 


After restarting my server, it still shows that the Update failed. Any other ideas? Thank you.

@Tim Hunter 


If you’re technically savvy, you can try the steps below :


1. Click Start and start typing on your keyboard for "services.msc"
2. In your search results "services.msc" should show up. Open it with a click.
3. A new windows will open containing all Windows services on your system.
4.Search for "Windows Update"
5. Right-click the "Windows Update" and then click Stop.

We will now clean the Windows Update temporary cache folder:
1. Hold your windows-key pressed and hit "R" key simultanous.
2. A small new windows will appear.
3. Type %windir%\SoftwareDistribution\DataStore in this new window and click OK.
4. This will open Windows Explorer on the correct location.
5. Delete all contents of this folder. (Hint: Use Ctrl + A to select all files and folders)

Now we will start the Windows Update Service again:
1. Switch back to the windows Services.
2. Locate Windows Update.
3. Right-click on it and choose Start.
If the problem still persists i would recommend you to switch to latest windows server 2019.
Hope this helps

What failed exactly? Also post the results of;


(Get-HotFix | Sort-Object -Property InstalledOn)

A picture ….. really? How convenient to work with.




@Dave Patrick 


Source Description HotFixID InstalledBy InstalledOn
------ ----------- -------- ----------- -----------
EBE Update KB3192137 NT AUTHORITY\SYSTEM 9/12/2016 12:00:00 AM
EBE Update KB3199209 NT AUTHORITY\SYSTEM 10/25/2016 12:00:00 AM
EBE Update KB4132216 NT AUTHORITY\SYSTEM 5/22/2018 12:00:00 AM
EBE Update KB3186568 EBE\Administrator 5/25/2018 12:00:00 AM
EBE Update KB4091664 NT AUTHORITY\SYSTEM 10/12/2018 12:00:00 AM
EBE Security Update KB4465659 NT AUTHORITY\SYSTEM 11/14/2018 12:00:00 AM
EBE Security Update KB4485447 NT AUTHORITY\SYSTEM 2/19/2019 12:00:00 AM
EBE Security Update KB4498947 NT AUTHORITY\SYSTEM 5/17/2019 12:00:00 AM
EBE Security Update KB4503537 NT AUTHORITY\SYSTEM 6/18/2019 12:00:00 AM
EBE Security Update KB4509091 NT AUTHORITY\SYSTEM 7/16/2019 12:00:00 AM
EBE Security Update KB4512574 NT AUTHORITY\SYSTEM 9/11/2019 12:00:00 AM
EBE Security Update KB4521858 NT AUTHORITY\SYSTEM 10/15/2019 12:00:00 AM
EBE Security Update KB4520724 NT AUTHORITY\SYSTEM 11/19/2019 12:00:00 AM
EBE Security Update KB4503267 NT AUTHORITY\SYSTEM 1/9/2020 12:00:00 AM

You said earlier that was successful? I don't see any trace of it.


May need to check the \windowsudate.log file for details.


(please don't post debug logs in forums)







@Dave Patrick 


Windows showed the installation was successful and then asked for a restart. After restarting, it showed the update as failed.


I opened the Log folder but all I see are .etl files that are "garbled" when I open them in Notepad.


You'll need to use PowerShell to generate the readable log file.






@Dave Patrick 


Appreciate all your help and guidance on this, as I know very little and am trying to learn as I go.


Do I need to do another process first, in order for the Get-WindowsUpdateLog to work?


Get this error:

Get-Process : A positional parameter cannot be found that accepts argument 'Get-WindowsUpdateLog'.
At line:1 char:1
+ PS C:\WINDOWS\system32> Get-WindowsUpdateLog
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-Process], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.GetProcessCommand

Well here's what should have happened.


Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator.DSPATRICK> Get-WindowsUpdateLog

Converting C:\Windows\logs\WindowsUpdate into C:\Users\Administrator.DSPATRICK\Desktop\WindowsUpdate.log ...



DumpFile:           C:\Users\ADMINI~1.DSP\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00000

The command completed successfully.



DumpFile:           C:\Users\ADMINI~1.DSP\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00001

The command completed successfully.

 Some things to try;


sfc /scannow

dism /online /cleanup-image /restorehealth

or possibly a repair install by running setup.exe from the root of the install media. I'm not a big fan of doing this and in my opinion time would be better spent standing up a new one, patch fully, migrate roles or applications over to it.






@Dave Patrick 


PS C:\Users\administrator.WYNNETR> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Managemen
Version: 10.0.14393.0

Image Version: 10.0.14393.2457

No component store corruption detected.
The operation completed successfully.



@Akshay_Mane wrote:
If the problem still persists i would recommend you to switch to latest windows server 2019.


The official Microsoft website link for Windows Server 2019 is this:


Not that 3rd party link in your comment.

@Dave Patrick 

A sarcastic comment. How useful to work with.


Server 2019 does exactly the same with various updates.