DISM Cleanup progress status broken on Win11 22H2?

[marplo]

Hi,
during patching now I've noticed on my system Win 11 22621.1702 and latest NTlite 2023.5.9235 the percentage progress during DISM cleanup is no longer showing up. It's been working fine since it was introduced later last year, including last month patching.

Maybe not a big deal but definitely helps to estimate the time until operation is done.
It worked ok definitely on 22621.1635 (april 2023) and NT build 2023.4.9196

 

[nuhi]

Hi,

yes, it's because the cleanup that had the percentage is not working when ran from Win11 22H2, it would just skip and seemingly be OK, but this other solution actually cleans.
Will make it better when available, as soon Microsoft officially opens up the API, or it's published somewhere how to attach to it properly.

Thanks for the report anyway.

 

[marplo]

One more thing..

Since it was a Server 2016 image the CUs are marked as not applicable via offline DISM.
They indeed fail on Win10 (I believe RPC procedure call error), but on this W11 build whole process completed successfuly and NTLite reported image to be server 14393.5921.

I will test it perhaps tomorrow whether the image is indeed updated without errors.

 

[abbodi86]

They indeed fail on Win10 (I believe RPC procedure call error), but on this W11 build whole process completed successfuly and NTLite reported image to be server 14393.5921.

You mean this error?

Error: 1726

The remote procedure call failed.
An error occurred closing a servicing component in the image.
Wait a few minutes and try running the command again.

that's mostly not a harmful error
sometime DISM just fail to unload the mounted image registry hives
running dism.exe /Get-Packages command against the mounted image afterwards, will recover the error and correctly unload the hives

 

[nuhi]

One more thing..

Since it was a Server 2016 image the CUs are marked as not applicable via offline DISM.
They indeed fail on Win10 (I believe RPC procedure call error), but on this W11 build whole process completed successfuly and NTLite reported image to be server 14393.5921.

I will test it perhaps tomorrow whether the image is indeed updated without errors.

If you meant the latest 14393 (1607) cumulative updates, I actually get "Not applicable" error on integrating it, on Win11 even, works when installing live on a 1607 machine.
Haven't seen any RPC errors, so you're saying it depends on the host, will test that after we sync up on the Win11 integration of 1607 updates.


abbodi86, did you notice the same for the last 2-3 months, that 1607 updates don't integrate? If so, any tips would be appreciated.

I tested now with DISM alone:
SS windows10.0-kb5023788-x64_33ea5888c89d2888b845cf02e8d3950d13d1d1f9.msu
CU windows10.0-kb5026363-x64_8fc1ee2832426d09b9b6088873afc82420609730.msu

DISM doesn't even report an error, it would if an update is unpacked and used via the update.mum.
Just processes too fast, not realistic for a huge update like 1607.

Tried now with /Get-Packages in-between, same.

Let me know if you try, attached the logs.
Thanks.

 

[abbodi86]

nuhi, They removed applicability for "regular" client editions since March, because the extension support for Intel Clovertrail Devices ended
2023-03 CU KB5023697 and later are applicable only for Enterprise LTSB and Server 2016 editions (and WinPE)

you don't get the "not applicable" message when you add msu file
you will have to use the cab file instead to show it