Use DISM to Repair Windows 10 Image  

Page 45 of 84 FirstFirst ... 35434445464755 ... LastLast

  1. Posts : 2,557
    Windows 10 pro x64-bit
       #440

    Hi,
    @IronZorg89 :

    It did install the .Net cab package but that does not solve the problem we're disccussing here. In fact I fail to see any relation between the two quite different issues.

    Hi @ fdegrove:

    As mentioned in my post #420, it's a .cab file. I don't know if there is some .NET file in the downloaded package for some reason, but for all know I followed Jessica Deen's procedure and it worked for me.
      My Computers


  2. Posts : 2,832
    Windows 10 Pro X64
       #441

    Hi,

    Unfortunately you've been mislead by the error code I'm afraid. If it solved the problem we're discussing here then what can I say? It won't solve anyone else's problem I'm afraid. Unless they experience problems installing dot Net framework that is.

    One way of checking out is to uninstall the dot Net app and check again, right ?

    Cheers,
      My Computers


  3. Posts : 2,557
    Windows 10 pro x64-bit
       #442

    Hi,
    Unfortunately you've been mislead by the error code I'm afraid. If it solved the problem we're discussing here then what can I say? It won't solve anyone else's problem I'm afraid. Unless they experience problems installing dot Net framework that is.

    One way of checking out is to uninstall the dot Net app and check again, right ?

    Cheers,

    Hi again
    @fdegrove:

    I am sorry if I am misleading anyone. That is not my intention. One question though: Why in your post #421, you said that you have tried with the downloaded .cab file and it worked. The following is your own quote:

    "Hi,

    Thanks for that. I just copied the cab file to c:\ and that worked just fine.

    Cheers, "
      My Computers


  4. Posts : 2,832
    Windows 10 Pro X64
       #443

    Hi,

    It worked in that it did indeed installed that package but nothing more than that.

    Don't worry about it though. I know you meant well.

    Cheers,
      My Computers


  5. Posts : 2,557
    Windows 10 pro x64-bit
       #444

    Hi,
    It worked in that it did indeed installed that package but nothing more than that.

    Don't worry about it though. I know you meant well.

    Cheers,

    Hi @fdegrove:

    You are absolute right. The Jessica Deen's procedure worked with the command line she provided in her procedure done in an elevated Powershell prompt but it's still not working when one uses the normal command line: dism /online /cleanup-image /restorehealth in a command prompt (Admin) as seen in the screenshot I have just taken after trying it in my PC.


    Use DISM to Repair Windows 10 Image-joint-sfc-dism-error-0x800f081f.png

    As you can see in the screen shot sfc /scannow ran without finding any integrity violation, but the command line: dism.exe /online /cleanup-image /restorehealth stopped at 98% with the error: 0x800f081f. The thing is, like most people in this thread, I have tried all of Brink's methods in the first pages, but unfortunately to no avail. I definitely have to get to the bottom of this problem and I will eventually get back with my findings.
      My Computers


  6. Posts : 31,467
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #445

    IronZorg89 said:
    ...the command line: dism.exe /online /cleanup-image /restorehealth stopped at 98% with the error: 0x800f081f. The thing is, like most people in this thread, I have tried all of Brink's methods in the first pages, but unfortunately to no avail. I definitely have to get to the bottom of this problem and I will eventually get back with my findings.
    There is another thread on this. The problem is specific to the Creators Update and appears to be one of Microsoft's own making. Findings are that DISM is looking for a package called Microsoft-Windows-TestRoot-and-FlightSigning-Package that doesn't actually exist. The detailed findings (and a registry hack to 'fix' it) are here...
    Creators update component store shows corruption but unable to repair

    ...now as this 'error' appears to be a false positive (there is no such package and DISM shouldn't be looking for it) it's up to you whether you edit the registry now, or wait for MS to release a proper fix. I'm going for 'waiting', mainly on the grounds that using DISM to do an offline repair works without error, suggesting there's nothing that really needs repairing.
    Use DISM to Repair Windows 10 Image - post# 400
      My Computers


  7. Posts : 4,131
    Windows 3.1 to Windows 11
       #446

    The problem is specific to the Creators Update and appears to be one of Microsoft's own making. Findings are that DISM is looking for a package called Microsoft-Windows-TestRoot-and-FlightSigning-Package that doesn't actually exist. The detailed findings (and a registry hack to 'fix' it) are here...
    Creators update component store shows corruption but unable to repair
    Problem addressed and all questions Answered.
    But always worth repeating..
      My Computer


  8. Posts : 2,557
    Windows 10 pro x64-bit
       #447

    @fdegrove and @Bree,

    Living up to my commitment and following up to my post #444, I did a lot of research on the topic and my understanding is that in order for the command line: "dism /online /cleanup-image /restorehealth" to work, one has to convert the install.esd file to install.wim file; the former being an encrypted form of the latter. That means one has to decrypt the install.esd first to a .iso file and then mount the latter with a new drive letter in File Explorer. This mounted drive now can be used as a reference in the command line:

    Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\Sources\install.wim:1 /limitaccess

    X, being the mounted drive letter (H, D, or E).

    I know, Like "Kyhi" said everything has been addressed and all questions answered. I totally overlooked some essential parts of the thread for not taking the time to read it thoroughly. My bad!. I am going to give it a try and see what gives.

    On the other hand, I also have to agree with "Bree" when he said that the problem is specific to Windows 10's Creators Update. That is totally true, because before the advent of the latter, I never ( not once) had a problem with running: dism /online /cleanup-image /restorehealth. It had always completed successfully 100%, which begs the question: What is going on with Microsoft?. They sure have a reason for changing things all the time, but go figure.

    At one point, I thought it was because of the latest cumulative update: KB4016240. I uninstalled it from update history and try the command line again, but to no avail. I even went as far as doing a repair install (in-place upgrade) and ran the dism command line after. That also didn't work.
    Last edited by IronZorg89; 01 May 2017 at 16:23. Reason: Ortograph
      My Computers


  9. Posts : 31,467
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #448

    IronZorg89 said:
    ...which begs the question: What is going on with Microsoft?. They sure have a reason for changing things all the time, but go figure.
    The 'Microsoft-Windows-TestRoot-and-FlightSigning-Package' would appear to be something to do with Insider development that should have been removed before public release.

    The question is what exactly is "flight-signed"?
    These are certificates that are used during the Windows development process and chain to an internal root.
    https://social.technet.microsoft.com...eview2014Setup
      My Computers


  10. Posts : 2,557
    Windows 10 pro x64-bit
       #449

    @ Bree,

    Thanks for the information. You seem to be well versed with how Microsoft is doing its stuff specifically with reference to your quote:

    "The 'Microsoft-Windows-TestRoot-and-FlightSigning-Package' would appear to be something to do with Insider development that should have been removed before public release."

    Really sorry to say that this is a bit typical of Microsoft. Sometimes, they forget to test something, omit or change something altogether. Like right now, my problem is to find a way to decrypt the install.esd file that is in the 'Sources" folder of my mounted Windows.iso file in order to change to install.wim. The link provided in this thread for the Tech Bench ISO goes way back to 2015 and doesn't seem to work anymore. When I click on it, it opens a blank page with the message:

    "We are sorry, the page you requested cannot be found".

    That is understandable for, it would not probably work with the Creators Update's build. If you have any tips on how to convert this install.esd (electronic software download) to install.wim, that would be greatly appreciated. I am still reading this thread in is entirety to see if I can come up with something. There are lots of 'links' on the web which pretend to do the decryption, but most of them are either laced with malware, or one has to pay..
      My Computers


 

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 Discussions
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 12:47.
Find Us




Windows 10 Forums