[SOLVED] Windows could not search for new updates Code 80092010

[burrito]

I have exhausted my google-fu skills to the best of my ability and cannot find anything on this error code (80092010). From what I could find related to general issues with Windows not being able to pull updates I have scanned the file system (sfc /scannow), I've reported the affected servers to WSUS (wuauclt.exe /reportnow /detectnow), I've restarted the Windows Update service on affected servers, as well as restarting update services on WSUS (WSUS Service and Windows Update), and finally the good ol' reboot of the WSUS server. I can still pull updates from Microsoft by checking for them online and can reach the web portal for WSUS.

Some other suggestions were related to IIS, SQL, and the WSUS database (reindexing the db if it hasn't been done in a while) but I wasn't quite sure how to pursue this avenue and it seemed irrelevant especially re-indexing the WSUS db, since the WSUS server isn't that old.

Since I cannot find a precedent for this specific error on Technet or other relevant sources and any troubleshooting steps related to the general issue of not being able to check for updates have proved to be fruitless I am reaching out to you fine people. Any suggestions would be greatly appreciated.

 

[Go The Power]

Hello and welcome to the forum.

The error code 80092010 refers to following reference:

C:\Users\Alex\Desktop\~ENV>err 80092010
# for hex 0x80092010 / decimal -2146885616 :
[COLOR="#FF0000"]  CRYPT_E_REVOKED                                               winerror.h
# The certificate is revoked.[/COLOR]
# 1 matches found for "80092010"

C:\Users\Alex\Desktop\~ENV>

Are you still using a certificate for the WSUS configuration? From what I can see it was turned of by defualt WSUS no longer issues self-signed certificates - WSUS Product Team Blog - Site Home - TechNet Blogs

Are you able to check the certificate to see if it is still active?

 

[burrito]

The cert we have is still valid through 8/6/2018 which is issued by Go Daddy. This looks like it was changed back in August of 2013 from the Technet link you posted. However this is a new issue for us, seeing updates ran smoothly last month.

Also, our onsite WSUS server(no issues this update cycle) is running Server 2012 compared to the offsite server that is having the issues which is on Server 2012 R2.

 

[burrito]

So I wasn't aware that our certs were re-keyed for our off-site servers when we recently re-keyed our onsite's. This would explain the invalid certificate issue you initially explained. Thanks for the help Power, much appreciated!

 

[Go The Power]

Your welcome :)