Page 2 of 3 FirstFirst 123 LastLast

  1. Joined : Feb 2015
    Bamberg Germany
    Posts : 12,916
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
       22 Mar 2015 #11

    I just use Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc/scannow&Dism /Online /Cleanup-Image /RestoreHealth&sfc/scannow&pause and that's enough. No fancy techniques needed anymore, it's been fixed.
    Attached Thumbnails Attached Thumbnails Capture.PNG  
      My System SpecsSystem Spec

  2.    22 Mar 2015 #12

    adamf said: View Post
    Check your file E:\Sources\install.wim exists. You could have an ISO that contains an esd not a wim.

    You need a space and between /Cleanup-Image and /RestoreHealth also.
    That's it, my file extention is esd. What do I need to do now? Thanks.
      My System SpecsSystem Spec


  3. Joined : Nov 2013
    Posts : 804
    10 Pro Preview x64
       22 Mar 2015 #13

    jjthenovice said: View Post
    That's it, my file extention is esd. What do I need to do now? Thanks.
    You need to convert your ESD to a standard ISO not an ESD ISO.

    I just checked the tutorial and it says nothing about it but when I ran it it a few days ago I'm sure it gave me 4 options one of which was "Create Standard ISO" and one was "Create ESD ISO" It seems the tutorial might have changed. Download the utility again and run it again and then point the path in the above command to the generated .wim (assuming it makes an iso with a wim).

    If that doesn't work you'll have to ask @Kari on this thread Windows 10 Forums why you are getting an esd not a wim in your iso.
      My System SpecsSystem Spec

  4.    22 Mar 2015 #14

    adamf said: View Post
    You need to convert your ESD to a standard ISO not an ESD ISO.

    I just checked the tutorial and it says nothing about it but when I ran it it a few days ago I'm sure it gave me 4 options one of which was "Create Standard ISO" and one was "Create ESD ISO" It seems the tutorial might have changed. Download the utility again and run it again and then point the path in the above command to the generated .wim (assuming it makes an iso with a wim).

    If that doesn't work you'll have to ask @Kari on this thread Windows 10 Forums why you are getting an esd not a wim in your iso.
    Thanks for the reply. I downloaded WinReducer and copied the install.esd to my hard drive and converted it to WIM. Then I just pointed to it on hard drive and it worked. When I ran sfc /scannow it found and fixed the corrupted files. Thank you for the help, it got me pointed in the right direction.
      My System SpecsSystem Spec


  5. Joined : Nov 2013
    Posts : 804
    10 Pro Preview x64
       22 Mar 2015 #15

    Good news
      My System SpecsSystem Spec

  6.    22 Mar 2015 #16

    May I ask a quick question? Why did I have to run this command: Will I need to keep the install.wim? It's currently in the root directory of my C drive. As stated earlier I had to convert the install.esd on my iso to install.wim. Thank you.
      My System SpecsSystem Spec


  7. Joined : Nov 2013
    Posts : 804
    10 Pro Preview x64
       23 Mar 2015 #17

    Generally the dism command will repair the component store by looking on the internet. However if this doesn't work you need to use a different source. This can be either another windows installation or a .wim file. Generally an ISO will contain a .wim but (depending where you got it or how you made it) it may contain a .esd file instead. That is why you had to convert it - your ISO didn't contain a wim.

    Now I have run it once, and also run sfc /scannow dism works fine without specifying the .wim. I can just enter the command Dism /Online /Cleanup-Image /RestoreHealth without additionally specifying the /source parameter like @Cliff S did in the post above).

    So no, if you can run dism and sfc now without error you don't need to keep it. You can always convert the esd again if you do. You will not need it for anything else as you can re-install from the compressed ISO you have.

    If you have lots of space though you can just leave it - it will not do any harm (except make your backups a bit slower).
      My System SpecsSystem Spec

  8.    23 Mar 2015 #18

    adamf said: View Post
    Generally the dism command will repair the component store by looking on the internet. However if this doesn't work you need to use a different source. This can be either another windows installation or a .wim file. Generally an ISO will contain a .wim but (depending where you got it or how you made it) it may contain a .esd file instead. That is why you had to convert it - your ISO didn't contain a wim.

    Now I have run it once, and also run sfc /scannow dism works fine without specifying the .wim. I can just enter the command Dism /Online /Cleanup-Image /RestoreHealth without additionally specifying the /source parameter like @Cliff S did in the post above).

    So no, if you can run dism and sfc now without error you don't need to keep it. You can always convert the esd again if you do. You will not need it for anything else as you can re-install from the compressed ISO you have.

    If you have lots of space though you can just leave it - it will not do any harm (except make your backups a bit slower).
    Thanks for the info. Things sure were more simple in the old days (Win 3.0 and 3.1) then "alive in 95 (Win95) the fix in 96. Just a little nostalgia..... Again thanks...
      My System SpecsSystem Spec


  9. Joined : Nov 2013
    Posts : 804
    10 Pro Preview x64
       23 Mar 2015 #19

    jjthenovice said: View Post
    Thanks for the info. Things sure were more simple in the old days (Win 3.0 and 3.1) then "alive in 95 (Win95) the fix in 96. Just a little nostalgia..... Again thanks...
    Well I suppose so considering that there wasn't a component store to even repair - you had to guess (thus the 'dll hell' expression).

    A bit like a caveman complaining about their fire going out and yearning for the days of raw meat when everything was easier

    And you are of course, welcome
      My System SpecsSystem Spec


  10. Joined : Jan 2015
    Spain
    Posts : 115
    Windows 8.1/10 TP 9926
       23 Mar 2015 #20

    adamf said: View Post
    Generally the dism command will repair the component store by looking on the internet. However if this doesn't work you need to use a different source. This can be either another windows installation or a .wim file. Generally an ISO will contain a .wim but (depending where you got it or how you made it) it may contain a .esd file instead. That is why you had to convert it - your ISO didn't contain a wim.

    Now I have run it once, and also run sfc /scannow dism works fine without specifying the .wim. I can just enter the command Dism /Online /Cleanup-Image /RestoreHealth without additionally specifying the /source parameter like @Cliff S did in the post above).

    So no, if you can run dism and sfc now without error you don't need to keep it. You can always convert the esd again if you do. You will not need it for anything else as you can re-install from the compressed ISO you have.

    If you have lots of space though you can just leave it - it will not do any harm (except make your backups a bit slower).
    Thanks for the insightful explanation, Adam

    So, I've been looking into the system hard lock-ups that some of us have been suffering since the release of build 10041, and it seems that the cause may be the WDDM 2.0 driver we get through Windows Update for NVIDIA and AMD cards.

    So, I've performed yet another clean install of build 10041. This time, however, I disabled WU driver download at the end of the installation. I've installed the drivers I needed from the hard disk and I'm using Catalyst 14.12 Omega for Windows 8.1; which means no WDDM 2.0 driver, but that's something I did want on purpose.

    So far, no hard lock-ups, but I'll keep on testing throughout the following days.

    PS: And yes, I used the same trick again to restore the functionality of SFC because, once again, it found corrupted system files after an utter clean install process.

    Regards,
    Luis.
      My System SpecsSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
DISM - Repair Windows 10 Image
How to Repair Windows 10 Image using DISM If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem. For example, you would use DISM to fix...
Tutorials
Solved How do i delete system files on other HDD?
i just installed windows 10 onto my first SSD (Made it my master drive) and i'd like to delete every file and folder on my old HDD except the one in which all my games are installed (Not program files its a folder labeled "Games" in the root...
Installation and Setup
0x800f081f Got error in SFC & DISM too in build 10240
i did these all scans but nothing worked im getting this error 0x800f081f does anyone had it tooo?? pls help .. :huh: "dism /online /cleanup-image /scanhealth dism /online /cleanup-image /checkhealth dism /online /cleanup-image /restorehealth...
General Support
Solved Can't even build 10041
Hello, everybody! I have read a lot about upgrading my Windows, put nothing helped. I have Windows 10 build 9926 on my PC and when I want to upgrade it I get the 0x80246017 error.. I tried a lot to fix it but I still can not upgrade my OS. When I...
Windows Updates and Activation
Iso for build 10041
I would like to know where to download the iso for build 10041 if it is available. Thanks.
Installation and Setup
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 13:26.
Find Us
Twitter Facebook Google+



Windows 10 Forums