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

173 answers

Sort by: Oldest
  1. Anonymous
    2017-12-05T01:08:18+00:00

    this wont work. authcab.cab is expired. This effects all microsoft OSes still getting update up to windows 7 (including xp embedded). authcab.cab needs to be reissued so that is not past expiry. backdating the system will fix it if you want proof.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-05T02:37:16+00:00

    After resetting my SoftwareDistribution folder in an attempt to fix the 80248015 error yesterday, that particular setting is unchecked, and Windows Update says that I am only receiving updates for Windows. Yet, I'm still unable to update my Microsoft Security Essentials by forcing an update through the program and get a 80248014 error instead.

    Perhaps some other setting was not reset along with the rest when I renamed the SoftwareDistribution folder, but I'm not sure what it is. I've heard that the catroot2 folder should be reset as well to fully reset Windows Update components, but I don't want to mess around with more stuff in my computer unless I know it works.

    EDIT: Forgot to mention that before resetting my SoftwareDistribution folder, I had the setting checked. However, now I'm unable to re-check it either.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-05T03:17:04+00:00

    I'm still getting error 80248015 when I try to run Windows Update (Win 7, 32-bit) but MSE is updating itself normally by manually using MSE's own updater, regardless of whether the box Born told us to uncheck is checked or unchecked, and without changing the date on this PC.

    Got 2 MSE definitions updates this afternoon, and now have the latest: 1.257.1389.0,  which was created at 4:05 PM on 12-4-17. Not sure if that's my time zone (Pacific) or some other zone.  

    I don't understand the panic here. MS is unlikely to issue any serious or major updates between now and the next regularly scheduled 2nd Tues updates. So I don't think there's any real threat to anybody's system as long as we can get MSE updates using MSE, itself.

    Sure, MS screwed up -again- and it's a waste of our time and I'm as annoyed as everyone else, but it's not a critical problem. 

    My 2-cents...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-12-05T03:28:33+00:00

    After resetting my SoftwareDistribution folder in an attempt to fix the 80248015 error yesterday, that particular setting is unchecked, and Windows Update says that I am only receiving updates for Windows. Yet, I'm still unable to update my Microsoft Security Essentials by forcing an update through the program and get a 80248014 error instead.

    Perhaps some other setting was not reset along with the rest when I renamed the SoftwareDistribution folder, but I'm not sure what it is. I've heard that the catroot2 folder should be reset as well to fully reset Windows Update components, but I don't want to mess around with more stuff in my computer unless I know it works.

    EDIT: Forgot to mention that before resetting my SoftwareDistribution folder, I had the setting checked. However, now I'm unable to re-check it either.

    You can't just rename that folder, you have to open a CMD prompt window and run it as Administrator.

    Enter these commands and press <Enter> after each one:

    net stop wuauserv

    cd %windir%

    ren SoftwareDistribution SDold

    net start wuauserv

    Close the CMD window and open MSE and click Update tab >Update definitions

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-12-05T03:40:52+00:00

    That's exactly what I did: I renamed SoftwareDistribution through the command prompt (started it as Admin) after I stopped wuauserv with the net stop command. Again, Windows Update now starts up, but I've been unable to update my MSE via Update Definitions

    in the program itself - it just returns error 80248014. I even restarted my PC after making the change, and the error was still there.

    EDIT: I am still in somewhat of a panic BECAUSE my MSE cannot update. I rarely use Windows Update for other things, but yesterday, I was unable to update my MSE due to to 80248015. After renaming the SoftwareDistribution folder in an attempt to fix it, MSE returns error 80248014 instead. Hopefully I described the problem clearly and you can see why it's nothing to scoff at. There was another person with the same issue as well.

    EDIT2: I tried to recreate the issue on a rarely used Win7 Home Premium 64 bit (same OS as the desktop facing this issue) laptop that I have. However, to my surprise, not only did Windows Update start upon loading the desktop screen without any errors, it was ALSO able to update MSE immediately. Hitting 'update definitions' in MSE on the laptop likewise returns no errors. So I'm completely stumped right now.

    Was this answer helpful?

    0 comments No comments