Windows 10 error

[thomasbell4711]

I'm trying to update Windows 10 but when doing the updates a Windows 10, version 1803 - error 0x80240013 has came up. How do I fix this and what does it need me to do?

 

[stdragon]

Open services.msc (Services), scroll down the list to Windows Update. Stop that service.

Delete the SoftwareDistribution folder. It's located "C:\Windows\SoftwareDistribution"

Don't worry, the next time you check for updates, it will rebuild that folder. Most likely something got corrupt in it, and needs to be purged from the system

Edit: Sometimes you might need to stop the "Background Intelligent Transfer Service" too if you're unable to delete that folder.

 

[thomasbell4711]

I did this and now when I try to update its saying files are missing.

 

[stdragon]

I did this and now when I try to update its saying files are missing.

Where you able to delete the entire SoftwareDistribution folder and not just files inside it? Because if you left file remaining, that will cause the issue.

If you've done that, rebooted the computer, and still run into trouble, the next step is to run a few DISM command to check, validate, and correct the system if at all possible. Read the link below prior to just executing the commands.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

 

[thomasbell4711]

I deleted the whole file. I turned off after so when I go back on, will that be it rebooted then I'll do what you advised next. Thanks

 

[ex_bubblehead]

One or more of the solutions here ( https://ugetfix.com/ask/how-to-fix-windows-store-error-0x80240013/ ) will fix the problem. "Clear Windows Store cache" has been the one that clears the problem most often for the upgrades I've done. In fact it crops up so often that I simply clear the Windows Store cache before even starting an upgrade now.

 

[stdragon]

I've often found that the wsreset.exe command doesn't fix anything. It's really a failing of Microsoft here. Once that App Store get's hosed, it's nearly impossible to reconstruct without a wipe/reload of the OS.

And yes, I've been down the rabbit hole repairing with Powershell command and whatnot to repair. Perhaps I was just unlucky to run across a system that was that badly munged.

Anyways, I hope it helps him better than it did me