Can't install Windows updates-- error code 80248015

Anonymous

error code 80248015 can't install updates.

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

Answer accepted by question author

Anonymous

Verify that the time, date/year & time-zone are set correctly

<<Set the clock>>

Always remember to set a System Restore point before doing any work on your computer.

Rename the Windows Update Softwaredistribution folder

That is what I got when searched around for error 0x80248015

This problem may occur if the Windows Update, Software distribution folder has been corrupted.

We can refer to the following steps to rename this folder.

Please note that the folder will be re-created the next time we visit the Windows Update site.

Close all the open windows.
Click the "Start" Button, click "All programs", and click "Accessories".
Right-click "Command Prompt" and click "Run as administrator".
In "Administrator: Command Prompt" window, type in " net stop WuAuServ" (without the quotes) and press Enter.

Note: Please look at the cmd window and make sure it says that it was successfully stopped before we try to rename the folder.

Click the "Start" Button, in the "Start Search" box, type in " %windir%" (without the quotes) and press Enter.
In the opened folder, look for the folder named "SoftwareDistribution".
Right-click on the folder, select "Rename" and type " Sdold " (without the quotes) to rename this folder.
Still in "Administrator: Command Prompt" window, type the command " net start WuAuServ" (without the quotes) in the opened window to restart the Windows Updates service.

Note: Please look at the cmd window and make sure it says that it was successfully started.

Note: If the issue is resolved and you can successfully download and install updates, you can safely delete the SoftwareDistribution.old directory to recover disk space.

The windows update team and other users who regularly read the forum can either share their knowledge or learn from your interaction with us.

UTC/GMT is 15:15 on Monday, May 21, 2012

0 comments

63 additional answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2017-12-04T19:09:42+00:00

Yes, It worked on a Windows server 2008 R2 and on a Windows 2012 server too.

Thanks,
Was this answer helpful?

0 comments No comments
Anonymous

2017-12-04T19:07:43+00:00

I went back to 12/01/2017 but the 2nd will probably work too. I was able to update Windows 7 with no problem when I did this. This appears to be a problem with how Windows Update resets the expiration date. If the files are corrupted then why does changing the date allow it to work? This also indicates that if the files are corrupted then the corruption comes from the updates themselves. It appears from the sudden spike of responses today that a whole lot of others are having this problem on this date issue.
Was this answer helpful?

0 comments No comments
Anonymous

2017-12-04T18:53:15+00:00

Большое спасибо, Хосе Антонио! Это отличный подарок для Рождества 2017 года. Ваши рекомендации позволили мне решить давнюю проблему: центр обновления Windows не хотел автоматически обновляться более года. Даже в руководстве многие загрузки не могли быть загружены! Но после создания новой папки под названием «Sdold» обновления рушились, как дождь на моей голове :))) После этого я удалил папку под названием «SoftwareDistribution.old», которую я создал ранее, чтобы решить проблему Windows обновления. Но до этого кода ошибки я не показывал Windows, поэтому мы не могли встретиться с вами в World Wide Web :)))
Was this answer helpful?

0 comments No comments