Solved DISM /Cleanup-Image - DISM Failed - What To Do Next Please

Greetings.

How can I identify what file(s) are corrupted and can I use the P50t files as a repair source? If so, what do I do? I can follow instructions, most times

Here is the problem:
My wifes laptop, a Toshiba P840 (running 8.1 64bit) has a problem. I also have a Toshiba laptop, a P50t (running 8.1 64bit). On mine, I ran sfc /scannow which found corrupted files. Using this forum as a guide, I ran the DISM cleanup tool, which fixed the problem(s). sfc /scannow is error free.

Ran sfc /scannow on the P840 which found corrupted files. Ran the DISM cleanup tool. It failed with this report: "error: 0x000f0906 The source files could not be downloaded. Use the "source" option to specify the location of the files that are required to restore the feature," etc, etc.

I was puzzled as to why one laptop would obviously download the required files but not the other. Thinking that it might be that I have Windows Update set to notify me of updates but not download them, I changed the setting to allow updates automatically.

I ran DISM Cleanup tool again and it failed again, reporting this: "The restore operation failed. Either the repair source was not found or the component store cannot be repaired. Error: 0x00f081f. DSIM Failed. No operation was performed."

The DISM log file looks strange (not that I have ever seen one before). I will copy/paste some of it here. Once it gets into the "Chinese/Japanese" characters, they go on forever, lol) The log file is identical on both runs.

Log File:
[1528] Wimserv process started for guid 91611296-6641-479c-af99-13da546322fb. Id is 1148
[1148] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1148] Mounted image at C:\WINDOWS\TEMP\bfb5eeaf-bd8e-46c9-bf29-7cd1fc195526.
[1528] [0x8007007b] FIOReadFileIntoBuffer1415): The filename, directory name, or volume label syntax is incorrect.
[1528] [0xc142011c] UnmarshallImageHandleFromDirectory511)
[1528] [0xc142011c] WIMGetMountedImageHandle2568)
[1528] [0x8007007b] FIOReadFileIntoBuffer1415): The filename, directory name, or volume label syntax is incorrect.
[1528] [0xc142011c] UnmarshallImageHandleFromDirectory511)
[1528] [0xc142011c] WIMGetMountedImageHandle2568)
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1528] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1148] Received unmount request for image with guid 91611296-6641-479c-af99-13da546322fb.
[1148] Unmount for image at C:\WINDOWS\TEMP\bfb5eeaf-bd8e-46c9-bf29-7cd1fc195526 complete.
〲㐱〭ⴴ㄰ㄠ㨳㤰〺ⰴ䤠普††††††††䐠卉⁍†䥐㵄㔱㠲吠䑉㠽㈱吠浥潰慲楲祬猠瑥楴杮琠敨猠牣瑡档搠物捥潴祲*桔獩洠祡戠⁥癯牥楲摤湥戠⁹獵牥氠瑡牥**䑃卉䵍湡条牥㨺楆慮䍬湯瑳畲瑣਍〲㐱〭ⴴ㄰ㄠ㨳㤰〺ⰴ䤠普††††††††䐠卉⁍†䥐㵄㔱㠲吠䑉㠽㈱匠牣瑡档搠物捥潴祲猠瑥琠䌧尺䥗䑎坏屓䕔偍❜**䑃卉䵍湡条牥㨺異彴捓慲捴䑨物਍〲㐱〭ⴴ㄰ㄠ㨳㤰〺ⰴ䤠普††††††††䐠卉⁍†䥐㵄㔱㠲吠䑉㠽㈱䐠獩䍭牯⹥汤敶獲潩㩮㘠㌮㤮〶⸰㘱㠳‴*䑃卉䵍湡条牥㨺楆慮䍬湯瑳畲瑣਍〲㐱〭ⴴ㈰〠㨸㌳㈺ⰰ䤠普††††††††䐠卉⁍†偁㩉倠䑉ㄽ㐵‴䥔㵄㜵〴䐠獩䅭楰搮汬›†††††††††††††††††††††ⴠ䐠獩䥭楮楴污穩䥥瑮牥慮൬㈊㄰ⴴ㐰〭′㠰㌺㨳〲‬湉潦†††††††††䥄䵓†䄠䥐›䥐㵄㔱㐴吠䑉㔽㐷‰楄浳灁⹩汤㩬㰠ⴭⴭ*瑓牡楴杮䐠獩䅭楰搮汬猠獥楳湯ⴠⴭⴭ‾*楄浳湉瑩慩楬敺湉整湲污਍〲㐱〭ⴴ㈰〠㨸㌳㈺ⰰ䤠普††††††††䐠卉⁍†偁㩉倠䑉ㄽ㐵‴䥔㵄㜵〴䐠獩䅭楰搮汬›†††††††††††††††††††††ⴠ䐠獩䥭楮楴污穩䥥瑮牥慮൬㈊㄰ⴴ㐰〭′㠰㌺㨳〲‬湉潦†††††††††䥄䵓†䄠䥐›䥐㵄㔱㐴吠䑉㔽㐷‰楄浳灁⹩汤㩬嘠牥楳湯㘠㌮㤮〶⸰㘱㠳‴*楄浳湉瑩慩楬敺湉整湲污਍〲㐱〭ⴴ㈰〠㨸㌳㈺ⰰ䤠普††††††††䐠卉⁍†偁㩉倠䑉ㄽ㐵‴䥔㵄㜵〴䐠獩䅭楰搮汬›慐敲瑮瀠潲散獳挠浯慭摮氠湩㩥∠㩃停潲牧浡䘠汩獥坜湩潤獷䐠晥湥敤屲獍灍湅⹧硥≥ⴠ䐠獩䥭楮楴污穩䥥瑮牥慮൬㈊㄰ⴴ㐰〭′㠰㌺㨳〲‬湉潦†††††††††䥄䵓†............... and it goes on & on & on & on..........

Wondering if the same file has been posted on before:
"FIOReadFileIntoBuffer1415): The filename, directory name, or volume label syntax is incorrect"

I came across this post"
http://www.eightforums.com/performa...re-health-function-gets-error-0x80240021.html

It has the same file name. I will not do anything until instructed.

Sorry about the Sad faces but I am not guilty, that's the way the file name is written.

Bump..... any help is appreciated.

From my past searches on this about all you can do is try to use another repair source. I copied the below from the Microsoft site.

Thanks popeye. Side By Side Folder sounds like the way to go. Do I point the repair tool at the Windows 8.1 installation DVD? If so, do I need to point it to a specific folder on the DVD or does the repair tool find the files it needs from the DVD, without any help from me?

You need to specify the file install.wim which is on the DVD in the sources directory. Change the X below to whatever drive letter your DVD drive is.

[/B]

adamf said:

You need to specify the file install.wim which is on the DVD in the sources directory. Change the X below to whatever drive letter your DVD drive is.

Code:

[B]DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:[COLOR=#ff0000]X[/COLOR]:\Sources\Install.wim:1 /LimitAccess[/B]

Click to expand...

Nice additional information. I have never actually tried this myself, curious if it will work.

I will try this on my wifes laptop, when I can pry her away from it. lol. The laptop works normally as far as she is concerned but I just like it to be exactly what it should be. If a file is corrupt, one day that file may need to be accessed and then problems! I will report back when I have done it. This procedure is all new to me.

Something I have discovered also. If all you have is an ISO then the files are ESD not WIM. There is a neat utility called WinReducer Wim Converter that will convert the Install.esd files to Install.wim files.

PS: I'm the same way when it comes to wanting things to be right even if it doesn't seem to be a problem at the present time.

I obtained a ISO last night of Win 8.1 Pro x64 and when I mounted it, there was "install.wim" and no ESD files were found when I ran a search on it. Both our Laptops have Windows OEM on them. It was with some difficulty that I found a ISO that had not been "played around" with.

I intend to burn the ISO onto a DVD. As our two Laptop OS's are genuine, this DVD is of limited use but necessary to do fixes like this.

I would hope they're genuine. But yea, same boat here, need that ISO to do some things. Strange your download has wim files mine has esd but I just converted using that utility. Maybe it has something to do with how you choose to save it when downloading.

At any rate let us know how it goes.

All fixed but not by using the DVD as source. I ran the DISM tool and pointed it at the optical drive. The drive was accessed and the program ran for 20 odd minutes. It finished by reporting this:
"ERROR:0x800f081f. The source files could not be found, use the source option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source"

As I had used an 8.1 DVD as the source, as one of the options that link gives, I needed to look elsewhere. I Googled the error code and came to this thread: Dism online restore health function gets error 0x80240021 - Microsoft Community I followed sidv88 instructions and it fixed the corrupted file:
"I have been able to resolve the issue. The key is to use the Dism /Online /Cleanup-Image /StartComponentCleanup command before Dism /Online /Cleanup-Image /RestoreHealth , and the component store was repaired. SFC was then able to fix the remaining corrupted files."

Thanks for the help on this problem. You don't find too many solutions posted as some people just can't be bothered to post the Fix after they have found a fix elsewhere. Cheers.

Good to know! It can take some jumping through hoops to figure out exactly will fix this particular problem in every situation. Glad you got it fixed and letting us know how you did it.