[DISCUSSION] Windows 11 Insider Preview Build 25387.1 (PC) [Canary Channel - zn_release]

Aren't they just doing comedy?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

that's not the point, uup converter (and W10UI?) can't integrate updates correctly on older Windows versions (even on 22621) because it can't extract SSU (files inside SSU, not SSU file from MSU)
so it works only on ~25XXX host OS

 

Yes, but that's easy to fix. It now works for me in Windows 10 again.

I extracted these three files to the bin-folder of the converter.

Code:

~\UUPs\professional_de-de.esd\3\Windows\System32\expand.exe
~\UUPs\professional_de-de.esd\3\Windows\System32\cabinet.dll
~\UUPs\Windows11.0-KB5027849-x64.msu\DesktopDeployment.cab\dpx.dll

and added the files to the converter v90 in line 320 (maybe only the expand.exe is necessary).

Code:

set _fils=(expand.exe,cabinet.dll,dpx.dll,7z.dll,7z.exe,bcdedit.exe,bfi.exe,bootmui.txt,bootwim.txt,cdimage.exe,imagex.exe,libwim-15.dll,offlinereg.exe,offreg.dll,wimlib-imagex.exe,PSFExtractor.exe,cabarc.exe)

Now the converter script can extract all fies fron the SSU-25387.1200-x64.cab.

 

in my tests expand.exe from 22621.1778 build and the latest dpx.dll from DesktopDeployment.cab are enough even on Windows 7 x64
I don't know why we need cabinet.dll, it works fine without it on fully updated Windows 7 x64 system
it works even with expand.exe from Windows 7 x64 + latest dpx.dll

for "set _fils" variable in uup converter script it's enough to just add expand.exe, but expand.exe (from Windows 7 x64 and later) + dpx.dll (from the latest available DesktopDeployment.cab) should be in the bin folder

there's also another issue with clean up: uup converter and W10UI shows a lot of 100% entries in progress log
I was trying to reproduce it on 25387.1 host OS and got the same results
the good news is that it doesn't try to clean it up in an infinite loop and it gets to normal after ~3 minutes

for W10UI fix I just edited the script and replaced every expand.exe with new variable in bin folder, works fine

anyway, seems like we need new W10UI and uup converter versions
it should copy expand.exe from host OS and dpx.dll from DesktopDeployment.cab to some temp folder and use it from there
again: cabinet.dll is not needed in my tests even on Windows 7 x64, but maybe I'm missing something

I'm still concerned about current situation with cleanup, maybe something should be changed in scripts as well

 

This has nothing to do with the uup converter or W10UI.That comes straight from the servicing stack. After starting the cleanup process, the stack performs 53 loops bevor the 54 loop terminales the cleaning. All loops are terminated without errors. Dism is just reporting it. You also get the same output, if you run dism with cleanup in the terminal against an offline image without any script. So I guess that's normal. Or a bug in the servicing stack.

The other more serios problem is the error 0x8000ffff when trying to process the steps Core to Pro and/or CoreN to ProN without cleaning. There ist a conflict with this Package (Core to Pro):

Code:

Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25387.1 (superseded)
Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25387.1200 

For some kind of reason, the servicing stack tries to use the the superseded package 25387.1 to upgrade the edition instead of using the new one 25387.1200. This results in the error

Code:

Unexpected version mismatch for transmog operation [HRESULT = 0x8000ffff - E_UNEXPECTED]

After performing the cleanup task with the many 100% lines, the right package is used (25387.1200) and and no errors at all.

 

@TS2008 I'm aware about upgrade problem, but didn't know this is because it's trying to use superseded package
everything sounds to me like this build (or updates for it) is bugged and something will be fixed in newer release

as I remember some months ago it wasn't possible to install self created LCU MSU, only CAB+PSF updates were installing correctly, and after that they have released WIM LCU

there's plenty of time till august, hope they can fix at least upgrade from Core to Pro

 

I performed several tests in the terminal without the script, just doing the steps manually with the 25387.1 (add SSU, LCU, cleanup, change taget edition etc). Changes noting. The strange behavior is related to the servicing stack v10.0.25387.1200 and I don't see a way to bypass this. Maybe it is a bug in the servicing stack or this behavior is now by design.

 

You need to login to view this posts content.

 

Is it possible to share dism.log for where cleanup is performed?
it may explain the many 100% lines (although it's mostly servicing stack bug)

also, does the "many 100% lines" occur if you use Windows_InsiderPreview_ADK_en-us_25387?

 

It makes no difference whether Windows 10 (19045.3031) or Windows 11 (25387.1200) is used or with the ADK_25387 in both OS. The results are each time the same.

And after reading and interpreting the log several times, I believe that the behavior is by design with the servicing stack 28387.1200. The main cleaning session ist splitted in several sessions and each of these sessions generates a 100% line. All sessions run without errors and after that, the main session ends with "The operation completed successfully.". No Errors at all. So I assume this is normal behavior at the moment.

The other problem with the error 0x8000ffff without cleaning also remains in all OS.

My logs were submitted to you (logs_25837_13062023.7z), because the forum ist not happy with the file.

 

Thanks

i think the multiple 100% lines are related to FOD packages, they are cleaning them each separately

Code:

Maint: Deepclean: Trying to prune package Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.25387.1

53 packages

the easier solution for now is to suppress output for dism cleanup command for builds 25380+
and skip edition-upgrade updating if cleanup option is OFF

 

Another fake Cumulative Update got pushed.

 

what update? I don't see anything new, 1200 was released 1 weak ago

 

You need to login to view this posts content.