Use DISM to Repair Windows 10 Image  

Page 47 of 60 FirstFirst ... 37454647484957 ... LastLast

  1. Posts : 7,567
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       01 May 2017 #460

    mikiep said: View Post
    @HippsieGypsie Forgot the index number;

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:G:\sources\install.wim
    ....might instead try
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:G:\sources\install.wim:1 /LimitAccess
    ( :1 usually is Windows Pro, :2 usually is Home)
    Thank you, mikiep. I shall try that first. I have home so it's 2.
      My ComputersSystem Spec

  2.    02 May 2017 #461

    wim - esd

    You can use either wim or esd image for what's the format concerned.
    For more info look HERE
    For ESD:
    Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:Full Path to install.esd file:1
    Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:Full Path to install.esd file:1 /limitaccess
    For Wim:
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess
    will do the job of recognizing the format.

    The trouble with esd is not the format it self, but, esd made with MediaCreationTool sometimes (it's Microsoft so read that as most of the times) is, by its content, faulty. I've tested these esd images converting them to wims, and the error persists for both formats. MSDN or retail wims are tested by microsoft for this functionality, but i believe that MediaCreationTool ones simply are not. They wait for us to do that, report and fix the problems. It's cheaper that way, and holiday last longer if they do not have to do that (Just as they sometimes leave peaces of testing software on Retail and MSDN images just to do some hidden testing on our working machines with out letting anyone know about it.)

    Have a nice day.

    PS convert wim from MSDN or retail to ESD and try the commands. They work all right. Take a few seconds more to complete but it actually (pays off in space/time ratio to refer to Mr. E. from the post above).

    And... Albert was right... at that point of time, he did. A bit latter it had consumed it. We are using "bugs" and "glitches" as an excuse to obtain artificial profit. Nothing for something kind of a way. That's not over-unity, that's absolute absence of humanity (in the manner of: we do not know how to define humanity no more). Do not fail to see that Albert's "technology" equivalents greed, that is what "appalling" is about. The old bast*rd was a poet above all. Just ass Albert was a poet, Microsoft is actually lead by no fools.
    Last edited by ibach; 02 May 2017 at 03:57.
      My ComputerSystem Spec

  3. Bree's Avatar
    Posts : 9,532
    10 Home x64 (1809) (10 Pro on 2nd pc)
       02 May 2017 #462

    ibach said: View Post
    The trouble with esd is not the format it self, but, esd made with MediaCreationTool sometimes (it's Microsoft so read that as most of the times) is, by its content, faulty.
    Not quite, apparently. The 'fault' in 1703 seems to be not in the .esd or .wim, rather it is in the database that DISM uses to find what should be installed. When run online the database says there's a 'flight signing package' but this doesn't exist in the esd/wim. When run offline as in post #400 of this thread DISM doesn't try to look for it, so runs successfully to 100%.

    Boot with Windows 10 version 1703 Official install media (mine has both x86 and x64). Use SHIFT-F10 to get a Command Prompt. Create a folder called C:\Scratch. Run this command (for Home Edition -- Pro would use "...install.esd:1"):
    DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch
    post #400
      My ComputersSystem Spec

  4.    02 May 2017 #463

    Bree... I was merely explaining wim-esd general differences. Nothing of what I have said in my last post has a thing to do with this particular error. So I do not understand "Not quite, apparently." part.
    The MediaCreationTool image (esd or converted to wim, all the same) has returned error in numerous cases, when MSDN or Retail image of the same build did not.
    Not that you are wrong about Windows 10 version 1703 where all of the images fail online and none (for MediaCreationTool read none as current) does fail offline (If no other errors of course, so 100% is actually around 50% average and sfc comes in handy in most of the other 50%).
    About of the content of the image... It is faulty. We did use INSTALL.wim/esd to install in the first place. And we got to the error using it (as well as with windows update). The error is there even if we do clean install with current MediaCreationTool or any other 1703 image. I've tested that. The DATABASE that DISM uses to find what should be installed is part of the image. DISM is instructed to read REGISTRY that has been written by install image it self. If working offline, DISM is instructed not to read registry and that is a workaround but not the solution to the error of 1703 build problem. It merely allows other errors to be fixed and OS to be repaired when DISM fails online on 1703 build. Uninstalling the offending package is the solution as Microsoft will finally confess.

    PS /ScratchDir:C:\Scratch I like a lot (if not enough ram particularly... though... D: if available could speed things up in some cases)
    Last edited by ibach; 02 May 2017 at 08:58. Reason: cosmetics
      My ComputerSystem Spec

  5.    02 May 2017 #464


    As "Brink" rightfully pointed out in his post #455:

    "DISM is currently pretty much broken right now in the Windows 10 Creators Update"

    Pretty much a fair assessment. I couldn't agree more.

    I think this problem is definitely of Microsoft's own making and therefore for them to fix. Overall, I am also started to get a little bit uneasy with all the hassle this error (0x800f081f) is generating fearing that I might break something else while trying to fix it. Besides, my PC is running pretty smooth right now and all other command lines run successfully except for the one at issue in this thread.

    sfc /scannow found no integrity violaltions
    dism / online /cleanup-image /checkhealth
    DISM /Online /Cleanup-Image /AnalyzeComponentStore
    DISM /Online /Cleanup-Image /StartComponentCleanup

    all run successfully.

    I think that I am going to leave at that and wait for the next cumulative update and see if Microsoft will fix this problem. They sure are well aware of the problem and the downtime they are causing everybody having to deal with it.
    Lastly, I cannot thank you enough for your patience and help. .
      My ComputerSystem Spec

  6.    06 May 2017 #465

    "Error: 0x800f081f" possible fix for windows build 15063

    For any of you who are getting the "Error: 0x800f081f" whatever you try and who are on the latest creators update build 15063: there is something wrong with the dism command in this build, it has nothing to with your computers.

    I found the answer to this and a fix for the problem on this website:*
    Windows 10 V1703: Fix for DISM error 0x800F081F | Borns Tech and Windows World
    This fixed everything for me, dism now works fine.

    Hope this helps people, it took me days before I found this website.
      My ComputerSystem Spec

  7.    06 May 2017 #466

    That article points back to @Eagle51 's post here at Tenforums as the fix:
    Creators update component store shows corruption but unable to repair - Page 3 - - Windows 10 Forums

      My ComputerSystem Spec

  8.    06 May 2017 #467

    Funny that every week or so a user comes here and say the same thing
      My ComputerSystem Spec

  9. Brink's Avatar
    Posts : 34,423
    64-bit Windows 10 Pro build 18290
    Thread Starter
       06 May 2017 #468

    At least they're only trying to be helpful. :)
      My ComputersSystem Spec

  10.    06 May 2017 #469

    Brink said: View Post
    At least they're only trying to be helpful. :)
    Agreed. :)
      My ComputerSystem Spec

Page 47 of 60 FirstFirst ... 37454647484957 ... LastLast

Tutorial Categories

Use DISM to Repair Windows 10 Image Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone

Related Threads
SFC Scannow or DISM/RestoreHealth using Image in Performance & Maintenance
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Hello, everyone, I've managed to resolve most of my problems with build 10041 by making SFC work. I've opened a thread on Windows Insider's forums explaining how to do it. Check it out:...
I've just upgraded Windows 7 64-bit HP OEM to Windows 10 Technical preview 64-bit. Extracted the install while booted within 7, install went smoothly, opted to keep all my files, and once the install was finished it went to boot Windows 10. It hung...
I installed the 32 bit version of W10 on an old Acer laptop to get back up to speed with developments, and one of the first questions or issues that cropped up is when using W10's disk image utility to make a system image. I deliberately wished to...
Windows 10 TP Repair and Recovery Features in Installation and Upgrade
I'm currently running the 10 TP in a virtual machine. I see that the various boot and repair options can be accessed by <shift> Restart from the desktop, however F8 during boot doesn't appear to work. Can someone who is actually running this on...

Tags for this Thread

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 00:48.
Find Us