Windows Update is broken for some Windows 7 users

Windows 7 users are reporting problems checking for updates through Windows Update and Microsoft Update.

The root of the problem may be an expiration date that Microsoft needs to fix on its side, noted Computerworld earlier today.

A Microsoft Answers thread for those hit by the Windows Update Error 80248015 -- which began at some point on December 3 -- is growing. I've also seen some with Windows Server 2008 reporting this same problem on Twitter...

Click to expand...

Read more: Windows Update is broken for some Windows 7 users | ZDNet

I am getting the message ""Windows Update cannot currently check for updates because the service is not running. You may need to restart your computer.""
Should I just wait for MS to sort this out?

mitchell65 said:

I am getting the message ""Windows Update cannot currently check for updates because the service is not running. You may need to restart your computer.""
Should I just wait for MS to sort this out?

Click to expand...

I read that's one of the errors that's been cropping up lately. Have to wait for MS to push out a fix for it. Will have to download and install it from MS update catalog if that's the case.

I haven't had any issues on any of my systems though, so not sure why it's affecting some and not others.

According to MS, they've now fixed the issue...

Did Microsoft Just Break Windows 7 Update System?

Hi

My guess is its the recently released November Preview kb4051034
They were playing arround with the Certificates.

As i DIDNT install it, guess what i can update

Roy

torchwood said:

Hi

My guess is its the recently released November Preview
They were playing arround with the Certificates.

As i DIDNT install it, guess what i can update

Roy

Click to expand...

Think you could be right there Roy.

I never install the previews either, so haven't had any update issues.

As its NOT an MS fix in that article, just a suggested known workaround.
MS will have to issue a standalone KB to fix it, because as stated in the article the .xml is digitally signed


Roy

I haven't install any previews in about 3 months and I had the problem.
Took a good long needed rest from my computers and this mourning it seems Microsoft has fixed the problem on one of my computers. The other one still has the problem.

I get

Windows Update cannot check for updates, because the service in no running. You may need to restart your computer.

I have restarted 3 times and it didn't help.
I do not get any error code.

Is there a 'KB' that I should be looking for to remove??

torchwood said:

As its NOT an MS fix in that article, just a suggested known workaround.
MS will have to issue a standalone KB to fix it, because as stated in the article the .xml is digitally signed


Roy

Click to expand...

Wasn't referring to the fix in the article, just the fact that at the bottom of the article MS has stated they've fixed it.

Some more info from MS instead of just "we've resolved it" would be helpful though!

Rollback the date prior to Sunday and manually run the update then change it back to the present date. That should update the expiration date in the authcab file.

Thank you very much Sky Ranch!

That process fix the problem.

I'm going to reboot and try Windows 7 Updates again to verify.
It's still working as it should.

Jack

Sky Ranch said:

Rollback the date prior to Sunday and manually run the update then change it back to the present date. That should update the expiration date in the authcab file.

Click to expand...

Nice find Sky Ranch! Any idea what's causing it? As I can't seem to reproduce any errors on any of my systems. Thought perhaps it might be something they've pushed out in the rollups as I don't install those, only the Security-only updates, and haven't had any problems with WU.

Brds7t7 said:

Nice find Sky Ranch! Any idea what's causing it? As I can't seem to reproduce any errors on any of my systems. Thought perhaps it might be something they've pushed out in the rollups as I don't install those, only the Security-only updates, and haven't had any problems with WU.

Click to expand...

No clue as to why some users are not affected.

You can look in the Software Distribution directory and look at when the last time the authcab file was updated and open the authentication XML document and take note of the expiry date.

Edit: It could also be that you had "Microsoft Update" disabled in WU settings. I've noticed that as a workaround (uncheck Microsoft Update) for users that were afflicted with the recent WU problem.

Sky Ranch said:

No clue as to why some users are not affected.

It could also be that you had "Microsoft Update" disabled in WU settings. I've noticed that as a workaround (uncheck Microsoft Update) for users that were afflicted with the recent WU problem.

Click to expand...

Weird, I've tried it with other MS products both checked and unchecked and still can't reproduce it.

The plot thickens....

Sky Ranch said:

Rollback the date prior to Sunday and manually run the update then change it back to the present date. That should update the expiration date in the authcab file.

Click to expand...

Just noticed the issue this morning.
Thanks Sky Ranch, your suggestion fixed it for me.
Strange, I haven't seen that happen before, I simply could not even open Windows Update - just a blank window with the houglass.
That resulted in explorer.exe restarting each time.

I got it this afternoon after 3 tries, restored a backup, updated, seems to be back to "normal". Thought it was just my machine.

My Windows Update is still not working. I am able to see my list of installed updates, and my last set was installed on 11/30 - all seem to be MS Office - related updates. I haven't installed any "preview" updates, although I do install the roll ups periodically, so I don't think they are the cause of this - at least not for me. I haven't tried rolling the date back yet, since I don't know if there are any updates I need to install immediately and I wasn't sure if that only applied to Error 80248015.[FONT=&quot][/FONT]

I don't have any error messages containing error numbers - instead, I get the red shield with the X, and the pop up dialog box saying that Windows can't check for updates because the service isn't running, and I need to restart my machine. Doesn't help.

I'd rather not delete my Softwaredistribution folder, as some have done, because I'd still like to be able to see my update history. I have a restore point from 11/30, so if I need to I can restore from that point.

In the meantime, should I give this a few days to see what we get from Microsoft?

Or, is the link I pasted below the fix for this? I couldn't tell when it was released so I don't know if it's current, and I've browsed so many threads and sites I can't remember where I found this.

[FONT=&quot]https://support.microsoft.com/en-us...eck-for-updates-error-message-when-you-try-to
[/FONT]

Laurie. The problem seemed to have started on the 3 Dec 2017 & is caused by an expiring MS AuthCab date.

To repair the situation, untick the Auto Time setting Function, in Time & Date, then reset the date to before 3 Dec 2017. Reboot the computer. Run Windows Update & it may update if there any not included before 3 Dec. When it has finished Updating, reset the Auto Time function & reset the date to today. Reboot the computer & re run Windows Update, which should now work & install Updates to the current time.

This is what I did on mine this Morning & Windows Update is working properly again & I have not lost my Update history.

Sky Ranch said:

Yes, rollback the date prior to 12-3-2017 and manually run the Windows update then change it back to the present date. No reboot necessary.

Check C: Windows > SoftwareDistribution > AuthCabs > authorization (file date should be 12-4-2017)

Click to expand...

What you say is correct if you are not locked out running Windows Update. Just changing the Date will not fix the lock out. You have to reboot after the date set so you go back to before the AuthCab expired.

Ranger4 said:

What you say is correct if you are not locked out running Windows Update. Just changing the Date will not fix the lock out. You have to reboot after the date set so you go back to before the AuthCab expired.

Click to expand...

I had the same scenario as the above poster on multiple machines and all I did was rollback the date and went back into control panel and manually update.