By Brian Livingston
Reader Jeremy Rosenblatt blows the whistle on a situation in which Microsoft’s widely used Windows Update routine finds no updates to install – even when there are clearly many patches needed by a machine.
“The behavior would not cause a typical user to suspect a problem,” Rosenblatt writes, “as Microsoft provides no hint that an error has occurred.” I’ll let him tell the rest of the story:
- “The cause of the issue is that if a machine has its date set to something outside of the valid range of the SSLcertificate on MS’s WinUpdate site, WinUpdate will get an SSL error. Instead of reporting it in some intelligible manner, WinUpdate simply reports, ‘There are no updates available for your computer. Please check back later’ (with no error message at all).
“Only if you then click on the ‘See Also/Windows Update Catalog’ do you get a clue that there might be an error involved. And even then it isn’t obvious what’s going on. You get an error page, but the only troubleshooting tip is a mailto tag that formats an e-mail to MS with ‘ERROR 0x800A138F’ in the subject line.
“It’s easy to try for yourself. Just change your machine’s date to 2001, open a fresh instance of IE and go to Windows Update.