Getting Windows 7 Update error 80248015? You are not alone - gHacks Tech News

Getting Windows 7 Update error 80248015? You are not alone

If you run a device that is powered by Microsoft's Windows 7 operating system, you may have noticed already, or not, that the system's update functionality may be broken completely.

A check for updates returns the error message "Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer".  The error 80248015 is displayed, but anything you try to resolve the issue on your end fails.

A restart does not resolve the issue, and the error may be thrown even if you downloaded updates just fine the other day.

A thread on Microsoft's Answers forum indicates that the issue is widespread. It is unclear if all Windows 7 systems are affected by the issue, or if only a subset of systems are affected.

windows 7 update error 80248015

Woody on Computerworld suggests that Microsoft broke updating on Windows 7. He suggests, based on a user report on his Ask Woody website, that Microsoft may have missed updating the Expiry Date of a file, and that this may be the cause for the update issues.

The file is authorization.xml, which you find in c:\Windows\SoftwareDistribution\AuthCabs\authcab.cab.

Apparently, changing the system's date to one that is older than 03.12.2017 fixes the issue temporarily, but the only other option that Windows 7 users appear to have at this point is to wait for Microsoft to publish an update that corrects the issue.

Update: Günter Born discovered that disabling "Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows" in the update settings fixed the issue on his end. You may want to try this to see if it resolves the issue for you as well.

This is not the first time that Windows users get hit with the Microsoft Update error 80248015. It happened three years ago in November 2014 to Windows XP and Server 2003 customers who could not use Windows Updates anymore either.

Back then, only some machines were affected by the issue while others had a different expiry date so that updating worked fine on those.

A search on the Internet returns multiple references to the Windows Update error 80248015, some of which dating back nearly a decade. While the error may be caused by system administrators disabling Windows Update functionality, this is apparently not the case for the current issue.

Closing Words

It is not really flattering for a company like Microsoft if errors like 80248015 happen frequently. Windows 7 is still supported, and it seems amateurish if the issue is indeed caused by Microsoft forgetting to update a file on the system.

To be fair, we don't know if the file is causing the issue, but it is clear that its expiry date coincides with the beginning of the issue.

Summary
Getting Windows 7 Update error 80248015? You are not alone
Article Name
Getting Windows 7 Update error 80248015? You are not alone
Description
If you run a device that is powered by Microsoft's Windows 7 operating system, you may have noticed already, or not, that the system's update functionality may be broken completely.
Author
Publisher
Ghacks Technology News
Logo

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

Comments

  1. Hard Right said on December 4, 2017 at 6:54 pm
    Reply

    Wonder how the HindooSoft fanboyz will explain this?

    1. DVF said on December 4, 2017 at 7:43 pm
      Reply

      When I changed system date to earlier than 3/12/2017 now get new Windows Update error 80072F8F indicating system clock needs synchronizing.

      1. Anonymous said on December 4, 2017 at 9:06 pm
        Reply

        I changed date the 01/12/2017 and it worked , the 3 dec is the expiring date

    2. Manuel said on December 5, 2017 at 11:23 am
      Reply

      It’s not a bug, it’s a feature to simplify your decision to upgrade to Windows 10 for *FREE*

  2. Paul Frank said on December 4, 2017 at 7:25 pm
    Reply

    My windows 7 update did the same thing. Now it just shows a blank white screen when I go to update.

    1. Sophie said on December 4, 2017 at 8:26 pm
      Reply

      Microsoft are now so staggggggeringly inept. It is so shameful, and I have not got words for what they have become. I work in software development, and I test everything so deeply and thoroughly. What’s to blame? Why has it got so bad? Do they just not care at all any more?

    2. Liam said on December 15, 2017 at 1:49 am
      Reply

      That happened to me too.

  3. Günter Born said on December 4, 2017 at 8:06 pm
    Reply

    @Martin: a better workaround will be to uncheck optional updates for Microsoft components, as I described within my blog post: http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/

    1. Martin Brinkmann said on December 4, 2017 at 9:02 pm
      Reply

      Thanks Günter, I have added an update.

  4. Yuliya said on December 4, 2017 at 8:31 pm
    Reply

    This folder c:\Windows\SoftwareDistribution\AuthCabs\* is empty for me. My Win7 PC is up to date – Simplix UpdatePack7R2 FTW!!

  5. martial said on December 4, 2017 at 9:08 pm
    Reply

    3/12/2017 is the expiring date ,I changed 1/12/2017 and it worked

  6. dgreen said on December 4, 2017 at 9:13 pm
    Reply

    I used Gunter’s workaround and it worked perfectly. I was able to update my MSE definitions. I also did 2 windows update checks and they both went smoothly.
    I also had changed my settings when this first started late yesterday afternoon to “never check” and I will leave it that way until this issue is resolved.
    I tried to post on askwoody’s site but the site is having problems and I wasn’t able to get in.
    I’m running Windows 7 Home Premium 64 bit 2008 R2
    Just recently had a new hard drive installed and Windows 7 was reinstalled. (via Staples).

  7. sasa said on December 4, 2017 at 10:42 pm
    Reply

    I solved thanks to the blog of Gunter…thank you so much

  8. Mike Lynch said on December 4, 2017 at 10:51 pm
    Reply

    MS could be attempting to do to Windows-7 Users what they did they did to Vista Users, NO ACCESS TO UPDATES, regardless of the date!

  9. pHROZEN gHOST said on December 4, 2017 at 11:19 pm
    Reply

    As we approach the end of life, there are going to be Windows 7 and 8 hiccups as MS concentrates most of its effort on Windows 10. LIke any older product, (a ’69 Olds Cutlass for example), don’t expect the manufacturer to support it for ever.

    If you don’t want to move up to Windows 10, move onto something else”

    various flavors of Linux
    DOS
    CP/M

    Or, why not give up on computers and stick to a cell phone. They seem to be where most people are these days.

    BTW … Let’s see how many horn-backed green trolls bite on this one.

    1. Manuel said on December 5, 2017 at 11:30 am
      Reply

      “As we approach the end of life” Windows 7 is supposed to receive security updates and bugfixes till 14th January of 2020. That’s still a lot of time to go.

      1. pHROZEN gHOST said on December 5, 2017 at 7:39 pm
        Reply

        Manuel and others with similar sentiments,

        I do not work for MS. I am not a choirboy for MS. I don’t really care what OS anyone else uses.

        I am terribly sorry that you cannot understand that we REALLY ARE approaching EOL on your personal choice of OS. MS is changing. Life is about change. That sucks. I am so very sorry that I’m a Can-EH!-dian.

        You don’t have to migrate to Windows 10 like most of us. You do have options if you are willing to embrace change.

        1) Get rid of your computer and use your cell phone like many others.
        2) Migrate to OS/2, DOS or CP/M (needs a Z80 processor with at least 64KB of RAM)

        Have a nice day eh!

  10. AK said on December 4, 2017 at 11:21 pm
    Reply

    W7 64-Bit & W7 32-Bit.

    WU Jammed on Red ?

    Make a note of your ‘Change Settings’, settings.

    Change Settings to : ‘Never Check For Updates’.
    Remove ‘X’s’ from all the boxes below. ‘OK’.
    ‘Check For Updates’ : Working Again.

    Change Settings back to : Your Customization.
    ‘Check For Updates’ : Still Working.
    Well worth a punt.

    AK

    1. Brian said on December 10, 2017 at 2:40 pm
      Reply

      Thanks worked for me.Brian.

    2. AB said on December 14, 2017 at 9:15 pm
      Reply

      It worked perfectly for me too. Thanks AK !

  11. martial said on December 4, 2017 at 11:33 pm
    Reply
  12. Mola Ram, CEO Microsoft said on December 5, 2017 at 2:28 am
    Reply

    I haven’t updated Windows in 3 years.

    1. ilev said on December 5, 2017 at 4:43 pm
      Reply

      Same as I.

  13. dante said on December 5, 2017 at 2:32 am
    Reply

    It’s their way of forcing upgrades. Notice your PC gets really really slow booting up after an update when Microshaft wants you to buy a new OS?

  14. Coriy said on December 5, 2017 at 2:45 am
    Reply

    Sorry, but Günter’s workaround is a no go for me, and I suspect a lot of people.
    I don’t have the entry for “Give Me Updates for Microsoft Products…” on my Windows 7 computer.
    Also I got a different error, 0x80070490, when I tried a Windows Update Diagnostic FixIt from MS.
    That one requires SFC /scannow as a possible repair.

    Also, I use Microsoft Security Essentials and its update capacity is unharmed by this M$nafu.
    Ah, the Life of a Windows User…

    P.S. I used the Dism++ program in an attempt to fix the error. It didn’t work, but it freed a lot of cruft including 1.3 GB of file in the Software Update folder when it collapsed the DataStore.edb file.

    1. Coriy said on December 5, 2017 at 2:56 am
      Reply

      I tried another (so that’s two) old Windows Update repair from MS, and that did the trick along with the other attempts.
      So I have a leaner system and now have to tell update to NOT install optional updates that I once told it not to install.
      Ah, M$nafu…

  15. Stefan said on December 5, 2017 at 3:32 am
    Reply

    I use ‘WSUS Offline installer’ to do all updates and (if i am not mistaken) You can choose – ONLY SECURITY UPDATES via it as well as downloading the updates from Microsoft’s Windows Catalog online.

    http://download.wsusoffline.net

    I have all Windows Update components disabled and also blocked via a 3rd party firewall and never let them go online.

  16. John said on December 5, 2017 at 6:57 am
    Reply

    Seems to be back up & running now

  17. Eien said on December 5, 2017 at 8:11 am
    Reply

    I guess I’m lucky then i don’t have such problem.

  18. nik said on December 5, 2017 at 9:54 am
    Reply

    S A B O T A G E
    A
    B
    O
    T
    A
    G
    E

  19. Belga said on December 5, 2017 at 9:54 am
    Reply

    No error message for me, but the constant return of all hidden updates (important and optional) for a long time.
    This happens after I have made each “security update only” downloaded through Microsoft catalog.

  20. jmwoods said on December 5, 2017 at 10:23 am
    Reply

    I was able to fix it earlier by running the freeware tool Windows Update MiniTool.

    Didn’t install any updates, just did a check, and closed the program when it was done.

    Was then able to open and use Windows Update.

    The expiration date in authorization.xml was bumped up to 2025.

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

  21. Ben said on December 5, 2017 at 11:38 am
    Reply

    This worked for me . It is tested on one PC (Windows 7 Ultimate).
    You can find this information on many internet sites and you can do it in different ways.

    Open Command Prompt in elevated mode.
    1. Stop Automatic Update Service: Net stop wuauserv
    2. Find Windows\SoftwareDistribution\
    3. Rename SoftwareDistribution
    4. Start Automatic Update Service: Net start wuauserv
    5. That’s it.

    This morning I had no problems and I could run updates again.

    1. JimV said on December 5, 2017 at 9:52 pm
      Reply

      Yep…that’s the tried-and-true approach that worked for my Win7Ult desktop that started that wonky WU behavior on Monday. Only problem is losing all of the archived WU database entries, but c’est la vie…

  22. Lynne said on December 5, 2017 at 12:02 pm
    Reply

    I tried numerous solutions to this problem on and off all day. I found this website and tried Gunter’s fix. All I did was uncheck the optional update box on the windows update screen. It worked! Windows update searched, downloaded, installed in less than 10 minutes. So easy. Thank you.

  23. Mike J. said on December 5, 2017 at 3:53 pm
    Reply

    I don’t mess with updates either.

  24. Mike J. said on December 5, 2017 at 3:54 pm
    Reply

    I don’t bother with updates either.

  25. jasray said on December 5, 2017 at 5:16 pm
    Reply

    Interesting–if I install Classic Shell on Windows 7, flip-flap with a Rainmeter “clock” skin, and use MUT, WSUS, and Simplex, all my problems disappear.

    Third party tools! Miracles!

  26. Laurent G said on December 5, 2017 at 5:27 pm
    Reply

    Hi all,

    I had the issue. Not error 80248015, but unable to search for updates (“Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer”)
    I tried to stop then restart the WinUpdate service => no result.

    Then I set, a proposed by some, the date to December 1st, and forced search for updates.
    Worked fine.

    Then I reset back the system date to today, December 5th. And have been able to search again for updates.
    Issue “seems” to be cleared by these operations…. at least in my own case.

  27. James D said on December 5, 2017 at 7:09 pm
    Reply

    Why do people use shty windows update instead of prepacked Simplix Update packs is above me. I get that average Joe doesn’t know anything but people who visit such forums and read such articles should have already do an analythics search about how to optimize windows 7.

    1. Lynne said on December 5, 2017 at 10:22 pm
      Reply

      I guess we are just not too smart, James. By the way, the term is ‘beyond me’ not ‘above me’.

      1. jasray said on December 5, 2017 at 10:44 pm
        Reply

        No, I take it to mean “above me” meaning everyone else knows something James doesn’t know. Everyone is “above” and “beyond” him in knowledge and understanding–even though he doesn’t seem to have any problems with updates like the other sudo-masters have [or is that pseudo]. In other words, it’s easier to complain [except in the case of Classic Shell] about Windows rather than use a third party program and move one with life [or is that on]. One is All and All is One.

        Maybe MS is having problems with the structural dynamics of flow?

        Naturally, anyone using Linux, as a few have indicated, don’t have problems with program updates or system updates or ransomware or . . . .

      2. Lynne said on December 5, 2017 at 11:42 pm
        Reply

        Thank you Jasray, I stand corrected. I admitted I’m not too smart.

  28. Julian Alarcon said on December 5, 2017 at 8:45 pm
    Reply

    Same issue in Windows Server 2008

  29. iwk said on December 5, 2017 at 9:12 pm
    Reply

    It seems problem is bigger. My USB 3.0 devices stops working (including keyboard and mouse!) and Intel(R) USB 3.0 eXtensible Host Controller shows error “Windows cannot verify the digital signature for the drivers required for this device“. Error 52. After booting with F8 and Disable driver signature enforcement it works…until reboot. Some permanent fix?

  30. Ben said on December 6, 2017 at 4:03 am
    Reply

    I had the issue on Dec 4, but on Dec 5, my Windows 7 notified me that updates were available (only for Excel). I downloaded it and installed it through Windows Updates without issues.

  31. Joseph said on December 6, 2017 at 9:39 pm
    Reply

    I noticed that my MSE In Vista Home stopped updating at that date (the 3rd). So after a lot of difficulty i was able to change the expiry date to the 1st .MSE updated immediately after that. Tried to update Vista (and the expiry date changed to 7 /2021. So if your security essentials wont update ,you know what to do. Change the date, save the file authorization.xml as all files /.xml. Update MSE then try to update Vista.(MS just came out with a statement that said the date will correct itself in the authorization.xml when you try to update. (remember to stop windows update at cmd line- net stop wuauserv – after you save it then – net start wuauserv to start it.

  32. DGC said on December 6, 2017 at 11:11 pm
    Reply

    The Problem affects ALL WIN-7 Machines. The Problem is definitely tied to the authorization.xml file. The update when it becomes available shows an issue date of 2017-12-01 and an expiration date of 2025-07-01. Do not know what other files may be affected, but the above file is definitely part of the problem. Once again THANK YOU M$ for being such a bunch of aholes.

  33. rChaz said on December 7, 2017 at 9:23 am
    Reply

    Thanks AK! That also worked for me. I wasn’t initially showing the option “Give me updates for Microsoft products and check”…, nor did I have the option to “Show me detailed notifications when new Microsoft software is available”…, so I couldn’t use Günter’s workaround.

    After resetting to “Never check for updates”, OK, then reset back to my original “let me choose”, everything was working again, and I also had the additional 2 options above restored.

  34. TonyCzar said on December 7, 2017 at 8:19 pm
    Reply

    Eventually, my Windows Update window just went blank white. After reinstalling Windows Update at-

    https://www.microsoft.com/en-us/download/details.aspx?id=49540

    … at least I was able to see the error message again.

  35. DGC said on December 7, 2017 at 9:00 pm
    Reply

    M$ has still not pushed a FIX for this. Here is a FIX THAT DEFINITELY WORKS on ALL WIN-7 Machines.
    Change the System Date (change date and time) to 11/30/17. Reboot the P/C or Laptop. In control panel go to Windows Update and check for updates. Install all updates listed (optional updates excluded). Restart the P/C or Laptop, and once again check for updates. When it says Windows is up to date, change the system date back to the current date. VOILA, problem corrected. If you open the authorization.xml file, in the AUTHCABS folder, you will now notice the ExpiryDate 2025-07-01. This fix has worked on ALL WIN-7 Machines I have used it on. Happy fixing :)

  36. A different Martin said on December 7, 2017 at 9:37 pm
    Reply

    Hey, Martin — I wouldn’t mind seeing an article comparing WSUS Offline Update with Simplix, KUC, and any other third-party Windows updaters out there. The native Windows Update function has screwed up (and screwed users) often enough in the past couple of years that interest in third-party solutions has probably gone up considerably. I’m reasonably happy with WSUS Offline Update (which I learned about from you), but when commenters I respect tout, for example, Simplix, it piques my curiosity.

  37. snb said on December 15, 2017 at 6:30 pm
    Reply

    1. Disable Microsoft Update.
    2. Reboot system (!)
    3. Scan and install updates from Windows Update.
    4. Reboot system.
    # now authcab expiration has been updated to year 2025.
    5. Enable back Microsoft Update.
    6. Scan for updates.
    # voila, everybody happy.

    Credits to “DGC” (https://www.ghacks.net/2017/12/04/getting-windows-7-update-error-80248015-you-are-not-alone/#comment-4304303), his idea is functional too.

  38. Rosie said on December 24, 2017 at 4:22 pm
    Reply

    Aha! My old hard drive had a couple of mini-crashes on December 21. I created a system image, bought a new hard drive and applied the system image to the new hard drive. I knew that there might be corrupted files in the system image, so I checked carefully to make sure everything worked. Two things didn’t: FreeCell and Windows Update. I fixed the FreeCell by borrowing a DLL from a friend, but the Windows Update issue baffled me. I tried everything! So it’s quite a relief to discover that the problem started on December 4 and has nothing to do with my hard drive at all.

  39. Rosie said on December 25, 2017 at 6:36 pm
    Reply

    Okay, I posted that last reply a bit too soon. When I looked more closely at the Windows Update log, I discovered that I’d been getting error 80248015 December 4-22. Then on December 22 (the date I installed the new hard drive) I started getting error 8000247 instead. I gave up working on this for the time being and moved on to another project that involved doing a search in MS Outlook for a specific e-mail. This is when I discovered that my indexing had vanished and would not come back. In order to fix the indexing issue, I downloaded and installed the latest driver for Intel Rapid Storage Technology. That allowed me to start the computer on rebuilding the indexing. At some point during this process, Windows Update revived, found new updates and – as it usually does – asked me if I wanted to download and install them.

    When I was looking for fixes for my Update problems, nowhere did I read any suggestions about updating the IRST driver. But that’s what seems to have done the trick. Not sure it it was the updated IRST driver itself or the fact that with the new driver, my computer could start rebuilding the indexing? That is, does Windows Update use the IRST driver or does it use the indexing?

    Anyway, everything seems to be working now.

Leave a Reply