1.    23 Apr 2017 #1
    Join Date : Jul 2015
    Posts : 149
    Windows 10

    DISM Restore Health "source files not found"


    Forgive the redundancy with other threads on this topic, many of which I have read, with no solution...

    1. Mounted the ISO from which 1703 Pro was installed. Converted the \sources\install.esd file to a .wim file.
    2. Placed install.wim in D:\.
    3. From an elevated CMD C:\> prompt, ran...
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\install.wim:1 /limitaccess

    Is the syntax to install.wim incorrect? The installed build is 15063.138 Because the ISO was downloaded just after the 1703 debut, subsequent updates may have upped the build # suffix. Is that an issue?

    What am I missing here? Thanks.
      My ComputersSystem Spec
  2.    23 Apr 2017 #2
    Join Date : Aug 2016
    S/E England
    Posts : 4,475
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by borgus View Post
    What am I missing here? Thanks.
    Nothing, really. As you've already read the other threads you'll have gathered this appears to be a 'bug' in DISM introduced in 1703. You may not have spotted this post that shows using 1703's DISM for an offline repair does complete successfully.
    Use DISM to Repair Windows 10 Image

    As the offline repair finds no problems on my system, while an online repair fails with 'source not found' I'm assuming there's nothing that actually needs repairing. I'm expecting a fix from Microsoft in (hopefully) the next cumulative update.

    You can actually use the .esd file directly, no need to convert to .wim. See the command line in the above post. One point to check in your command line - the index you used. The index :1 is for Pro in my .esd. Check you are using the right one...
    Code:
    C:\WINDOWS\system32>dism /get-imageinfo /imagefile:d:\x64\sources\install.esd
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Details for image : d:\x64\sources\install.esd
    Index : 1
    Name : Windows 10 Pro
    Description : Windows 10 Pro
    Size : 15,278,163,599 bytes
    Index : 2
    Name : Windows 10 Home
    Description : Windows 10 Home
    Size : 15,099,341,449 bytes
    Index : 3
    Name : Windows 10 Home Single Language
    Description : Windows 10 Home Single Language
    Size : 15,102,384,056 bytes
    Index : 4
    Name : Windows 10 Education
    Description : Windows 10 Education
    Size : 15,096,909,438 bytes
    The operation completed successfully.


    The installed build is 15063.138 Because the ISO was downloaded just after the 1703 debut, subsequent updates may have upped the build # suffix. Is that an issue?
    Others have reported that on a clean install of 15063.0 (which is what my .iso will install) DISM reports no corruption and an online /restorehealth works. It's only after any updates have been installed that the problem appears, lending credence to the theory that it's an MS-created fault.
    Last edited by Bree; 23 Apr 2017 at 17:52.
      My ComputersSystem Spec
  3.    23 Apr 2017 #3
    Join Date : Jul 2015
    Posts : 149
    Windows 10
    Thread Starter

    Thanks for chiming in Bree. Yes, the index (1) is correct for PRO.

    You refer to "see the command line in the above post." Yet there is no post prior to my initiation of this thread. What is the OFFline command that succeeds in this situation?

    And you're likely correct that nothing needs fixing. SFC /scannow is clean. Take care.
      My ComputersSystem Spec
  4.    23 Apr 2017 #4
    Join Date : Aug 2016
    S/E England
    Posts : 4,475
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Sorry, by 'above post' I meant the post I had provided a link to. The command line it contains is:

    Code:
    DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch
    Which I used successfully on my system (Home) (apparently Brink thinks the 'ScratchDir' option may be unnecessary).

    BTW: there's a new post on that thread with a link to this...
    https://answers.microsoft.com/en-us/...ge=2#LastReply
    ...which goes some way to explaining what causes the apparent 'error'.
      My ComputersSystem Spec
  5.    23 Apr 2017 #5
    Join Date : Jul 2015
    Posts : 149
    Windows 10
    Thread Starter

    No luck with the command line below, where INDEX.esd was on D:\. "Error occurred while accessing temporary directory."
    DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:\install.esd:1 /ScratchDir:C:\Scratch

    Likely the command still isn't quite right for an offline test?? But, from the look of the referenced posts, it's not a concern.
      My ComputersSystem Spec
  6.    23 Apr 2017 #6
    Join Date : Aug 2016
    S/E England
    Posts : 4,475
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by borgus View Post
    .. "Error occurred while accessing temporary directory."
    Yes, I got that the first time I ran it. Then I realised I had to create C:\Scratch myself before DISM could use it
      My ComputersSystem Spec
  7.    23 Apr 2017 #7
    Join Date : Jul 2015
    Posts : 149
    Windows 10
    Thread Starter

    Well, all right! Forgive my ignorance, but how did you do that and what's the correct command line - to reference the D:/ drive install file? ^_^
      My ComputersSystem Spec
  8.    24 Apr 2017 #8
    Join Date : Aug 2016
    S/E England
    Posts : 4,475
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Create the C:\Scratch folder before you start, DISM can't create it for you. Then boot to a Command prompt with the install media, a recovery drive or Advance Start up. The command I used successfully was:
    DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch

    That command was for Home. Change 'esd:2' to 'esd:1' for Pro. You can confirm the index number you need to use with dism /get-imageinfo /imagefile:d:\x64\sources\install.esd

    Change the /source path to suit where your install.esd is to be found (drive letter, path, x86 or x64 as appropriate.)
      My ComputersSystem Spec
  9.    24 Apr 2017 #9
    Join Date : Jul 2015
    Posts : 149
    Windows 10
    Thread Starter

    Thanks for the feedback enlightenment.
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
Solved DISM won't run "restore health" in Insider build 15046
I downloaded build 15046 with no problems. I like to use Kyhi's program for the DISM utilities. Question: with the new build will "restore health" run? I keep getting can't find "source" error. If so, what is the procedure please?
Performance & Maintenance
Dism problem "The source files could not be found"
I have done an SFC /scannow at least two dozen times now on my Windows 10 tablet, resulting in "Found corrupt files but was unable to fix them" message Several posts on this site alone tell me to do a "dism /online /cleanup-image /restorehealth"...
Performance & Maintenance
dism results: "the soure files could not be found"
I am having applications start up in "suspended" mode. I have tried several suggestions. I am running Norton on the computer for my anti-virus and did a full system scan that found nothing. Here is some of the command prompt logs: ...
Performance & Maintenance
Trying to fix DISM "source" not found issue with Techbench ISO-how?
I started having the DISM online /cleanup-image errors when I used the command saying "source not found" I downloaded the Techbench ISO from a source and put the contents into a Folder called ISO in native directory on C drive. What command do I use...
General Support
Solved "Error (0x800F081F) - DISM Unable to find source" & "sfc /scannow"
I have upgraded 5 machines and clean installed 3 machines. Experienced an issue with one machine with continuous corruption problems After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:04.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums