BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow

philc43 said:

That's great! You are doing really well.

in the command you used:
X:\Sources>DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:E:\sources2\install.wim:2 /ScratchDir:C:\Scratch

The 2 is called the index number. Are you sure this is the right number so that it matches your installation. In a previous post #21 you were using index number 1. You can find out what all the index numbers are in your particular ISO by using the following command:

dism /get-wiminfo /wimfile:<Drive Letter>:\x86\sources\install.wim

Substitute <Drive Letter> for the actual drive letter for your mounted ISO.
This will give you a list of the index numbers and what version of W10 they refer to.

Hi , index 2 was indeed a typo. I verified in the console that I typed index 1.
In fact there are no other indices available besides index 1.

I will try the files posted by Bree next.

I took all of the clean files provided by Bree, and copied only the required .cat and .mum files to a separate directory. This allowed me to fix all the KB4056892 related .cat & .mum files reported by DISM as errors.
There was no replacement of the good files, just the bad files.

Overall, we've fixed 32 errors related to KB4056892, and the total error count went down from 144 to 112 per attached dism7.txt

I also attached the tracking excel file, which notes that we've fixed items 40, and 42-72 (32 items total).
I probably would need the rest of the files to make progress.

Detailed procedure:
I used the following commands after booting with a windows 1803 USB stick.
Where <mydir> is the path to the directory containing the required .cat and .mum files.

for /R e:\<mydir> %f in (*.cat) do copy %f c:\windows\servicing\packages <-- this copies all the cat files
for /R e:\<mydir> %f in (*.mum) do copy %f c:\windows\servicing\packages <-- this copies all the mum files

The directory included not only the packages starting with 309 and ending with 570, but also the
Package_for_RollupFix~31bf3856ad364e35~x86~~16299.192.1.9

I then re-ran the following command
X:\Sources>DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:E:\sources2\install.wim:1 /ScratchDir:C:\Scratch

As mentioned before, <mydir> only contained the files found by DISM as corrupted, the good files were not included, and hence not over-written on the affected machine.

Sure I can set up a new (different) PC with an x86 windows 10 version.
How do I start with the right version of windows so that I can add the appropriate images to it?
I assume if I start with an 1803, I wouldn't be able to install many of the previous images.

Just wanted to provide a quick update - I was able to set up a 1709 x86 en-us machine, and will be working on copying the relevant packages and checking them for corruption with DISM on the affected machine within a couple days as time allows.

Sorry for the long delay - very busy with the kids, difficult to do anything :)

I was able to fix all the .mum and .cat files associated with a clean 1709 windows install by copying them from a healthy computer. However none of the packages for KB updates were present on the healthy computer.

The error count is now down to 72 errors, as shown by both dism8.txt and rev3 of the excel file.

I have downloaded all the .msu files for the required packages, just need advice on how to install them on the healthy machine. Note that there is no windows license on the healthy machine - I used a workaround described on the web using a KMS key

You Dont Need a Product Key to Install and Use Windows 10

I used the appropriate KMS key from here.
https://docs.microsoft.com/en-us/pre...612867(v=ws.11)

Please let me know how to extract the KB .msu packages on the healthy machine.

Thanks again!

ok - I was able to extract all the KB packages on the healthy PC, and replaced the corrupted .mum and .cat files on the affected PC.

The CBS Manifest corruption count is now at 0, however there are still errors.
See dism9.txt