Comments on: CheckSUR: System Update Readiness Tool to repair Windows Update

By: Beast MC

Beast MC — Sat, 07 Jan 2017 21:52:00 +0000

I got
DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.18489

Error: 87

The restorehealth option is not recognized in this context.
For more information, refer to the help.

The DISM log file can be found at C:WindowsLogsDISMdism.log

By: Crunt

Crunt — Fri, 23 Dec 2016 20:59:00 +0000

December, 2016 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB3205401)

Am running 8.1 and set for automatic updates. Receiving updates and installed with no problem except the one noted above.
Numerous attempts – always fail.
Bothersome because when trying to restart – computer loads this update which always fails.

By: MrTom4

MrTom4 — Thu, 27 Oct 2016 18:31:00 +0000

In reply to Sevian. Yes, as tim noted, it can stay at 20% for a while. That's what mine's doing. Just run your task manager to see what's going on. Mine's downloading a lot of information from the internet and CPU and hard disk activity. It finally finished and said it was completed, but it's still downloading something from the internet, and I have updates turned off.

By: Kenneth Rammer

Kenneth Rammer — Sat, 24 Oct 2015 02:09:00 +0000

I received Error: 87 , Can anyone help?

By: datastorm

datastorm — Mon, 19 Oct 2015 18:35:00 +0000

Windows 10 Pro here.

=================

The two DSM commands worked fine for me the first time around, the app store opened up.

Okay so then I followed your suggestion to run Windows Update and rebooted, but now the Windows App Store is doing the same thing again.

Now this time around the two DISM commands don’t fix the problem. What gives? Strange.

Also, WSReset.exe still gives me the “ms-windows-storePurgeCaches The app didn’t start” popup error window.

About a month ago I fixed the issue by performing a Repair-Install using a windows 10 iso from inside of winsdows 10. This did fix the problem, but it seems like overkill. Isn’t there an simpler way to fix the problem than to perform a repair-install of WIndows 10 every time the store breaks?