[DISCUSSION] UUP dump - download Windows 10/11 UUPs with ease

Hello,
I tried to download ISO 26100 24H2 from UUPdump, but while creating the same I got error as attached screenshot, I had this kind of error also with previous build (both RETAIL), what can I do to create such ISO correctly and without errors?

Today's ISO: 26100.3323.250220-1537.GE_RELEASE_SVC_PROD3_CLIENTMULTI_X64FRE_IT-IT.ISO
Previous ISO: Windows 11, version 24H2 (26100.3194) amd64

Both of ITA's languages..

EDIT: Tried now too, errors from log:

2025-03-06 05:32:10, Error CBS Permanent package 'WinPE-Rejuv-Package~31bf3856ad364e35~amd64~~10.0.26100.1' cannot be uninstalled. CurrentState Installed HighestState Absent [HRESULT = 0x800f0825 - CBS_E_CANNOT_REMOVE]
2025-03-06 05:32:10, Error DISM DISM Package Manager: PID=8464 TID=904 Failed initiating changes - CDISMPackage::Internal_ChangePackageState(hr:0x800f0825)
2025-03-06 05:32:10, Error DISM DISM Package Manager: PID=8464 TID=904 Failed to Remove the Package. - CDISMPackage::RemoveEx(hr:0x800f0825)
2025-03-06 05:32:10, Error DISM DISM Package Manager: PID=8464 TID=904 Permanent package cannot be uninstalled. - GetCbsErrorMsg
2025-03-06 05:32:10, Error DISM DISM Package Manager: PID=8464 TID=904 Failed while processing command remove-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0825)

Also with this errors, the ISO works without any problems or conflict??

 

@xscorpionx

It's harmless error that i forgot to suppress or add a check to skip the operation when "LCUmsuExpand" is enabled
will be fixed soon

 

I just got it too. Thanks for confirming that it's harmless.

 

I also got this error but I had "LCUmsuExpand = 0" in "ConvertConfig.ini" file (I did not change any value in this file except for setting UpdtBootFiles to 1). As the error is harmless, all is good.

I am still attaching the ISO creation log + the DISM log to this post for your reference, just in case.

 

Thank you for the info, I wasn't aware of it.

 

I have a question. Since the Dev and Beta 24H2 channels have the same build, what is actually different when building the ISO from UUPDump to distinguish between Dev and Beta or are the ISOs going to be identical?

 

only the build number matters, if it's the same on both channels, then the builds are the same

there is a special case where the build may have been updated several times with different AggregatedMetadata.cab, in which case each build should be checked manually, but usually only the metadata differs

 

Interesting but what about those people who install from a build but do not join any insiders channels, how does their system differentiate on if it will have Beta features or if it will have Dev features?

 

only Canary builds will be opted into the Canary channel by default
builds from other channels will be in Retail after installation, so at this moment 26120 Beta and Dev builds are identical and both are on Retail after installation

you should enroll into correct Insider channel in you want to get all the features and future updates
the Retail channel is never supported on Insider builds, so the end result may vary

 

if you mean "Windows CPC OS" then it's because it was renamed from "Cloud PC"

edit "\uupdump-x86\uup-dump\shared\utils.php", line 138 from

Code:

$isWNC = str_contains($updateTitle, 'Cloud PC');

to

Code:

$isWNC = str_contains($updateTitle, 'Cloud PC') || str_contains($updateTitle, 'Windows CPC OS');