[ARCHIVED] Windows Editions Reconstruction Project

When Dism++ is installing LCU, it is rundll32.exe running ---> Success

When Dism.exe is installing LCU, it is Dism.exe running ---> Failure

 

Speaking about 10240, I haven't yet a solution but i spotted something easy to overlook.

When the LCU fails to install, it's said that no changes were made to the image.

That's a lie!!!, the image is corrupt.

After you get the 1st error you can't do anything else, not even a (not needed) resetbase.

In short, after you get the first error, even if you do the right thing (say install an older CU) you keep getting an error.


In short, each test requires that you unmount discarding the changes, and remount, or any further attempt, no matter if right or wrong, will be hopeless.

 

Yes. You are right. Unrecoverable damaged.

 

Dism++ shows "\??\C:\Windows\WinSxS ---> Succeeded
Dism.exe shows "\??\X:\Windows\WinSxS ---> Failed

 

Your method is right, successfully changed the cumulative update to targetState="Staged", thank you.

Code:

<?xml version='1.0' encoding='utf-8'?>
<Session version="8.0" id="372_48204984" client="DISM Package Manager Provider" options="0" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" operationCovered="33793" correlationVector="l7pa96BsI0+F3CRR.1" Queued="2022/09/17/22:44:48" Started="2022/09/17/22:44:48" Complete="2022/09/17/22:47:24" status="0x0">
    <Tasks>
        <Phase seq="1">
            <package id="Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.22621.1" name="Windows Core Edition" targetState="Installed" options="4"/>
            <package id="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22621.521" name="Windows Professional Edition" targetState="Staged" options="4"/>
        </Phase>
    </Tasks>

 

Target OS image: 10240.16384

Code:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"SystemRoot"="C:\\Windows"
"PathName"="C:\\Windows"

Running OS image: 19041.1

Code:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"SystemRoot"="X:\\Windows"
"PathName"="X:\\Windows"

So,
Dism++ uses 10240.16384 C:\Windows\WinSxS ---> Success
Dism.exe uses 19041.1 X:\Windows\WinSxS ---> Failure
?

Or,
the script should be run under 10240 environment
?

No. Dism++ author only knows. Let it go!

 

For the record, I'm trying an install of 10240 regressed to .16384 with an in place "upgrade", and WU offers the latest SSU from May 2022, and the CU KB4505051 from May 2019.

Clearly MS doesn't use Dism++

 

So you can use rundll32 in script and make it automatic?

 

hahaha funny

 

Only if you can provide me with a feasible solution.

 

You need to login to view this posts content.

 

Use the dism in 10240 ADK?

 

You need to login to view this posts content.

 

No, I had tried. It is the same as from 10240 image.

 

Yes, I dit it too. (But the registry in 10240.16384 image was changed to X:.)

Dism.exe failed, no mater C: or X:. But Dism++ can make it. Amazing.

 

Even though the registry has changed to C:, it still looks for X:.
X:\ Is not a real drive letter, so it is easy to have problems. I often encounter the problem that files cannot be found under X:\Windows\WinSxS\Catalogs , but after solving the problem, I find that they are not associated with X:\.

 

Would Dism++ author share the solution?

 

I will try to install the package containing ssshim.dll separately, which is more helpful for troubleshooting.

 

Thank you so much for participating in such an issue trouble-shooting.

 

Q: xinso, why did you say only Dism++ can integrate LCU to 10240.16384?
A: It's because only Dism++ can integrate then.