Windows Update 0x8024500C

[Cache]

Anyone any advice on this one please?

 

I set up a new WSUS server on Server 2016 3 weeks ago and all was fine, looked at WSUS while checking a couple of things for tomorrow and noticed the server hadn't checked in for 8 days. Running Windows Update gives update error 0x8024500C, it did eventually check in though.

 

Anyone any hints as to what it might be? Googling produces errors relating the the "Dual Scan" functionality of Windows Update, but out of all the policies enabling it all I can see is the only one I have enabled is the one which disables it checking against Microsoft Windows Update.

 

Tried manually installing the October Cumulative update and enabling the do not allow the defer policies to trigger checking against Windows Update but still the same result. This is only affecting the server 2016 machines, Windows 7 / 2008 / 2008R2 / 2012 / 2012R2 are all checking fine.

 

Stumped now, any help appreciated!

[speckytecky]

We are on 2012 but the WSUS on that decides to stop every couple of weeks and only comes back live after a server restart.

[Cache]

Tried that, even left it off for an hour in the vague hope it might do it but alas no.

 

Can't even read the Windows Update log file because the system can't decode it and no amount of Symbol updates seems to fix it.

[Cache]

Just in case anyone else comes across this, still can't read the Windows Update log but an old fashioned Windows Update reset fixed being able to check for updates.

[ajs]

Try running Get-WindowsUpdateLog in Powershell and reading the generated file to see what's going on.

[Cache]

Get-WindowsUpdateLog can't decode it for whatever reason, just returns a load of unknown entries with "No Format Information Found".

[minimoo]

@Cache - might not be related but something you could try / investigate:

 

a) https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/ might related (might not be)

b) increase the iis pool size https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/

[3s-gtech]

I just fixed a batch of laptops with this error. I had switched off internet location for updates (as they were pulling the 1709 update alongside unapproved stuff), they then gave this error when checking from WSUS. The storage on the WSUS server was completely full, so expanded that then stopped WU on each client, emptied SoftwareDistribution, restarted WU and they all worked lovely.

[Cache]

I have fixed the error code by resetting the Windows Update components on the server as I posted above and what @3s-gtech posted and posted it back in case anyone else came across it - I still can't read the WindowsUpdate log but as long as Windows Update carries on working that can be a fight for another day.

 

Thanks for the additional replies though.

Edited November 18, 2017 by Cache

[newpersn]

anyone else having problems?

 

I'm downloading office updates but not Windows 10 updates? I'm i missing something?