Close
Skip to content

40 Comments

  1. Uday Sharma
    June 21, 2021 @ 2:31 pm

    Thank you very much it helped me in windows 8 and i don't have any access to windows 10.
    It helped me very much.

    Reply

  2. Ram
    November 28, 2020 @ 5:10 am

    Thank you. I have lookedd at many guides on fixing DISM source errors and yours is the best.

    Reply

  3. Luke
    December 9, 2019 @ 7:51 pm

    Make sure you check your DISM version, these commands don't seem to work on a Win 7 pro OS instance when working with generated windows 10 media.

    Reply

  4. Federico Montanari
    October 31, 2019 @ 1:39 pm

    thank you very much very clear explanation and guide, nice job.

    Reply

  5. Michael
    August 31, 2019 @ 11:04 pm

    I was able to extrac the install.wim into c:\ root folder
    but regardless what i do the dism is not working and still cannot find the source i even packed that file into an image and tried it from there no luck …. why the fuck needs this to be so complicated

    Reply

    • lakonst
      September 1, 2019 @ 11:08 am

      Use the instructions at this method (NLITE) to extract the install.wim file and try the procedure again.

      Reply

    • Wolfgang K
      May 9, 2020 @ 2:00 am

      Has NLITE been of any help to anybody yet? – I'm super sceptical of 3rd party software for good reasons. Staying away from untrusted sources unless multiple folks can attest to no issues.

      Reply

  6. Kev
    June 7, 2019 @ 7:02 pm

    Worked like a charm!!

    Reply

  7. cafyon
    April 3, 2019 @ 1:14 am

    7zip software is able to:
    – open windowsxx.iso
    – then extract or open install.esd

    If one's intention is to extract specific files from windowsxx.iso or install.esd and not creating an install.wim, then 7zip is more than sufficient.

    Reply

  8. Graham
    March 15, 2019 @ 11:33 pm

    Hi,

    I hope you still look at this site, as the last post I see here was a long time ago!

    I have spent a lot of time now (Days on and off!), trying to convert a windows 10 install.ESD file to an install.WIM file, so I can deploy Windows on a server, using WDS without luck.

    I have followed examples from several different sites… Your example is the only one I have found that mentions the different compression formats e.g. Max, Fast, Recovery & None. I know the example says that the Recovery option has to have a .ESD extension but that is the only option that works (Although I give it the .WIM extension) without giving me the error "11 An attempt was made to load a program with an incorrect format" is the Recovery option but WDS reports that the file is either invalid or corrupt.

    I am now at a loss and am hoping for a response and a possible solution or explanation as to what I am possibly doing wrong!

    Thanks

    Reply

    • lakonst
      March 16, 2019 @ 10:12 am

      @Graham: Another method to convert ESD to WIM is by using NLITE. If you want to try, then follow these instructions and tell me the results.

      Reply

      • Graham
        March 18, 2019 @ 12:30 am

        Hi lakonst, Thank you very much for your prompt reply and suggestion of using NTLite.
        The program did it's magic and the .WIM file it created was accepted (Imported) by WDS but when I try to PXE load a machine, it starts to boot via WDS, then I get an error from Windows Boot Manager, saying that Windows failed to start. Status: 0xc0000001 A required device isn't connected or can't be accessed.

        Any ideas?

        Regards
        Graham

        Reply

        • lakonst
          March 18, 2019 @ 10:25 am

          @Graham: 1. Make sure that you have set the correct Date/Time at the machine 2. Add the network drivers in the boot image. 3. In WDS server's registry: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP and change the RamDiskTFTPBlockSize value to 1456.
          Now try to boot again…and if you receive the same problem..
          4. Open WDS > At the left, right-click on your server and choose Properties > Select the "TFTP" tab and set the Maximum block size to 1024. > Restart the WDS server and try to boot the machine again.

          Reply

  9. kpal
    February 27, 2018 @ 12:31 am

    Do you put it the extracted install.wim back into the iso?
    If so, by what method?

    Reply

    • lakonst
      November 12, 2018 @ 11:39 am

      @kpal: To put the install.wim back to the Windows ISO file, you have to:
      1. Extract the Windows ISO image file.
      2. Delete the existing install.wim (or install.esd) from the "sources" folder at the extracted ISO folder.
      3. Copy the extracted install.wim to "sources" folder (at the extracted ISO folder)
      4. Create a new Windows ISO file from the extracted/modified folder.
      The instructions can be found here: https://www.wintips.org/how-to-edit-iso-file-modify-windows-iso-bootable-image/

      Reply

    • Graham
      March 18, 2019 @ 11:08 am

      Good Morning lakonst,

      Thanks again for prompt response.
      I did some research and did try "4. Open WDS > At the left, right-click on your server and choose Properties > Select the "TFTP" tab and set the Maximum block size to 1024. > Restart the WDS server and try to boot the machine again." without luck. I also tried installing the Laptop directly with Windows-10 install DVD, which I hadn't previously! and I got the Windows Boot Manager Status 0xc0000260 … I then released that maybe this Laptop just won't work with Win-10 as it is an old Dell, which I was using as a test machine to practice WDS imaging tools.

      If this is the case, I apologize for wasting your time :-/

      Graham

      Reply

  10. abdu
    December 13, 2017 @ 8:09 am

    EDIT:
    I mean,
    I extracted one indexed item and want to put this back alone only
    so How to compress back this install.wim to install.esd, and what must be set to the installation configuration to be able to smoothly perform the installation correctly after the other of the item(s) left out.

    Reply

    • lakonst
      December 13, 2017 @ 11:49 am

      @ To convert the extracted INSTALL.WIM to Install.ESD use the following command: (don't forget to modify the full path for the source and the destination image files)
      dism /export-image /SourceImageFile:"install.wim" /SourceIndex:1 /DestinationImageFile:"install.esd" /Compress:recovery

      Reply

  11. abdu
    December 13, 2017 @ 8:06 am

    @Lakonst
    I mean:
    I extract one indexed item and want to put this back alone only
    so How to compress back this install.wim to install.esd, and what must be set to the installation configuration to be able to install correctly after one of the indexed item is left out.

    Reply

  12. abdu
    December 13, 2017 @ 8:03 am

    @Lakonst
    How to compress back to esd the install.wim, and what the setting to be made in installation configuration to be able to install correctly after one of the indexed item is left out.

    Reply

  13. Iqbal
    December 6, 2017 @ 7:06 pm

    great work man.

    Reply

  14. Clay Davis
    November 23, 2017 @ 8:04 pm

    I seem to be missing a crucial step. I copied the esd file, but how do I paste it to the C: root folder?

    Reply

    • lakonst
      November 23, 2017 @ 9:08 pm

      @Clay Davis: Highlight the Disk C in explorer and Paste.

      Reply

  15. Hydroxide
    November 21, 2017 @ 10:36 pm

    I'm getting Error 605: the specific buffer contains ill-formed data when trying to extract the ESD. Any ideas?

    Reply

    • lakonst
      November 22, 2017 @ 11:00 am

      @Hydroxide: Please try an in place upgrade. Your system files appear to be corrupt.

      Reply

  16. Howard
    October 31, 2017 @ 8:43 pm

    I have always had problems with DISM resolving component store corruption. As you said, it could not find the source. Your method solved the problem. The corruption has been repaired. It is so hard to find reliable information regarding problems with DISM, but you have done it! Thank you so much for sharing …

    Reply

  17. AZMountainGeek
    September 22, 2017 @ 12:44 am

    I've been trying to repair a WIndows 8.1 installation using DISM, which fails using the esd file, so I'm trying to extract that to a WIM file to use (I've read elsewhere that DISM doesn't always find the source files in the esd.) Step 1 works fine and I can see there's only 1 installation in the ESD file (obtained from an ISO built using Windows Media Creation Tool). But when I run step 2 I get the following error:

    Error: 11
    An attempt was made to load a program with an incorrect format.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    The DISM log shows the following:

    2017-09-21 15:25:38, Warning DISM DISM WIM Provider: PID=7668 [ReadWimHeader:(2268) -> version/header mismatch] C:\install.esd (HRESULT=0x8007000B) – CWimManager::WimProviderMsgLogCallback
    [7668] [0xc144012e]
    2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 [WIMCreateFile:(415) -> Fail to read WIM header] C:\install.esd (HRESULT=0x8007000B) – CWimManager::WimProviderMsgLogCallback
    2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1440 – CWimManager::Export(hr:0x8007000b)
    2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4862 – CWimManager::InternalCmdExport(hr:0x8007000b)
    2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 Error executing command – CWimManager::InternalExecuteCmd(hr:0x8007000b)
    2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2273 – CWimManager::ExecuteCmdLine(hr:0x8007000b)
    2017-09-21 15:25:38, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=8007000B

    Any ideas?
    Thanks!

    Reply

    • lakonst
      September 22, 2017 @ 8:59 am

      @AZMountainGeek: Have you downloaded the ISO file at the same Windows version & architecture (64bit or 32Bit) as the OS is? Also, are you sure that the ESD contains only one version of Windows? From the error I understand that the version of ESD file is mismatch.

      Reply

      • AZMountainGeek
        September 24, 2017 @ 6:14 am

        @lakonst: Thanks for the quick response. Just to be sure, I redownloaded the ISO with Media Creation Tool paying careful attention to the version and architecture. Here's what checking the ESD contents shows:
        C:\temp>dism /Get-WimInfo /WimFile:install.esd

        Deployment Image Servicing and Management tool
        Version: 6.3.9600.17031

        Details for image : install.esd

        Index : 1
        Name : Windows 8.1
        Description : Windows 8.1
        Size : 13,116,079,066 bytes

        The operation completed successfully.

        …only one version, so the index 1 should work, but I still get error 11. After more research it looks like there are several problems can cause the error. Apparently even if CMD is started as administrator it's possible that it runs as 32 bit which could cause the problem. I've experimented using some other info I found (most notably which subdirectory to run DISM from), but so far no joy – still getting error 11. Will keep researching, but if anyone has some other ideas I'd be grateful. Thanks!

        Reply

        • lakonst
          September 24, 2017 @ 10:25 am

          @AZMountainGeek: Try to download the WINDOWS ISO file using the Windows ISO Downloader tool and tell me the results with DISM.

          Reply

    • Ricardo Bohner
      April 7, 2018 @ 8:00 pm

      Dear @AZMountainGeek

      I was having the same error as you: "An attempt was made to load a program with an incorrect format." and it took me some hours to figure out what it was.

      When you type in dism /export-image /? it is stated that the compression of the destination image has to be the same as the source image and that is the key to the solution:

      Unfortunatley I don't know how to check the compression state of an image yet but there are only 4 possibilities (at least in Windows 8.1): fast, none, max and recovery.

      So what you have to do is try the /compress switch with that 4 options until you get it right.

      Turns out "max" is not always the compression used by microsoft for my Windows 8.1 install.esd that was on my flash USB it was "recovery". Don't even know what to think of it if that is a low or high level compression but that was what made the command work for me. So good luck, I hope this helps.

      Reply

      • Nate
        November 6, 2018 @ 6:53 pm

        Dear @RicardoBohner
        This after-solution helped me buddy. Thanks a lot

        Reply

      • Kevin
        August 3, 2019 @ 11:01 am

        Thanks Ricardo, this was the answer!

        Reply

  18. Adorianu
    June 20, 2017 @ 7:07 pm

    Now when i want to do everything again i cant even do step 1 with dism /Get-WimInfo /WimFile:install.esd Because it cant find the file while its still there…..

    Reply

  19. Roger
    May 6, 2017 @ 11:57 pm

    Hi agin,

    I used your procedure to extract and export install.wim file on C root, wich worked perfectly but when I run the ISM /Online /Cleanup-Image /RestoreHealth /Source:wim:.. in he console, I wind up once again with that Could not find the files needed for repair. Any idea to solve that problem? I must precise here that I used the exact proper version ( Windows 10 Home ) and that I entered the exact file path too. Thanks in advance, Roger.

    Reply

    • lakonst
      May 7, 2017 @ 10:13 am

      @Roger: 1. If the WIM file is in the C root, make sure that you type correct the DISM command: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:C:\install.wim
      2. Make sure that you have downloaded the correct version of Windows 10 Home (32 or 64 bit).
      3. If you still have problems then follow the instructions on this article: FIX DISM Source Files Could not be Found Windows 10/8

      Reply

  20. Roger Cimon
    May 6, 2017 @ 9:02 pm

    Works just great, man! You're a pro! :-P

    Reply

  21. Red
    April 17, 2017 @ 2:46 am

    thank you for this awesome guide. i was having problem with DISM: Error: 0x800f081f The source files could not be found.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php