Error 87 running "DISM /Online /Cleanup-Image /RestoreHealth" on Windows 7.

Anonymous

I followed some advice on the wiki System file check (SFC) Scan and Repair System Files to find out how to fix corrupted files that SFC couldn't (as I had previously already known about SFC) and came across this barrier.

Here is a log file of DISM, if you need. It includes information only from the execution of DISM described in this thread.

Also, in case you need it, is my Command Prompt. Instead of creating a screenshot, I just pasted it in plain text.

Microsoft Windows [Version 6.1.7601]

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

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:\Windows\Logs\DISM\dism.log

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

Hello, joel perry

The TechNet Library article "DISM Supported Platforms" notes that "...Some DISM commands are not supported on all target images. For information about specific DISM commands, see Deployment Image Servicing and Management (DISM) Command-Line Options."; an admittedly-perfunctory perusal of the multiple articles linked in that one fails to reveal at a glance exactly what commands are supported by what OS, unfortunately - the documentation seems to follow the "new norm" of minimalization. "[DISM

Deployment Image Servicing and Management Technical Reference for Windows](http://technet.microsoft.com/en-us/library/hh824821.aspx)", the "section header" for the 51 pages of docs that includes all the articles I've linked in this post, specifically notes that the Windows 8 Windows Assessment and Deployment Kit (Windows ADK) can be used to service both Windows 7 & Server 2K8R2 WIM's, but there are a variety of qualifiers stated elsewhere, e.g. "Deployment Image Servicing and Management (DISM) Command-Line Options' states:

".../AnalyzeComponentStore and /ResetBase can’t be used when servicing a version of Windows that is earlier than Windows 8.1 or Windows Server 2012 R2 images."
".../StartComponentCleanup can’t be used when servicing a version of Windows that is earlier than Windows 8 or Windows Server 2012 images.", and
".../CheckHealth, /ScanHealth, /RestoreHealth, /Source, and /LimitAccess can’t be used when servicing a version of Windows that is earlier than Windows 8 or Windows Server 2012 images"

What is DISM?" mentions that "...To service inbox drivers in an offline image of Windows Vista with Service Pack 2 (SP2) or Windows Server 2008 with SP2, you must use the Windows 7 version of DISM or PkgMgr."

while "DISM Supported Platforms" also provides this: "Deployment Image Servicing and Management (DISM) works on Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server® 2012, Windows 7, and Windows Server 2008 R2 images. However, the full functionality is available only when you are servicing a Windows 8.1 or Windows Server 2012 R2 image. This is because the files and resources required to service any Windows image are located in the image, not on the technician computer. DISM will detect and use the resources available in the target image to update the image."

Although by no means a WIM-deployment professional myself, it would seem to me that you're presented with the limited options you're seeing simply because nothing else is supported by design,

and that using a later version of DISM (as outlined in "Copy DISM to Another Computer", which maintains that "...You can use deployment and imaging tools on a supported host operating system, such as Windows PE 3.0, even if you cannot install Windows ADK. You can copy the tools from a Windows ADK installation on your technician computer and configure the tools for use on a supported host computer.") would not provide the missing functionality...

0 comments

54 additional answers

Anonymous

2018-09-17T18:12:38+00:00

Actually, the spaces are mote than obvious: In Unix the convention is to use -option, in Windows /option, thus DISM simply expects options separated by a blank. Sure thing. That resolves nothing.

Thanks,

In my Win 7 - 64 bit system, I absolutely cannot determine just what is causing my Windows Update and my Systems Restore to fail. I've tried every suggestion, with my antivirus turned-off, getting a CBS.log from sfc/scannow, which reads:

"2018-07-07 17:31:34, Info CSI 0000042f [SR] Repair complete

2018-07-07 17:31:34, Info CSI 00000430 [SR] Committing transaction 2018-07-07 17:31:34, Info CSI 00000431 Creating NT transaction (seq 2), objectname [6]"(null)" 2018-07-07 17:31:34, Info CSI 00000432 Created NT transaction (seq 2) result 0x00000000, handle @0x120c 2018-07-07 17:31:34, Info CSI 00000433@2018/7/7:21:31:34.521 CSI perf trace: CSIPERF:TXCOMMIT;7 2018-07-07 17:31:34, Info CSI 00000434 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired"

I then tried DISM, getting that 87 Error*, and then tried*the Systems Update Readiness Tool, also to no avail.

It's just a head-scratcher.
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-17T16:32:28+00:00

believe me, it was entered correctly. something else is wrong!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-09-17T13:27:38+00:00

Actually, the spaces are mote than obvious: In Unix the convention is to use -option, in Windows /option, thus DISM simply expects options separated by a blank. Sure thing. That resolves nothing.
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-17T13:24:59+00:00

Same here, command entered per cut and paste, with these spaces:

C:\Windows\system32>DISM /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:\Windows\Logs\DISM\dism.log

The log file is most cryptic, contains only 'info' lines, with the exception of one single 'warning' line:

2018-09-17 06:19:08, Warning DISM DISM Provider Store: PID=576 Failed to Load the provider: C:\Users\thh\AppData\Local\Temp\8E06D6CC-B580-4AC3-A820-758061FA5B59\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Well, whatever that means, the error 87 is still here. Windows and the lack of support can be really frustrating.
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments