DISM clean up Windows 10 image - Error: 87

Which DISM command ?   ScanHealth you need to aim to the mounted iso,  example;  DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\sources\Install.wim:1 /LimitAccess           but other commands should work ok.

SFC is broken in most win10, until some future date.

Hi Cam,

I have sent you a Private Message to collect some details. Please reply to it to further troubleshoot this issue.

Please log on to the answers website to check the private message that I have sent you and provide us the details in the private message itself.

To see the Private Message, follow these steps:

You can view the private message section by

1. Clicking the red link above your post  

Or

2. Clicking on  link.

Thank you.

Yes there is another thread about it http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_repair/dism-online-cleanup-image-restorehealth/6cbd3640-573a-4b24-997f-16c637907b40

It fails when using command sfc /scannow and dism /online /cleanup-image /restorehealth does not work because it cannot find the files needed.

Actually both commands don't work 

C:\WINDOWS\system32>sfc/scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 0% complete.

Windows Resource Protection could not perform the requested operation.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.9926.0

Image Version: 10.0.9926.0

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are r
o restore the feature. For more information on specifying a source loca
 http://go.microsoft.com/fwlink/?LinkId=243077.

You need to read that article and look at the example I gave above to be able to run that particular RestoreHealth command.

You might just run

DISM /Online /Cleanup-Image /ScanHealth

If it says no corruption found, no reason to run restoreHealth

Yes you probably could do that if you had the disk for Windows 10 but as I have upgraded the OS it doesn't work because the files are unavailable.

A clean install would also require that you download the ISO and put that on a USB or DVD to run the command.

EDIT: today I thought I would run the command after updating Windows and low and behold it worked.

So it must have been a problem with windows update or some other online instance.

The component store is repairable.

That means there are errors that could be repaired if you want to take the time to download the iso. 

You don't actually need to save to usb, can right click the iso once downloaded and mount it... and then it will show as a Drive letter that you can explore or run that RestoreHealth command against.

Yes thank you, I will give it a try and see what happens. Downloading ISO file now.

Not sure why you cannot restore health online instead of using the ISO?

EDIT: I can report that nothing work even with the ISO mounted.

- When you say "SFC is broken in most win 10", I agree with you 100%, my current record is 7% verification before it gives an error have not been able to execute SFC.

-It fails even on a  brand new clean install (this really doesn't make sense),  and fails when I need to work to fix: explorer (hard error), (then the computer is non-responsive and slow, and need to reboot)

- For me, DISM ... /RestoreHealth completes but doesn't seem to fix the problem.  

- Given the volumes of feedback from users trying to get their windows 10 XX to work, maybe Microsoft will put together a tool that walks a user through to /Restoring the health of their systems, or least isolate the cause, and or the consequences of it not working.   Kind of like: Cortana - "Fix my ###XXX computer", sorry just a bit frustrated.

Just an FYI:

• DISM's cleanup-image commands only exist to detect, and if found, fix, component store corruption (i.e. the WinSxS folder)
  • The only exception is startcomponentcleanup, which exists to clean the WinSxS folder of old (backup) component stores (i.e. old Windows updates).  If restorehealth fails, odds are you need to perform component cleanup
• SFC only exists to check, and, if found, replace, system files that are corrupt (i.e. their hashes don't match what they should)

If the problem an end user is experiencing is not related to either, then it's not going to fix the issue.  These aren't fix-alls; each has a very specific and important purpose, but neither will fix issues outside of what they were designed to fix.

I do recognize this thread is a few months old and was commented on prior to build 10240, however, many of the issues with responsiveness and slowness are directly related to software being run that is not compatible with Windows 10; this applies even more to users who upgraded and have not yet performed a clean install.  Unlike Windows 8, Windows 10 will not tell you if software you have installed is not compatible prior to upgrading (it does to a point, but not with software designed for Windows 8 that isn't compatible with Windows 10).

For users who are experiencing unresponsiveness or slowness, and haven't done a clean install, that would be the place to start.  I understand it's a hassle to reinstall all your software again (even with an MDT LTI, it still takes me 2 days to reinstall everything), however it doesn't matter what Windows version you're upgrading to, upgrades will always result in issues... issues that will take more time to troubleshoot than it would take to clean install and reinstall all the software.