Use DISM to Repair Windows 10 Image  

Cr00zng,

Consider performing an in place upgrade repair using 1909 or 2004:
Repair Install Windows 10 with an In-place Upgrade

zbook said:

Cr00zng,

Consider performing an in place upgrade repair using 1909 or 2004:
Repair Install Windows 10 with an In-place Upgrade

. That was going to be my next suggestion also.

- - - Updated - - -

Cr00zng said:

Thanks for your help...

I changed the group policy, ran the "gpudate" command and downloaded "dotNetFx35setup.exe", but it would not install. Ran the DISM command as specified in the second link, but did not work:

Attachment 284486

Dism still cannot find the "install.wim" file.

PS: The second link has a spelling mistake, "ism" instead of "dism"but ran it anyway in red, when the "dism" failed.

You could tell right-off the bat that was a typo for "dism". At any rate, try the repair install aka In-place upgrade as suggested by @zbook and run the command-lines (CL) again and see if that has helped.

Check if your source file is actually install.wim and not install.esd. Also, check if Index:1 matches your Edition (often Pro is Index:6). Install.esd may not work as a source, but perhaps if you use /Source:ESD:[path] and the correct Index it might work.

For .NET, run optionalfeatures.exe and install .NET from there. You may not require .NET 3.5 at all. If you have any software that requires it, it would have been requested during the install of that software. You should be able to enable or disable .NET 4 from here.

Try getting the latest .NET Cumulative Update instead and install that after the .NET that you need is enabled.

If it is an install.esd, you can mount the ISO and change it to install.wim.

Not really necessary, DISM works with either as long as you tell it what it is using.

check if Index:1 matches your Edition (often Pro is Index:6)...

Check that with this tutorial.

See Full Details about a Windows 10 ISO file

I am wondering if the issue is not related to the MCT (ISO) for the latest upgrade Windows 10 May 2004, because some users have reported at the beginning when used, it gave Windows 10 Insider Preview (latest build). I don't know if that has been corrected.

As a cautionary measure, would not it be safer to roll back with a MR image to 1909 and use the ISO from UUP Dump for 1909 in case the issue persists in that build. That would be a safer bet.

zbook said:

Cr00zng,

Consider performing an in place upgrade repair using 1909 or 2004:
Repair Install Windows 10 with an In-place Upgrade

Thanks Z...

If DISM won't work, I'll just install Windows as new. I am just curious now why DISM does not work?

- - - Updated - - -

Bree said:

Check that with this tutorial.

See Full Details about a Windows 10 ISO file

I actually did, here's the result:



This is the system I am trying to fix:



This system had been updated from Win 7 Pro 64-bit 3-4 years ego. It's been working just fine since then.

Attempting to fix the image with DISM has the same result:



I am must be missing something, but cannot figure it out... Any help would be appreciated...

@Cr00zng,

Out of curiosity can you run sfc /scannow and a system diagnostic report

IronZorg89 said:

@Cr00zng,

Out of curiosity can you run sfc /scannow and a system diagnostic report

The "sfc /scannow" was one of the first command that I've ran, when the failed update showed up first. It showed the same as it does now:



I did not run the system diagnostic report yet, but did now:



Other than some information about the Even Log size, there is not much going on. Well, other than the update failing that is:

Installation Failure: Windows failed to install the following update with error 0x8007371B: 2020-06 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4560960).