Windows Update Service Not Running!

Topic

New Reply

I have a major issue on both my husband’s and my laptops. We both have Windows 7 64 bit Home premium and both WU is set for “check for updates but let me decide”. All our updates are up to date as for October updates. Recently Woody changed the Defcon to level 3 and said to get patched with regard to the Nov patches. Now all the required updates were showing on both pc’s as of last night before I went to bed (I left mine in sleep mode and shut down my husband’s). I had some questions and I was following the Defcon 3 thread here on Woody’s so I didn’t do any of the updates, I was going to do them today. Well when I clicked on the WU icon today to start the updates it said that my computer was up to date and that there were no updates available which I know was not the truth because I hadn’t installed any of them. I then clicked on “check for updates” and I got some sort of error (sorry can’t remember the number). I checked the installed updates and nothing other than the MSE definitions update was installed since all the Oct. updates. So I thought it might be a glitch and maybe I needed to restart my computer so I did. In the meantime while I was waiting for my pc to reboot I turned on my husband’s pc to check things out there. When mine rebooted and his started neither had the WU icon come up on the task bar as it usually does when there are new updates. So I clicked on the start button on both pc’s and manually went to the Windows Update and when I click on it I get this message:

When I click to check for updates I get this message:

I get this on both pc’s and I have restarted both and get the same thing. I have gone into the task manager to try to turn on the Windows Update service but nothing shows for WU.

I ran a Malwarebytes scan and no threats are detected.

I am NOT sure what to do……..HELP!!! Is it SAFE to use our pc’s?

 

3 users thanked author for this post.

woody, Pepsiboy, Microfix

Reply | Quote

Replies

It may be that the Windows Update Service itself is disabled or not started:

Click the start button (bottom left)
type service into the text box
Click Services (the list is aplhabetic)
Slide down to Windows Update
Does it show started?
If not, Double-click it
Click Start and make sure start up type is set to automatic (delayed start)
OK

If this does not fix things, I can offer more complex solutions

CT

1 user thanked author for this post.

KarenS

Reply | Quote

Thank You Canadian Tech, I have in fact gone in to the services on both pc’s and both say that the Windows Update is started and both set for automatic (delayed start). Keep in mind that I only use my computer and I am not savvy at all with doing any type of work on computers so anything in real depth will be over my head. 🙁

Reply | Quote

Hello,

Did you realize that we’ve passed “ExpiryDate”? I didn’t so I had problems with Windows/Microsoft Update.

Look at “c:\Windows\SoftwareDistribution\AuthCabs\authcab.cab” file.

There is information about valid date:

<IssuedDate>2013-12-03T11:59:25.5067616-08:00</IssuedDate>
<ExpiryDate>2017-12-03T11:59:25.5067616-08:00</ExpiryDate>

We must wait for newer file:

… or revert system’s date to older than 2017-12-03.

Edit: removal of direct download of .cab file

2 users thanked author for this post.

abbodi86, KarenS

Reply | Quote

Open Windows Update and click Change settings, change to Never
Restart your computer

I know this will sound complicated, but it really is not…….

You are going to reset Windows Update components:

Start, All Programs, Accessories, Right-click on Command prompt, Choose Run as administrator, OK. Type the following in the black box:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
pause
Exit

Tip: Instead of typing each line, you can select the text in the line above by high-lighting it, right-click, choose Copy from the pop-up menu. In the black window, Right-click anywhere, choose Paste from the pop-up menu, Enter.

CT

1 user thanked author for this post.

KarenS

Reply | Quote

Canadian Tech I know you are trying to help but I really don’t feel comfortable doing anything like that on our pc’s. I am so scared of screwing things up worse then they are now and then I will really be in a mess. What I don’t understand is WHY did BOTH pc’s do the exact same thing on the same day. One being left in sleep mode and one shutdown, neither installing any sort of update?

Reply | Quote

I can confirm the reset described by Canadian Tech here worked in at least one instance. Caution, it is destructive to Update History; but everything will still be properly listed in Installed Updates.

My 2011 Toshiba Satellite laptop (AMD) is now a secondary device, so I was less concerned with it’s fate. I remember when CT started his epic Answer thread on that volunteer website, and what caused it. I am not a big believer in coincidences. Aging Win7 is still outdistancing Win10. And there is a major gift-giving holiday this month. Might be a good time to nudge a few people into the market place. By hook or by crook.

I also acknowledge that if a transient problem at Microsoft’s update server just happened to become repaired within the same hour that I applied CT’s method; then I have come to a wrong conclusion. See above opinion regarding coincidences.

1 user thanked author for this post.

Microfix

Reply | Quote

anonymous #149436 here.

Pardon me, I used the term destructive without mentioning that all can be restored until you take the actually destructive action of deleting the renamed folder. The only thing CT’s reset does is hide the previous folder under a new name. To recover, without destroying either, shuffle the folders by renaming the new to a third name, then rename the old to the original. Reread that until it makes sense.

Reply | Quote

Thanks, that worked for my Win7 Pro 64-bit w/ last visit to WU 01 December.

Reply | Quote

I think there is something else going on.

@KarenS has two unrelated computers with the problem all of a sudden.
A friend of mine has the same problem when I tried to help her with updates this afternoon.
I had two pending updates on my Win7 – unchecked MSRT and a checked Office update that I have been waiting on. It now says I’m up to date – no updates.
One of the few hardware installs I have – is having the same problem – it’s been down since the last updates.

I think there is a problem with MS.

4 users thanked author for this post.

Microfix, dgreen, JDeC, KarenS

Reply | Quote

Agree, I think MS has an issue (if not many)

Windows - commercial by definition and now function...

Reply | Quote

I am also receiving the same Windows Update Error when I just checked for updates. The error code is: 80248015.  Prior to checking for updates I noticed that the unchecked November MSRT windows update had been removed, and that the most recent MSE definition update failed to install. The last one to correctly install was 1.257.1318.0 at 7:30 am  this morning.

A few months ago there was a similar problem that turned out to be caused by a faulty MSE update. At that time it took 3 or 4 days before Microsoft corrected the error.

2 users thanked author for this post.

dgreen, JDeC

Reply | Quote

CanadianTech and PKCano I am having the exact same problem!

PKCano do you think it is a problem with MS and we should just sit tight or is the Nov. rollup the problem????

edit to add..
FYI my last MSE update was this morning 1.257.1307.0

Reply | Quote

I don’t think this has anything to do with MSE – non of those reporting have done the updates.

I think MS is having a problem. Maybe WU is down. It’s too widespread for it to be an individual’s PC.

3 users thanked author for this post.

Microfix, KarenS, dgreen

Reply | Quote

What I noticed yesterday or the day before, was that one of the MSE def updates was in the recommended/ optional section of WU, these def updates are normally in the Important section.

Windows - commercial by definition and now function...

Reply | Quote

It is truly a shame what a mess Microsoft has made of the decades long revered Windows Update (WU) system. I know I am a heretic, but I saw this developing over a year ago. I look after about 150 client Windows 7 computers. September 2016, I set all computers WU to Never. For some months until May of this year, I applied so-called “security only” updates. Then they became all messed up. Office updates have become a cesspool.

At that point, I decided that the risk of Microsoft making a positive mess out of our Windows 7 computers was a certainty, while the risk of some hacker with a virus making a mess of our home computers was far less.

Not a one of these computers has seen a Windows Update since May 2017. They are protected by Bitdefender antivirus. Not a single one of them has had a problem of any kind. They are all stable and run completely reliably. Bottom line, for us, January 2020 has already come and gone. Guess what, Windows 7 looks better than ever for now.

CT

4 users thanked author for this post.

RamRod, woody, Elly, dgreen

Reply | Quote

PKCano that was my first thought when I realized that both of our pc’s did the exact same thing. I tried to Google it to see if there was a issue with MS or Windows Update but I can’t seem to find anything. That was another one of the reasons why I didn’t want to mess around with changing anything because if it is on MS’s end I might just end up doing something that I shouldn’t. I am a little relieved to hear that I don’t seem to be the only one having similar issue, not that I wish this on anyone else. Both my husband and I have Toshiba pc’s but different model numbers, both purchased in 2011. We had 4 Outlook 2010 updates (checked) and then the .NET update, the monthly rollup (both checked) and then the MRST (unchecked). All where there at 1:09pm this afternoon when my WU checked for updates but then when I went to install them I got the message that there was “No updates for my computer that everything was UP TO DATE”.

Reply | Quote

The next Patch Tues is the 12th. We have time to wait on this one.
Take a deep breath and check back tomorrow.

2 users thanked author for this post.

KarenS, dgreen

Reply | Quote

So is it safe to use our pc’s as normal in the meantime?

Reply | Quote

You should not have a problem using the PCs.
Just don’t run Windows Update until we figure what’s going on.

2 users thanked author for this post.

woody, KarenS

Reply | Quote

Rodger that…..hopefully we find out soon and it is an easy fix either on their end or ours. Thanks again PKCano!

Reply | Quote

Hi EVERYONE:

My windows update stopped working today also here in Riverside, Ca. My sister in Fresno, Ca had the same thing happen today.We both have windows 7 – 64 bit Performed the windows diagnostic and did not help, Followed Canadian tech suggestion and no luck.???? Why am I not suprised with all this happening with Microsoft. Keep us informed, many of us depend on your knowledge to keep us going. Thanks for all you do for us.

Sincerely,
Herb Kelly

Reply | Quote

Sorry everyone forgot to mention My windows update stopped working after I installed the November rollup and important updates when woody  changed to MS – DEFCON – 3, only installed checked updates and no optional. My computer was perfect until this point. Windows 7 SP 1, x 64

Herb Kelly

Reply | Quote

So I guess I’ll just sit tight for now. I was almost tempted uninstall the Nov. rollup (my first attempt at Group A).

CanadianTech, I’m inclined to think you are correct. To think I just had a new hard drive put in and reinstalled Windows 7, here I was thinking my computer will run like new…
sheesh…..

BTW
I’m getting the same message as Karen.
I have a Dell Inspiron desktop windows 7 Home Premioum 64 bit server 2008 R2

1 user thanked author for this post.

Canadian Tech

Reply | Quote

dgreen and others. If you would be interested, I can give you the process I use for re-building PCs within my strategy.

CT

1 user thanked author for this post.

dgreen

Reply | Quote

I had this problem on a desktop but also saw “WindowsUpdate_80248015” “WindowsUpdate_dt000”
Did not use yesterday but it was working Friday night.
After seeing no updates work I did install 64 bit manually
Nov 2017 KB 4048960
Nov 2017 (IE11) KB 4047206 — this one blew up uninstalled and reinstalled
Nov 2017 KB 4055038 (fix for dot matrix printers)
plus Nov MSMRT for November as I skipped 3 months
— all MSMRT does for me is remove the debug menu for Hearts — yes I can catch the system cheating so I use it 🙂
sfc /scannow says it saw and fixed a dll.
I ran this windows-WindowsUpdateDiagnostic.diagcab to see what the MS fix would do, but it undid fix sfc fixed, so avoid that one.
I guess they finally lost their minds and move towards win 10 or else.
The only update on my PC in last 48 hours (it was up) was the MS Security Essentials, nothing else.

No updates for me all of November last was Oct 27.
No the SSDs and HDDs are mechanically fine and no file integrity issues

Reply | Quote

I just did a search for updates and have encountered the same error as twbartender: Code 80248015. Windows update was working fine for me yesterday (3/12).

On 1/12 I installed the Office updates, Security Updates KB4048960 / KB4047206. The strange thing that happened to me though is that MSRT for October was offered again (checked), which I ran, but I didn’t realise until after it was for the previous month. Everything worked as per normal so I didn’t worry about it (it’s not as if this hasn’t happened in the past!).

Had a look at MS Community and found a couple of threads started today

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/window-updates/048f11d8-685a-470c-9369-defc61cb4aa9

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/error-code-80248015/aeae2fcd-100a-4478-8da4-a2b9558c229e

I think those threads will grow once everyone around the world accesses WU.

As PKCano mentioned, it may seem as if this is an MS problem.

 

Reply | Quote

I just noticed the same problem with Windows Update on my WIN 7 Pro sp1 x64 machines.

Don’t know if this is relevant but one hour ago Microsoft Security Essentials automatically updated the definitions to 1.257.1328.0, although it didn’t show up in the update history of Windows Update as it normally would.

If folks are nervous because they haven’t installed November patches you should still be able to download the patches from the Microsoft Catalog and manually install them. Just for kicks I downloaded the Rollup for WIN 7 x64 (KB4048956)from the catalog a couple minutes ago. Slow, but works fine. (I didn’t install it since I’m a group B guy.)

Reply | Quote

My best guess is that the Windows Update failures are related to Microsoft Office 2007 no longer supported. I had expected Windows Update to continue to function but simply not return any MS Office 2007 updates. Instead it appears that Microsoft got heavy-handed (on purpose or accidentally) and makes it appear that your Windows Update is corrupt. Why do I think this? Because I restored to a month old disk image when Windows Update had been working fine, but even after going back in time, Windows Update failed the same way. I downloaded MicrosoftFixit50202.msi and had to run it in “aggressive” mode to reinstall Windows Update. That allowed me to run Windows Update to get the November updates, but I can’t turn on the “Get updates for other Microsoft products” (which had been for Microsoft Office 2007). Unclear whether Microsoft has done this deliberately or by accident.

Reply | Quote

Not sure if your theory is true or not but that wouldn’t explain why WU stopped working for me or my husband because we both have Microsoft Office 2010.

Reply | Quote

Hello!

I too am unable to get updates – I have win 7 64x pro. I am not tech savvy and would rather not do complicated fixing & digging into the innards of my computer unless absolutely necessary.

My question is: Do you think MS will fix this in several days or will we be on our own because win 7 is just about on its way out for MS support?

Reply | Quote

Many others are having this issue.
Found this as a possible cause on the microsoft community website posted 12/4/17
(ie the problem is on the MS update side)

see ArgHereBeDragons post on page 2 top of page

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/error-code-80248015/aeae2fcd-100a-4478-8da4-a2b9558c229e

 

 

2 users thanked author for this post.

Purg2, Microfix

Reply | Quote

ArgHereBeDragons replied on 04/12/2017
This is what i can see.
The authcab file(s) (eg %windir%/SoftwareDistribution/AuthCabs/authcab.cab) contain an XML file called ‘authorization’. There seems to be one for windows update and one for Microsoft update if you have that installed.

There is an element in this file called  ExpiryDate which states:

<ExpiryDate>2017-12-03T11:59:25.5067616-08:00</ExpiryDate>

which depending on your timezone is more or less now.

This lines up with an error from windowsupdate.log namely

DtaStor    FATAL: Service 7971F918-A847-4430-9279-4A52D1EFE18D requested, but it is expired

where that guid relates to MS Update.

Hopefully this means we simply have to wait for MS to update the, er, updater so it will have a new expiry date! I believe in a perfect world the updater will do this automatically once one becomes available. Otherwise hopefully we are supplied with a download link somewhere.

Windows - commercial by definition and now function...

Reply | Quote

BTW I also changed my update settings to “never check…” until this is resolved.
My previous setting was “check but let me choose….”
which would check for updates once a day.

I hope this is a fix that MS will take care of…
sooner rather then later!
Apparently some are having issues with updating MSE definitions also.
sheesh, what a mess!

Reply | Quote

I have the same issue since yesterday , 3rd. ( win 7 x64)

Last known windows update background check was ( in the background ) at 18:something , gmt +1

Since then it stopped and initially presented a screenshot saying that there were no more updates available (green shield).

Trying to run it manually, got error.

The /WER/ReportQueue had reports mentioning an error that was equal to not being able to connect to the remote server.

Turned off , went to sleep. Turned on the pc

Now I get the same error as the OP .

Those are now vanished, and the only reports showing are in /ReportArchive , fresh after today’s startup, with a 80244019.
After a reboot, nothing new in /ReportArchive  (last thing is from the first daily boot) , but still windows update doesn’t work

Reply | Quote

Woke up to the same on both pro versions of W7x64 and W7x86.
Also MSE definitions update error on the W7x64, I then updated defs via mpam-fe on the system ok.BUT, WU was running and fully functional…go figure?!
W7 pro x86 however, WU is not functional at all (service not running, but it IS!)
Good grief..

Stopped WU service via cmd, Cleared SoftwareDistribution, restarted and tried again with still the same results on both systems.

Yesterday Everything was fine..

Windows - commercial by definition and now function...

Reply | Quote

Do any of the messages people are seeing here state WHICH service is not running? I ask because Windows Update requires several services to do its work. The information might be available in the event logs.

FYI, I have several Win 7 systems that got their updates around the middle of November. One is a test VM that I can easily snapshot and revert as needed. I just reconfigured the firewall to allow updates (normally the system can’t reach the servers), started the Windows Update service on it (I normally keep it disabled), and saw this sequence.

The only thing I didn’t have from the November update set, probably because of the timing of when I ran the update, was the the “Servicing Stack Update” (dated September 20, 2016!?!).

Not sure if this helps identify what’s wrong, but it’s a data point. Any suggestions for the next thing(s) I can test here?

-Noel

1 user thanked author for this post.

Elly

Reply | Quote

Noel,

Just saw a POSSIBLE temporary solution. Change your computer time/date to December 1. Recheck for updates. It showed this check went OK. Reset time/date to current time/date. Open Windows update. It shows most recent check as 12-1-2018 @ current time. Recheck for updates. Shows Error 80248015, BUT it also shows last check for updates as 12-1-2018.

It looks like Windows Update on THEIR end is not working. I’ll check again later to see what is going on.

Dave

Reply | Quote

No need to check.

Problem is with Microsoft

4 users thanked author for this post.

Elly, Noel Carboni, Tiernan, Pepsiboy

Reply | Quote

Noel Carboni, anonymous #149436 here.

If I recall you are among those who advised hide KB971033. I wonder if among or across your variety of Win7 systems you have a Home Premium equivalent with or without this item installed, and if that has any bearing on the current problem?

This is an old item, last discussed this recent July. But in July Windows Update still worked, and we are now under new conditions. Can you eliminate this wrong tree for me, so that I might look for squirrels somewhere else?

Reply | Quote

anonymous wrote:

If I recall you are among those who advised hide KB971033. I wonder if among or across your variety of Win7 systems you have a Home Premium equivalent with or without this item installed, and if that has any bearing on the current problem?

I’m sorry to say that I have no Win 7 systems on which I haven’t hidden that update, so I can’t contribute a data point to that thought. But apparently it’s been or being resolved by Microsoft now anyway, so perhaps it’s a moot point.

Regarding Pepsiboy’s comment above about changing the clock: My advice: NEVER intentionally set your computer’s clock back or forward. Some products will invalidate your license if they detect you doing so, most likely because of the legacy of people who have tried to run free trials for longer than intended.

-Noel

Reply | Quote

anonymous #149436 here.

Thanks Noel, for the follow up. If things had not been repaired, then your input would have been a valid data point. It successfully excluded that update from consideration. Because among the field of systems with that update hidden were both clear and afflicted systems.

Today my machine is running cleaner than usual. Thanks again.

Reply | Quote

Deja vu …
https://www.infoworld.com/article/2851796/operating-systems/microsoft-update-fails-with-error-0x80248015-server-2003-and-xp-customers-get-a-cold-shoulder.html
.
https://www.computerworld.com/article/2851530/fighting-with-a-broken-windows-update-part-2.html
.
It took M$ more than 1 week to fix this simple Nov 2014 problem for Win XP SP3 and Win Server 2003 regarding M$’s own set Expiry Date for the authorization of Windows Update.
… In the first place, was there a need for such Expiry Dates.? Doesn’t M$ stop sending important updates when an OS reached EOL.?

Seems, M$ are “forgetting” their older OS which still have to be supported and then took their own sweet time to fix the problem.

Reply | Quote

Well, it states that the Windows Update service is not running, simply.

Bits and windows update service are both running

Reply | Quote

The problem is not your PC. The problem is on Microsoft.

2 users thanked author for this post.

Tiernan, Pepsiboy

Reply | Quote

Yes,

I did realize after reading the post that was linked onto the ms website.
I’ve provided to warn all the chatrooms I’m into, for all that it may be worth anyway.

1 user thanked author for this post.

woody

Reply | Quote

anonymous wrote:

… In the first place, was there a need for such Expiry Dates.? Doesn’t M$ stop sending important updates when an OS reached EOL.? Seems, M$ are “forgetting” their older OS which still have to be supported and then took their own sweet time to fix the problem.

ditto

2 users thanked author for this post.

HiFlyer, woody

Reply | Quote

There’s no doubt a reason for the ExpiryDate (although none I can think of, at the moment). What I wonder is why the ExpiryDate isn’t set for the Win7 end of service date – and why it wasn’t changed years ago…

1 user thanked author for this post.

Tiernan

Reply | Quote

Hi Everyone:

My windows update started working again at (9.00 pm December 4, 2017. Windows 7 sp 1 64 bit

Sincerely,
Herbert Kelly

Reply | Quote

After running into this on 2 machines this morning, I renamed the Software Distribution folder and restarted the update service and got it working. After the fact, I saw the older AskWoody posts about the problems that come with that solution regarding update history, etc. I have these machines set to check for updates, but not install them. Will the workaround I used have any effect on that setting going forward? Just want to know how to handle updates in the future.

Reply | Quote

What you did for a “workaround” really wasn’t one. It was not necessary.

The problem was on Microsoft’s end. They expired a file that should not have been expired. So you should not have to change anything you have been doing with updates in the past.

Reply | Quote

https://answers.microsoft.com/en-us/windows/forum/all/cant-install-windows-updates-error-code-80248015/61f1309b-90f3-4c5f-bcc3-63440155577a?auth=1

Per Link above I JUST Fixed “Check for Updates” WU Error Code 80248015 by Stopping WuAuServ (Admin Cmd Prompt) and going to C:\Windows\SoftwareDistribution and Re-Naming it  w/extension  ( .Sdold ). Did a Re-Start. WHEN WU shtcut First Clk’d it presented SAME Error Screen – BUT – when Check for Updates was Clk’d the Process Started. A NEW SoftwareDistribution Folder results (the old, Re-named on is 1+ GB, so you can Delete WHEN Working WU confirmed). Hope this helps someone, albeit Error Code likely different. You LOSE Update History when you Rename SoftwareDistribution Folder. SAVE File IF you know HOW.

EDIT 12/4  12:34 CDT: After W7-64 Rollup install and TWO MORE RE-Starts my System is back to Normal in spite of the following: I JUST RE-Installed W7-64 Rollup KB 4048957  after several posted – OK with theirs – and as Prior – Opening JPG, PDF, DOC, XLS Documents from desktop ShtCuts Takes FOREVER, as Does CLOSING them. Opening Folders with Files is slightly delayed and Closing is OK. Made Macrium Image just prior to Rollup Inst. Snipping Tool Save As is very SLOW.

No LINK in this Blog allows Rt Clk/ Open in New Tab = Blank Screen.                               Could we ever login and Stay on the Same Pg vs navigating back to where we were when Login started?  FYI

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

Thanks for all the information here regarding this problem.

Reply | Quote

Before I read Woody’s article today I found this fix – https://answers.microsoft.com/en-us/windows/forum/all/cant-install-windows-updates-error-code-80248015/61f1309b-90f3-4c5f-bcc3-63440155577a?auth=1

It works, but you lose your update history, although all updates still show up in Control Panel\Programs and features\Installed updates.

Steve Cohen

1 user thanked author for this post.

woody

Reply | Quote

Hello, Portugal user here and I just have this exact same problem, same screen and same message box when I press to check for updates, I normaly like to wait 2/3 days after woody gives the heads up to see if no other bugs pop up. My machine is running Win7 Pro. MSE is updating fine tough (guess is independent from WU). So what do you guy recommend? Should I manually install the roll up (Im on group A) or should I just wait it out? I would appreciate if anyone could there me where to get the monthly roll up file to install manually in case that is the recommend course of action.

Reply | Quote

I’m having a hard time with this site!!  It won’t let me log in.

Hopefully this post will get through.

I found a temporary fix for the windows update issue.  I found it on the following site.

http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/

you have to go to update settings and uncheck give me updates for Microsoft products.
I did and my checking for updates worked without a problem and was able to install today’s MSE definitions.

 

apparently the fix comes from someone in Germany.

Reply | Quote

Seems that aside the temporary workaround of moving back the DATE, there’s another trick that allows to temporarily run again Windows Update

http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/

Aka, deselecting the option to search for other Microsoft products.

This hints that the expiry date is important for the “other” products, not for the OS updates… but anyway… why …

Reply | Quote

Anonymous #149436 from above here, again.

I have read about the Expiry issue, but do not understand how that means the Windows Update server/service/process/result continues to work for me and approximately half of Woody’s readers even today. And I have synchronized system clock to NIST.gov. I even verified that by manually changing time to a future hour in an elevated command line, then using the Timesetting GUI to check Internet Time, and it snapped back immediately.

I would have skipped this topic, except I think we have a barking dog at the wrong tree. And Microsoft gives us many trees to bark about. I say this because while the Windows Update GUI itself is fully functional, now the MSE GUI returns a nearly identical code 80248014. That is near enough that I am willing to think it is related. Why one repaired but the other not?

I intend to perform the same ‘reset’ as described by Canadian Tech a second time, to determine if MSE will properly check for updates. Incidentally, the magic is in the renaming of folders, thereby hiding them from the too smart for itself system. If you are doing this for a second (or more) time, you will need a new folder name each time. Duplicate folders can eventually be manually deleted, but it is a good idea to keep track of them until normalcy has returned.

Reply | Quote

Anonymous #149436 from above here, again, replying to self to report result.

Easily predictable, same result. Some evidence and conclusions:
Windows Update GUI continues to operate normally;
Forcing the process to recreate these folders contents eliminates error 80248015.
System clock is accurate to NIST;
expiry date is a problem, Microsoft is incompetent, but that doesn’t matter here.
MSE GUI still returns same error 80248014;
this error is not repaired using this method.
My settings already set to Receive Updates for Windows Only;
no conclusion.

New conjecture: because I have to rehide unwanted updates after having eliminated my prior list, the update number KB971033 is jumping out to me because it stands alone as important and checked, while four other unwanteds are on the optional/recommended list unmarked.

New Question: Is there an opinion on this item, KB971033, as it pertains to this error 80248014?

Usual thanks, and respect to all involved.

Reply | Quote

Here’s a workaround that works for the windows update issue.

I did it and it works!!!

http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/

you have to go to update settings and uncheck give me updates for Microsoft products.

I did and my checking for updates 2 times worked without a problem and was able to install today’s MSE definitions.

apparently the fix comes from someone in Germany.

Reply | Quote

I strongly recommend setting WU to NEVER, leaving it at that setting permanently. It is the only sure way of gaining complete control over the WU process. The process (WU) has become unpredictable, unreliable, and just plain erroneous so much of the time, that Woody’s MS-Defcon rating is almost always at 2.

CT

1 user thanked author for this post.

dgreen

Reply | Quote

Mmmm. I have been sitting here reading all the panic and hysteria and wondering how much it would actually bother me if WU were permanently out of commission – not that I think it will be: my guess is that MS are just twiddling their thumbs, hoping to convert a few more reluctant users to W10. After all, I only turn WU on once a month to download a handful of updates it is easier to get that way. Admittedly, it is a pain updating Microsoft Office from the catalogue, but I did it for a while when I had WU issues (anyone remember when it took hours and even days to download W7 updates via WU?). I have come to the conclusion that I can probably manage without it – and keep my system up-to-date – without having a nervous breakdown. But then I’m in Group B – the ‘Losers’ Group – and we have such a hard life, and all the wrong priorities! 🙂

1 user thanked author for this post.

Elly

Reply | Quote

I’m dgreen the one who posted the “workaround” above.  This site wouldn’t let me log in.

1 user thanked author for this post.

woody

Reply | Quote

dgreen posting
I used the above workaround and it worked perfectly.  No issues whatsoever.
I just did a 3rd windows check and it’s running fine.  I’m not going to push my luck however.

Reply | Quote

anonymous wrote:

Hello, Portugal user here and I just have this exact same problem, same screen and same message box when I press to check for updates, I normaly like to wait 2/3 days after woody gives the heads up to see if no other bugs pop up. My machine is running Win7 Pro. MSE is updating fine tough (guess is independent from WU). So what do you guy recommend? Should I manually install the roll up (Im on group A) or should I just wait it out? I would appreciate if anyone could there me where to get the monthly roll up file to install manually in case that is the recommend course of action.

Others have mentioned that they might wait for the update server to reset.  Or try this.

https://www.catalog.update.microsoft.com/Search.aspx?q=2017-11%20Security%20Monthly%20Quality%20Rollup%20for%20windows%207

Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

Reply | Quote

A way around this seems to be to change the date to before 3/12/2017, say 1/12/2017. Then go to the windows update box and untick the ‘Microsoft products’ update box. and ok it at the bottom. Then close it and open the windows update again, you should see you can now check for updates as normal, and if you then put the date back to normal, it will still do the updates as before. I think something went wrong or timed out on 3/12/2017…somewhere…

Reply | Quote

Hello, still investigating but it appears this is only affecting stand alone systems. All of my systems on the domain reporting to WSUS are not getting this error. I’ve only been able to check a handful of systems but this is what I’m seeing so far.

Reply | Quote

Wow, thanks so much for this information.  I was wondering what went wrong yesterday when I could no longer connect to Windows Update on my Windows 7 Professional machine.

Reply | Quote

Broken for me as well even though the service shows as running. Good job, microsoft! Your incompetence never fails to surprise. Not that i use update much as i’m in group b and regarding that… has anyone tried installing the security only updates? Any issues? I’ve still yet to install november and wondered if it was wise to do so at the moment, provided that is even still possible.

-T

Reply | Quote

anonymous wrote:

Broken for me as well even though the service shows as running. Good job, microsoft! Your incompetence never fails to surprise. Not that i use update much as i’m in group b and regarding that… has anyone tried installing the security only updates? Any issues? I’ve still yet to install november and wondered if it was wise to do so at the moment, provided that is even still possible. -T

I did install both november patches ( group B ) this morning, with the windows update issue already hitting me since last night.

I had 0 issues with adding the patches ( I’ve skipped the dot matrix fix, i don’t have such printers ), so feel free to go ahead

Reply | Quote

I got the 80248015 error early\mid-afternoon yesterday, Dec. 3. I had just checked for updates and was notified that 4 Windows updates, a .NET update, and a half dozen or so Office 2007 and 2010 updates were waiting. I got the error immediately when I tried to download and install these updates.

When I couldn’t find any reports of others experiencing this problem with the November updates I assumed I was alone. I searched on the error and found and applied the solution to rename the SoftwareDistribution folder.

That ‘fixed’ Windows Update but it wiped out my WU history, didn’t download any Office updates, and removed the WU settings check box to check for other Microsoft products. So I did another round of searching on this new problem but none of the solutions (generally altering settings in IE 11) worked for me. And that is where I am now.

So I was happy to discover today that it wasn’t just my PC afterall.

Now I am waiting to see if and when Microsoft will fix this problem (how can they roll out an update to fix WU if WU is broken?). And I’m hoping I can reverse the renaming of the SoftwareDistribution folder and the changes I made to IE11 and put things back the way they were. If not I’ll have to restore from my last image . . .

Reply | Quote

Noticed a few references to unchecking “give me updates for other Microsoft products” as a workaround. Use this workaround with caution, once unchecked this option will disappear from “Choose your Window Settings”. To get the option back there used to be a MS MrFixit. Of course there still is a registry fix and some other solutions, but they may be too difficult for some individuals. On 11-1-16 Woody posted how to get the option back.   https://www.askwoody.com/2016/how-to-restore-give-me-updates-for-microsoft-products/

1 user thanked author for this post.

Elly

Reply | Quote

From MS Forums

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-7-update-search-stops-with-0x80248015/536d2025-280c-41e2-a6c7-608c3dadd833

authcab.cab is expired. This effects all microsoft OSes still getting update up to windows 7 (including xp embedded)

http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/
<h2>What stands the error for?</h2>
If you search for the error on the Internet, you can quickly find indications that time, date or the time zone are incorrect (see e. g. here). But I was able to rule it out very quickly.  Then I visited my blog post Tip: Windows Update error code 0x8024xxxx list to decode error 0x80248015. It stands for WU_E_DS_SERVICEEXPIRED – An operation did not complete because the registration of the service has expired.

Reply | Quote

Well the screams from around the world got the job done and WU seems to be working again. I came to see what new posts were here on Woody’s and low and behold the Windows Update icon had returned to my task bar. When I click on it I get the normal looking box with all the updates waiting that were there before all this mess started. Thank you to everyone who posted with not only advice to help solve the situation but those who posted to say they too also had the problem so that myself and others knew that we weren’t alone.

Reply | Quote

Ditto here. The windows update service is up and running again. It can be verified by going to C:\Windows\SoftwareDistribution\AuthCabs\authcab.cab file.  The expiry date in the authorization.xml file now shows 2025-07-01T00:00:00.0000000-00:00.

EDIT html to text – may not appear as intended

Reply | Quote

Fixed!

My authorization.xml now has:

CabVersion 8110
IssuedDate 2017-12-01T00:00:00.0000000-00:00
ExpiryDate 2025-07-01T00:00:00.0000000-00:00

Security Essentials auto-updated to:
Definitions created on 12/04/2017 at 07:20 PM
Definitions last updated 12/04/2017 at 10:27 PM [when I logged on; US Pacific time]
definition versions: 1.257.1398.0

And a Windows Update ran normally.

Reply | Quote

I got same error (Windows Update cannot currently check for updates, because the service is not running) using Windows 7 Enterprise 64Bit today 5 Dec 2017

Then changed date to 1dec 2017 rebooted and ran updates again

Updates worked as normal no errors. when it finished I then changed the date back to today 5Dec2017

Error now gone, updates are working correctly

Hope that helps

JM

Reply | Quote

**** Changing the Date to (1 Dec 2017) WORKs *****

So does going to Windows updates, change settings,
On important updates change it to
[Never check for updates (not recommended)]

Now go back and run [Check for updates] again

When updates have installed then change the update settings back

I am using Windows 7 Enterprise 64Bit
Hope that helps

JM

Reply | Quote

anonymous wrote:

Before I read Woody’s article today I found this fix – https://answers.microsoft.com/en-us/windows/forum/all/cant-install-windows-updates-error-code-80248015/61f1309b-90f3-4c5f-bcc3-63440155577a?auth=1 It works, but you lose your update history, although all updates still show up in Control Panel\Programs and features\Installed updates.

Steve Cohen

IF Renaming SoftwareDistribution was YOUR fix and Update History is lost as per here, my Installed Updates List has 11 Entries of the SAME UPDATE in the 7/15 Group, one more in August, and does NOT match Update History.

IF you Re-Named the SftDist Folder.Sdold  & haven’t DELETED it, Does ANYONE know IF you can go in there and Find the Old Update History File and Copy-Paste into the newly Created one?

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

I tried this and it didn’t work – but that was before MS fixed things.

It doesn’t hurt to try:
Rename the current new (fixed) SofrwareDistribution folder to SoftwareDistribution.1712
Rename the original file (unfixed .Sdold) back to SoftwareDistribution

See if that is OK. If not, reverse the procedure

2 users thanked author for this post.

CraigS26, woody

Reply | Quote

For those of you who wiped the datastore and lost the MS Update “Give me updates for other MS products,”

HERE ARE THE INSTRUCTIONS FOR GETTING “Give me updates for other MS products” BACK.

 

1 user thanked author for this post.

woody

Reply | Quote

New issue
Started computer from OFF.

Checked Updates and it indicated you should check reqularly for updates (red warning). The install updates button was missing.  Now system notifier says to check for latest updates and on execute says WUPDATE service is not running. Rolled clock to Dec 1 .  That does enable ability to download did that yesterday as well but put clock correct and ability removed.

What I noticed / experienced today was :

If I set the clock back give me updates and give detailed notifications reappears.  When I correctly set clock they disappear.  Change clock to before Dec 1 or 2 and it works even letting MSSE get latest definitions.  I do have Visio 2007 but use office 2010. 2007 was EOL I believe, big deal Visio still works.

I installed 2 updates for MSSE only on 2 separate win update launches.  I then set the clock to correct day.  The win update is now working for me.  I did a restart of PC and it still works.  I just did a shutdown and restart and it is still working.  Again I only installed MSSE definitions today.  I installed one last night along with Office updates but it was not fixed until doing what I mentioned above .  Hope this helps somebody.  And hope it continues to work for me.

Reply | Quote

Wow, update issue in Windows 7 issue finally fixed for me. It took the steps listed by guenni as well as then running the Windows 7 Update Troubleshooter and then having the troubleshooter flag this issue and then using method 2 in the Microsoft article. Now, I can finally update Microsoft products again in Windows 7.

http://borncity.com/win/2017/12/05/windows7-fix-broken-update-error-0x80248015-12-4-17/

https://support.microsoft.com/en-us/help/900936/error-code-0x8024402c-when-you-try-to-install-updates-on-windows-updat

I hope this may benefit other users as well.

Reply | Quote

opti1 wrote:

I got the 80248015 error early\mid-afternoon yesterday, Dec. 3. I had just checked for updates and was notified that 4 Windows updates, a .NET update, and a half dozen or so Office 2007 and 2010 updates were waiting. I got the error immediately when I tried to download and install these updates. When I couldn’t find any reports of others experiencing this problem with the November updates I assumed I was alone (silly me). I searched on the error, found and applied the solution to rename the SoftwareDistribution folder. That ‘fixed’ Windows Update but it wiped out my WU history, didn’t download any Office updates, and removed the WU settings check box to check for other Microsoft products. So I did another round of searching on this new problem but none of the solutions (generally altering settings in IE 11) worked for me. And that is where I am now. So I was happy to discover today that it wasn’t just my PC after all. Now I am waiting to see if and when Microsoft will fix this problem (how can they roll out an update to fix WU if WU is broken?). And I’m hoping I can reverse the renaming of the SoftwareDistribution folder and the changes I made to IE11 and put things back the way they were. If not I’ll have to restore from my last image . . .

I can confirm that if to fix the 80248015 error you followed the procedure to rename the original SoftwareDistribution folder to Sdold (or something else), then let Windows create a new SoftwareDistribution folder, and you got back your functioning Windows Updates but lost your Windows Update history and your ability to get MS Office Updates, you can back out these changes (rename the new SoftwareDistribution folder to Sdnew or something else, rename the Sdold folder to SoftwareDistribution) and Windows Update will be back to normal as if none of this ever happened. Phew.

Reply | Quote

High champs,

I solved the problem today in following Woody’s advice and just set back the Windows 7 Systems Date to September 2017.  After doing so I restarted my computer and then used the Windows Update program. As expected, I could successfully watch for updates. Then there was of course the famous error message, but it did not matter. Meanwhile my busy computer had automatically downloaded another MS software authorization cab file with another expiry date allocated someplace in 2025!

Then I re-set the systems date to today (2017-12-14) and rebooted my computer. Looking again for windows updates the program told me that there were 5 important updates waiting to be downloaded.  Meanwhile I did the updating and Windows Update works fine again, hopefully up until 2025?

Best Regards

Berni of Germany

Reply | Quote