Newsletter Archives

• Windows Update in Win7 now appears to be working properly

  Posted on December 5, 2017 at 02:28 CST by woody • Comment in the Forums

  @MrBrian notes, and @abbodi86 confirms, that the bad value <ExpiryDate> updates itself when you check for Windows updates.

  Bottom line: You don’t need to do anything. As of a few hours ago, Windows Update should work normally.

  Windows Update’s new expiry date on Win7:

  2025-07-01T00:00:00.0000000-00:00

  Which seems to me to be just as arbitrary as the old one.

  Windows Patches/Security 80248015

• Windows Update for Win7 broken, throwing error 80248015

  Posted on December 4, 2017 at 08:38 CST by woody • Comment in the Forums

  Short answer: It’s Microsoft’s fault. They let the ExpiryDate pass without updating it. You can tweak your machine (e.g., set the date back) but for now, Win7 users just get to wait until Microsoft acknowledges and fixes the bug. In the interim, half of all Windows users around the world are unable to run Windows Update.

  Computerworld Woody on Windows.

  Yesterday’s comments are here. I tried to merge them into this post, but the AskWoody site isn’t working right. Sigh.

  Windows Patches/Security 80248015, Windows Update

• More on the 80248015 bug – XP users, heads up!

  Posted on November 27, 2014 at 03:15 CST by woody • Comment in the Forums

  Over at Computerworld, Michael Horowitz has sliced and diced the update <Expirydate> problem.

  Interesting info, particularly that he got the wuauclt.exe /detectnow command to break the logjam.

  If you have an XP or Server 2003 system – or you know someone who does – and they aren’t getting updates, make sure they understand that they aren’t alone. It’s Microsoft’s doing again. Still no official confirmation, still no idea when/if it’ll get fixed.

  Windows Patches/Security 0x80248015, 80248015, Server 2003 update, Windows XP update