Error Code 80248015

Anonymous
2017-12-03T21:29:45+00:00

How to fix Error Code 80248015 when trying to access windows updates

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

173 answers

Sort by: Most helpful
  1. Anonymous
    2017-12-04T06:49:39+00:00

    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.

    12 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-12-04T07:32:25+00:00

    Authcab.cab's .XML has these entries

    <ServiceID>7971f918-a847-4430-9279-4a52d1efe18d</ServiceID>

      <CabVersion>8110</CabVersion>

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

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

    This is a MS issue so they will need to update the cab.

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-12-04T08:17:16+00:00

    Apologies if this warrants a new thread, but since this is related to this issue, I thought I should post here first. Please bear with my explanation as English is not my native language.

    So, I'm on Windows 7, and I received this same 80248015 error earlier today when trying to update MSE. Upon opening Windows Update I was unable to get updates because 'the service is not running'. I panicked, since viruses seem to do the same thing, which is shutting down Windows Update first to prevent patches. Looked up solutions online and found one that involved renaming the SoftwareDistribution folder to softwaredistribution.old. After I did so, Windows Update started working again, so I thought it was a corrupt SD folder after all.

    I then tried to update MSE definitions again, and it failed with the error code 80242014 instead. I uninstalled MSE, then installed the latest version of it. The initial download of the definitions worked just fine - however, after a restart, the 80242014 error returned when I tried to force a definition update. I also cannot seem to enable the option to get updates for Microsoft products outside of Windows, even after opening the related go.microsoft.com page with Internet Explorer; it just returns a fail message.

    Did I mess up something big, or is this also related to the expiry date? If I did mess up, is there any way I can revert the changes I made, since I did not delete my old SofwareDistribution folder?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-12-04T08:54:12+00:00

    Same issue here, worked yesterday.

    It must be a Microsoft server bug since there are multiple reports of the same issue at the same time.

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-12-04T09:11:47+00:00

    Ha. I had the exact same reaction to those Windows Update errors as you and my MSE is now also borked (80242014). After reinstalling the MSE the first update went through without a problem and now I am getting error messages (80242014) - same as you.

    I don't think we did something "wrong". There is something wrong with die MS servers right now.

    1 person found this answer helpful.
    0 comments No comments