We help IT Professionals succeed at work.

Windows update from WSUS failed on some computers

Medium Priority
579 Views
Last Modified: 2018-08-26
In the WSUS 2012 console, if I go to Updates > All Updates and filter by 'Any Except Declined, Status = Failed' I see that an update (2018-06 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4284835)) installed for 91% of the computers but for some, there were errors. Double-clicking on this line item generates the report, which shows:

For 4 computers the Status = Installed
For 48 computers the Status = Not Applicable
For 6 computers the Status = No Status
For 6 computers the Status = Failed.

Over the last week, I tried a few times right-clicking on the failed update and selecting 'Approve' again, hoping that something would kick in and WSUS would attempt to trigger these updates again. But that doesn't seem to work.

I found some articles online that describe how to run the Windows Update Troubleshooter tool or stop the Service, delete the contents of the update folder, restart the Service and try again, but I imagine there's no automated way to do this. (I'd have to do this manually on each workstation?)

Are there any tricks or tips for getting updates to install?

One more thing: In that WSUS report, I can click on the 'Failed' link under the Status column (next to each of the 6 computers that failed) and a pop-up window shows the error. Almost all of them simply say "Error: Download failed."    Does this mean WSUS is not downloading this update? Or it is not able to push the update to the workstation? Or is the workstation trying to download this update? (I thought it should not do that if updates are being managed through WSUS? What would it be downloading?)

All of the computers are on the domain and on the same local network as the WSUS server.
Comment
Watch Question

MichelangeloSystem Administrator / Postmaster
CERTIFIED EXPERT

Commented:
The failed status means the computers were not able to complete the update install.
The clients are the ones downloading the update from the wsus which doesnot push updates, just makes them available for seected clients to download. The clients may be in auto install mode or not: check on one of the conouters the windows update setings and try a manual install from wsus.
E C
CERTIFIED EXPERT

Author

Commented:
One of the computers giving the error happens to be my workstation. I am in the Administrators group (a domain admin, actually). If I open the Windows Update page on my workstation and click the 'Retry' button, it says 'Checking for Updates' but within 1 minute, changes to 'Update Failed'

There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help:
2018-06 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4284835) - Error 0x80242006

Only option is 'Retry'
MichelangeloSystem Administrator / Postmaster
CERTIFIED EXPERT
Commented:
You could try this
https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78
On your workstation. It should reset windows updates
MichelangeloSystem Administrator / Postmaster
CERTIFIED EXPERT

Commented:
IF it does, it probably can be automated on clients
IT Systems Engineer
Commented:
Remove WSUS Settings Manually
Click Start and type regedit into the start search box, then Right Click and Run as Administrator.
Navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\
Right Click and Delete the registry key WindowsUpdate, then close the registry editor.
Open the Services Console by entering services.msc in the start search box.
Locate and Restart the Windows Update Service

this should reset the machine to blank and try that. also delete the machine from the wsus.
MichelangeloSystem Administrator / Postmaster
CERTIFIED EXPERT

Commented:
Hi Ecarbone,
any luck with your issue?
E C
CERTIFIED EXPERT

Author

Commented:
It was a lot of manual work but I essentially removed the WSUS settings from 12 computers, then I reset WSUS and re-implemented it. So far it appears to be working as expected. It's too bad that WSUS does not have a way to force these changes on the workstations. If something goes wrong you should not have to do this type of work on every computer. I think once things level out it will become more manageable and I'll keep an eye on WSUS at least once a week. Thanks again for your help with this.