Windows 10: Use DISM to Repair Windows 10 Image  

Page 42 of 55 FirstFirst ... 32404142434452 ... LastLast
  1.    22 Apr 2017 #410

    Brink said: View Post
    warning   Warning
    Nevermind. This option doesn't work. It doesn't get applied to the online Windows.



    Thank you @DonCuthbert for the at boot option. :)

    Here's an addition to what you posted for running DISM at boot. What do you think?

    I thought it may be a good idea to use "list volume" with the "diskpart" command first to verify the drive letters of the Windows and USB drives.

    Not specifying a scratch directory would have the command use the Temp directory by default instead. I didn't have an issue by not specifying a scratch directory, so I'm not sure it's an absolute necessity.

    If it works out well for others, I'll add this as another option in the tutorial.

    Attachment 129788
    Sorry, I did not see this until today.

    Yes, use Diskpart - list volume is my standard also. MBR disks often get the drive letters reassigned in Windows RE (C: becomes D:).

    I had the /ScratchDir option as default, because I always get a warning that the results may not work. It's simple enough to do and the DISM processing takes quite a while, so I always felt it would be time wasted if DISM failed and the user might immediately wonder if they should have done the /ScratchDir option. Usually I forget until I see the warning, then I use CTRL+C to cancel, create the ScratchDir and start over. The Temp directory is by default on the X: drive (X: = RAM Disk and limited in size, which is why the warning is displayed). So it seems easier to make the Scratch directory, or else change the TEMP Environment variable to use the disk instead:
    Code:
    set TEMP=C:\TEMP
    or
    Code:
    set TEMP = D:\TEMP
    I have found that if the Windows component store is not corrupt and sfc /scannow works the offline DISM /RestoreHealth should complete 100%.

    However, I have also had it happen, with Windows 10 version 1703, that the offline DISM repair did not fix an issue, but the /Online DISM did fix it. Even though /Online complained about the missing FlightSigning package, CBS.log still showed that DISM fixed the other corrupted file that the offline scan could not repair. Maybe it actually pulled it from Windows Update? Hard to know.


    EDIT: Sorry I did not see your post about it not being applied to the online Windows. What does that mean? Others have said this too. You are repairing your only copy of Windows with DISM, whether Windows is running or not at that moment. In most cases, there is nothing to fix anyway and sfc /scannow works.

    Obviously, offline repair does not insert the missing FlightSigning package to the WIM file, but users are upset that DISM fails with an error that suggests that it did not find the Source files, even if it uses them to fix other errors. Users often do not look in the right log to find what actually happened, so providing a means to see the 100% complete with no error may satisfy them. The concern is usually misplaced because Windows is fine. Only by reading the CBS.log will they see what happened. Running the DISM repair offline may satisfy that concern for those who will not read the log anyway.

    A relevant question would be, "What makes our running, or "Online" Windows look for the FlightSigning package during DISM repair, while repairing the same copy of Windows while it is not running does not look for that package?"
    Last edited by DonCuthbert; 23 Apr 2017 at 00:15.
      My ComputerSystem Spec

  2.    23 Apr 2017 #411

    Hi,

    A relevant question would be, "What makes our running, or "Online" Windows look for the FlightSigning package during DISM repair, while repairing the same copy of Windows while it is not running does not look for that package?"
    That's because running in off line mode the registry is not loaded.

    Cheers,
      My ComputersSystem Spec


  3. Posts : 32
    win10 insider Enterprise
       23 Apr 2017 #412

    fwiw;
    Searched the registry for FlightSigning & it didn't find the often mentioned keys.
    Later on searched it again and it did find it.

    Odd to me it didn't find it today once, and next time it did for exact same search. - Perhaps the problem is within the registry hives & not actually that mum file as offline RepairSource finishes ok easy enough.<thanks Don)
      My ComputerSystem Spec

  4.    23 Apr 2017 #413

    Here is another discussion from MS Community Forums where details on this are described by Willy Denoyette:
    https://answers.microsoft.com/en-us/...ge=2#LastReply
      My ComputerSystem Spec

  5.    27 Apr 2017 #414

    If DISM.exe /Online /Cleanup-image /Restorehealth fails... SOLVED


    and only to often it does.

    This will happen if there are Windows Packages Files installed that are not on the install image or, as in Windows Creator update from April 2017 image, there are some testing leftovers on the image it self that get installed (or were installed during previous updates. I'm not sure when.) but are not properly handled with creators update.

    Fix: download tweaking.com - Windows repair and do the Pre-Scan on step 2 like this:
    Click image for larger version. 

Name:	Untitled-1.png 
Views:	42 
Size:	40.1 KB 
ID:	132188Name:  Untitled-2.png
Views: 944
Size:  56.9 KBName:  Untitled-3.png
Views: 920
Size:  45.4 KB
    The scan result will point to offending files under Scanning Reparse Points (not in the image, I've fixed it already before taking snapshot... sorry).
    In Windows Creator update from April 2017 case those files are:
    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
    and registry keys:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]
    and
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    For other cases it could be other files and keys. They have to be deleted from registry and the hdd.
    DO Reset windows!
    If you do
    Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM: Path to...\install.wim:1 /LimitAccess
    after removing those files and keys from your machine, it will work with no problems at all.

    Have a nice day!

    By the way this particular problem does not get solved with repair install.
    The files and keys MUST be deleted manually taking the ownership and adding read/write rights.
    AND... testing of the inflight components was done at all of yours machines without you knowing anything about it. You could see the processes in task manager though during the last year or so hogging your CPUs and SSDs and RAM. Drop dead Microsoft!

    PS: if sfc /scannow works, and Dism /Online /Cleanup-Image /RestoreHealth fails, you can be sure this is the problem of this kind.


    Edit...
    Here is the complete pre-scan report (I've recreated the issue):

    ┌──────────────────────────────────────────────────────────────────┐
    Tweaking.com - Windows Repair v3.9.28 - Pre-Scan
    Computer: RADNIXXX (Windows 10 Pro 10.0.15063.250 ) (64-bit)
    [Started Scan - 27.4.2017. 13:00:31]
    └──────────────────────────────────────────────────────────────────┘
    ┌──────────────────────────────────────────────────────────────────┐
    Scanning Windows Packages Files.
    Started at (27.4.2017. 13:00:31)

    These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)
    C:\WINDOWS\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

    1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
    The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.

    THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.

    Files Checked & Verified: 3.832

    Done Scanning Windows Packages Files.(27.4.2017. 13:01:45)
    └────────────────────────────────────────────────────────────────────┘
    ┌────────────────────────────────────────────────────────────────────┐
    Scanning Reparse Points.
    Started at (27.4.2017. 13:01:45)

    Reparse Points are OK!.

    Files & Folders Searched: 587.668
    Reparse Points Found: 94

    Done Scanning Reparse Points.(27.4.2017. 13:02:10)
    └───────────────────────────────────────────────────────────────────┘
    ┌───────────────────────────────────────────────────────────────────┐
    Checking Environment Variables.
    Started at (27.4.2017. 13:02:10)

    No problems were found with the Environment Variables.

    Done Checking Environment Variables. (27.4.2017. 13:02:10)
    └───────────────────────────────────────────────────────────────────┘
    ┌───────────────────────────────────────────────────────────────────┐
    [Finished Scan - 27.4.2017. 13:02:10]

    [x] Scan Complete - Problems Found!
    [x]
    [x] You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.
    [x]
    [x] While problems have been found, you can still run the repairs in the program.
    [x] But for the best results it is recommended to fix the problems reported in this scan if possible.
    └───────────────────────────────────────────────────────────────────┘

    .mum files are going in combination with .cat files of the same name hence:

    C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
    C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

    and both are registered with:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    so you need to delete both files and keys.
    Last edited by ibach; 27 Apr 2017 at 06:15.
      My ComputerSystem Spec

  6.    27 Apr 2017 #415

    and as usual ... there is a better method by someone smarter than me... lass destructive and hazardous.
    Please use the same method for other offending packages too. Follow the link:
    Creators update component store shows corruption but unable to repair
      My ComputerSystem Spec


  7. Posts : 2
    Windows 10 Enterprise
       27 Apr 2017 #416

    ibach said: View Post
    and as usual ... there is a better method by someone smarter than me... lass destructive and hazardous.Please use the same method for other offending packages too. Follow the link:Creators update component store shows corruption but unable to repair
    There are quite a few methods mentioned in there. Which one are you referring to? The Offline repair?
      My ComputerSystem Spec

  8.    28 Apr 2017 #417

    sitruk said: View Post
    There are quite a few methods mentioned in there. Which one are you referring to? The Offline repair?
    The one by MonarchX

    MonarchX said: View Post
    To properly get rid of a system package like that you should either use WIM_Tweak (very old and outdated, not recommended) or use another more modern method that always worked for me to get rid of all packages I did not want:
    - Search Google for NSudo 4.3 (or 4.0, both can be found through MDL forums), search for CBSEnum, and download both packages.
    - Run NSudo 4.3 (4.0 may also work) as Admin to launch CBSEnum with All Privelages as Trusted Installer.
    - Take ownership of the correct registry entry in CBSEnum (from the Edit button at the top of CBSEnum).
    - Use the Flat List to view packages, find the 2 Microsoft-Windows-TestRoot packages, and select/highlight both packages.
    - Right-click on highlighted packages, make both packages visible, de-couple both packages, and only then select to uninstall both packages (at once).
    - Restart, search for remaining package registry entries, remove the registry entries (which would not be the in same place, but in ToBeUninstalled or similar-named registry folder).
    - Restart again and you're done correctly uninstalling the package.
    - You can now proceed to safely run DISM RestoreHealth and SFC /ScanNow without fear or having those packages restored and those error re-appearing.
    The "ToBeUninstalled" entry in that post should actually be: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall
    that is what I had added to that solution.

    And the tools used are brilliant for everyday use. Quite a refreshment to use those.
    NSudo 4.3 in combination with CBSEnum is powerful.

    Combining that with tweaking.com pre-scan could solve many more problems with DISM.
    That was how I came to my diagnose and solution independently. The removing package method from MonarchX is far more sophisticated, and the right way to go. (It also brings to focus and removes wow64 elements of the package which I have missed in my post)

    The offline repair does the repair job, but if you do it again online, the problem is still there. If done offline the repair does not take registry into account so it passes as OK, but in reality the problem that prevents it from completion online remains.

    PS: for all those who are not experienced with DISM: it's probably the best thing Microsoft has done to windows ever... Well... if used with care and respect to system dependencies. I think Dino (ntlite author) would agree. In combination with SFC it allows you to repair almost anything. I did not have to reinstall my machine for years now thanks to those tools. And there is in-place upgrade too for bigger or not so obvious problems, as the easy way out (not that it fixes creators update problem!).

    UPDATE...
    After some more analysing...
    Two more files I've found on HDD...
    C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
    AND
    C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat

    Do not know what to think of those. Will ask MonarchX for opinion. Look at that thread.
    Last edited by ibach; 28 Apr 2017 at 04:23.
      My ComputerSystem Spec

  9.    28 Apr 2017 #418

    The roots of the problem with Creatrors Update...


    I've noticed that the problem does not occur in all the cases.

    If installed with update assistant on a machine that has windows 10 updated (all the updates until today) and whose image is healthy (checked with DISM) the problem does not occur which is quite odd.
    (tested on my laptop not the VM)

    In the case when I have not checked the health state of the machine before installing the update, the problem is here (installed with update assistant).

    In fresh install I'm testing now. Will report latter... Done... Problem is here.
    PS on that fresh install: O horror! What a bulls! Ugly dumb Cortana is guiding you trough the setup! Still no Croatian keyboard in the first keyboard menu selection, it does occur in the alternative keyboard selection after the install though. Stupid stupid stupid discriminating *******s every other language is there!... That means no Croatian keyboard in repair wim too. ...Since when the word b_a_s_t_a_r_d is rude?!

    Repair install does not fix the problem.

    After fresh install... +updates:
    1) Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016240)
    2) Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical Preview x64 - April 2017 (KB890830) What the F***?! I've never installed Windows Insider Preview!
    3) Security Update for Adobe Flash Player for Windows 10 Version 1703 (for x64-based Systems) (KB4018483)
    4) Definition Update for Windows Defender - KB2267602 (Definition 1.241.637.0)
    Still error persists....
    dism /online /Cleanup-Image /StartComponentCleanup /ResetBase ... passed with no errors.
    Dism /Online /Cleanup-Image /ScanHealth again ... The component store is repairable. Error persists.
    DISM.exe /Online /Cleanup-image /Restorehealth ... Microsoft update did not fix the error... Failed in all variants but offline.

    (all the 64 bit editions, pro.)

    Still the only solution is to remove packages of Microsoft-Windows-TestRoot
    Last edited by ibach; 28 Apr 2017 at 06:15.
      My ComputerSystem Spec


  10. Posts : 2
    Windows 10 Enterprise
       28 Apr 2017 #419

    ibach said: View Post
    I've noticed that the problem does not occur in all the cases.If installed with update assistant on a machine that has windows 10 updated (all the updates until today) and whose image is healthy (checked with DISM) the problem does not occur which is quite odd.(tested on my laptop not the VM)In the case when I have not checked the health state of the machine before installing the update, the problem is here (installed with update assistant).In fresh install I'm testing now. Will report latter... Done... Problem is here.PS on that fresh install: O horror! What a bulls! Ugly dumb Cortana is guiding you trough the setup! Still no Croatian keyboard in the first keyboard menu selection, it does occur in the alternative keyboard selection after the install though. Stupid stupid stupid discriminating *******s every other language is there!... That means no Croatian keyboard in repair wim too. ...Since when the word b_a_s_t_a_r_d is rude?!Repair install does not fix the problem.After fresh install... +updates:1) Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016240)2) Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical Preview x64 - April 2017 (KB890830) What the F***?! I've never installed Windows Insider Preview!3) Security Update for Adobe Flash Player for Windows 10 Version 1703 (for x64-based Systems) (KB4018483)4) Definition Update for Windows Defender - KB2267602 (Definition 1.241.637.0)Still error persists.... dism /online /Cleanup-Image /StartComponentCleanup /ResetBase ... passed with no errors.Dism /Online /Cleanup-Image /ScanHealth again ... The component store is repairable. Error persists.DISM.exe /Online /Cleanup-image /Restorehealth ... Microsoft update did not fix the error... Failed in all variants but offline.(all the 64 bit editions, pro.)Still the only solution is to remove packages of Microsoft-Windows-TestRoot
    Ok thank you. I actually just gave up and reimaged my computer yesterday. I was running off a dirty upgrade from Windows 7 so this was the push i needed. If i have the issue again when I install that update ill refer to your suggestions.
      My ComputerSystem Spec


 
Page 42 of 55 FirstFirst ... 32404142434452 ... LastLast

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...

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 20:36.
Find Us