DISM Command Problem

Topic

New Reply

I read the following article:

“Doing the Restore Health Command is better than SFC /SCANNOW

•Open an Admin Command Box and type one of the following to run DISM in the manner you choose:
•Dism /Online /Cleanup-Image /CheckHealth
•Dism /Online /Cleanup-Image /ScanHealth
•Dism /Online /Cleanup-Image /RestoreHealth

I don’t have a clue what the difference is between the ScanHealth and CheckHealth switches are. You may do some research if you like. Regardless, it may take some time to run, from a few minutes to many depending on your system. If I remember right, it took about 15 minutes or so for mine to complete.

Update 9/20 – One of our readers, B, offered this very helpful information:

“/CheckHealth – This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.

/ScanHealth – This switch option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.

/RestoreHealth – (recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption”.

I tried to use the RestoreHealth command, but was told that “this option is not recognized in this context”. I am not sure what this means, and if someone could explain this and tell me how to get around this problem I would be grateful.

On a related point, whenever I run command prompt it opens as an Administrator. Clutching at straws I tried to run the RestoreHealth command as a non administrator but was unable to. The cmd.exe file in system 32 opens an administrator command prompt. Advice on this would also be appreciated.

Thanks and regards, Roy

Reply | Quote

Replies

I think it only fixes, or perports to fix, corrupt WU issues, and not general operating system
related corruption issues.

RestoreHealth command as a non administrator but was unable to.

It depends on how you set your system up. In most instances you should be running in the admin account, or right click on the command icon and select “run as admin” prior to.

Reply | Quote

DISM is not for live Windows, it’s for images that you will be deploying.

cheers, Paul

Reply | Quote

DISM is not for live Windows, it’s for images that you will be deploying.

Yes, it does work on live Windows. I ran it about three days ago to rebuild the store. Sfc /scannow found errors it couldn’t repair, and I ran DISM /Online /Cleanup-Image /RestoreHealth. It took between 10 and 15 minutes to complete, but replaced the corrupted files in the store, as well as the corrupted files that sfc couldn’t repair (because of the corrupted files in the store).

After the DISM command finished, I ran sfc /scannow again, and it found no integrity problems.

Here is a portion of the DISM.log file:

[1816] Caller did not request sparse mount
[1816] Mounting new image.
Wim: [\?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim]
Image Index: [1]
Mount Path: [C:WINDOWSTEMP1128584a-f03d-4b52-a195-ea7a18d1cbe3]
[1816] Wimserv process started for guid cbbe41e0-fdcf-4f80-af96-bda27bd805ea. Id is 1744
[1744] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1744] Mounted image at C:WINDOWSTEMP1128584a-f03d-4b52-a195-ea7a18d1cbe3.
[1816] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[1816] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1816] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1816] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[1816] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1816] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1816] ImageUnmarshallHandle: Reconstituting wim at \?GLOBALROOTdeviceharddisk1partition2RecoveryWindowsREWinre.wim.
[1744] Received unmount request for image with guid cbbe41e0-fdcf-4f80-af96-bda27bd805ea.
[1744] Unmount for image at C:WINDOWSTEMP1128584a-f03d-4b52-a195-ea7a18d1cbe3 complete.

The rest is not in English.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

How do I run command prompt as a non admin?

Reply | Quote

Just left click the shortcut. If you right click it there will be a “run as administrator” option, which pops up the UAC prompt. Windows 8 has a separate selection called “Command Prompt (Admin)” when you right click the Windows Flag in the bottom left corner.

cheers, Paul

Reply | Quote

@Paul

You can use the specific DISM commands referenced in post 1 against a live system. As Clint mentioned it is only to try to fix WU issues.

Joe

--Joe

Reply | Quote

You can use the specific DISM commands referenced in post 1 against a live system. As Clint mentioned it is only to try to fix WU issues.

Well that’s one for the “what were they thinking” archive.

cheers, Paul

Reply | Quote

You can use the specific DISM commands referenced in post 1 against a live system. As Clint mentioned it is only to try to fix WU issues.

See post #13 – it can also repair files that sfc /scannow cannot repair.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

http://technet.microsoft.com/en-gb/library/hh824869.aspx would suggest that it is for more than WU issues.

I know I suggested the DISM command to one of the Lounge members as a fix which resolved the problem, but memory being what it is, I can’t remember now what the issue was.

Reply | Quote

Sudo15,
You replied to me about a week ago with a link to the tech net article. I had seen this through google searches and have tried at least 4 dozen plus combinations using sources from 2 images on my c drive, images from my backup drive and my 8.1 install on a flash drive. I finally gave up.
I have no problems with windows update. My only problem has been with power options, which I was hoping to get fixed.

Clint and JoeP517,
The restore health option is supposed to fix component store corruption although I am not quite clear on just what that might be. Research indicates that the add features option in windows 8/8.1 might be a part of it but I haven’t been able or inclined to go that far yet. I’ll just let the computer shut down instead of sleep for now.

Rich

Reply | Quote

Sudo15,
Forgot to thank you for the quick reply last week.
Thanks,
Rich

Reply | Quote

It wasn’t your thread I was referring to as the Dism command in that instance resolved the problem, but given the different time zones of all of the members, I think the “quick reply” depends on who is awake at the time

What did the Dism /Online /Cleanup-Image /ScanHealth report ?

You would have to refresh my memory on the power options problem but there’s a command to restore the power options in Win 7 which has been found to work in Win 8.1, but can be baulked by an AV program – so you would either have to disable the AV or boot up into Safe Mode to use the Command Prompt in elevated mode.

Using the admin command prompt enter powercfg /restoredefaultschemes

This should restore the power options so you can create your own power plan.

This is an article on powercfg which may also help – http://technet.microsoft.com/en-gb/library/hh824902.aspx

Reply | Quote

I suppose you could run Dism /Online /Cleanup-Image /StartComponentCleanup before running the /RestoreHealth command if the /ScanHealth reports problems.

Reply | Quote

bbearren, I should have mentioned that my question relates to Win 8.1 and to the Win 10 tech preview.

I ran the command DISM /Online /Cleanup-Image /RestoreHealth, and it completed successfully. However, when I ran sfc /scannow the same errors were found as it found before running the RestoreHealth command.

The errors refer to failures to decompress files, and I find that strange in itself.

Any ideas as to what, if anything, I can do to get the errors corrected?

Please advise.

Thanks and regards, Roy

Reply | Quote

I’m running 8.1, but not the10 preview. You can run sfc /scannow in safe mode; that might get better results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren, thanks .I ran the command in safe mode, but it made no difference.

Reply | Quote