1

I have a Windows Server 2012 R2 running WSUS in the domain. I can see several Windows 8.1 computers not reporting status for over 2 weeks, and not installing any new updates, in the WSUS console.

On the client computer, manually clicking on 'Check for updates' results in an infinite loop of the client computer 'checking for updates' despite having a reliable and fast Ethernet connection to the WSUS server.

I have restarted the Windows Update service multiple times and removed the C:\Windows\Software Distribution directory, to no avail. The clients just keeps on searching for hours and hours with no end in sight.

Any ideas what I can do since Windows Update never displays any error message?

Citizen
  • 1,103
  • 1
  • 10
  • 19
pfolta
  • 21
  • 1
  • 7
  • What do the client logs have to say? – jscott Jun 03 '16 at 13:48
  • Oh, I completely forgot to mention the logs: So the standard Windows logs (application, security, system...) don't really have any entries relating to Windows Update. The log under WindowsUpdateClient\Operational logs an error when the Windows Update service is stopped, either with error code 0x8024002E or 0x80248014. I couldn't really find anything helpful online yet. – pfolta Jun 03 '16 at 13:59
  • And the [Windows Update client log](https://support.microsoft.com/en-us/kb/902093), anything interesting there? – jscott Jun 03 '16 at 14:10
  • Here's the client log file: http://pastebin.com/HUn2GuUC – pfolta Jun 03 '16 at 14:22
  • Are group policies updating and working on the Windows 8.1 clients? – Citizen Jun 03 '16 at 21:00
  • Yes, group policies are updating and working. – pfolta Jun 03 '16 at 21:25
  • do the windows update agent update and try again from a computer – yagmoth555 Jun 03 '16 at 22:07

3 Answers3

1

I was able to solve the problem by deleting the SoftwareDistribution and then running this reset tool: https://support.microsoft.com/en-us/kb/971058.

pfolta
  • 21
  • 1
  • 7
1

What we have managed to find is that the Update Orchestrator service is to blame so we have created a script that finds the process ID for Windows Update service (the update orchestrator works off of the same Process ID) kills it, deletes the software distribution folder (which might be unnecessary) and starts the Windows Update service again. The Update Orchestrator will follow shortly and updates will be able to resume. This requires being "run as administrator".

$ServicePID = (get-wmiobject win32_service | where { $_.name -eq 'wuauserv'}).processID
Stop-Process $ServicePID -Force
Remove-Item -Recurse -Force C:\Windows\SoftwareDistribution
net start wuauserv
Kyle Graham
  • 11
  • 1
-1

This helped me on Windows 7:

FIRST, STOP the B.I.T.S service AND Windows update... (via Services)NEXT , web search for KB3172605 (as of July 2016... and if that's outdated, search it anyway, Windows will point you to the proper update automatically, READ!)INSTALL the KB above... reboot, and start your normal Windows Update... Within 3 minutes I had 100's...

Jevgenijs
  • 1