It's only usefull to run it on windows, on EVERY other OS it won't integrate updates and we only support running it on a windows host.
Strange, did they change something again? Local UUP Dump App is missing the APPS part for 27863.1000. UUPDump website does not miss them. What do I have to change to fix this? And no, I do not want to use the website, I want to fix my solution.
They forgot Apps again (although first time for WIP build) UUPDump website just map (fetch) apps from previous canary build ( DOWNLOAD_APPS in download script) it's temporary hardcoded hotfix
"MS" is the only company with almost the entire world using its products, at the same time, it's the one that made the most stupid mistakes and "shoot on their foot". And that's because they are very confident that even if they don't put any effort in making its products better, people will continue using it (even with complains and rants).
This thread is about an exploit that was made possible by the original UUP dump dev and @abbodi1406, the building of an ISO from the WU server files is not an officially supported operation, so this is not the thread to blame msft for stuff, they did not provide the appx with the Insider Preview build UUP file set, could it be they will switch from providing the appx this way to providing them in the LCU as they are already present in the MSU too? Who knows, we'll have to see what comes next. (+ considering UUP file sets are provided by the WU servers, the apps are already installed at updating the system)
I am creating an Enterprise image of Windows 11 26100.4061. Sorry if this has been covered already, but is there a way to stop OneDrive and Copilot being integrated into the ISO? I realise it's relatively easy to uninstall these after the installation of Windows has completed, but I'd rather they weren't installed at all.
I havent used uupdump for some time now, but tried it with "Windows 11, version 24H2 (26100.4484) amd64" (all editions) today. I remember it took quite some time in the past and I always grabbed some coffee, watching the CMD. Now here I am, with 16 threads and NVMEs, waiting since like 2 hours+, staring at the script, now beeing at the "Creating Editions" part and adding LCU to wim. The ISOFOLDER still keeps growing for now, so everything seems to be fine. Did other things change or did windows just became exorbitant?
24H2 and up LCU's are now expanded before integration/installation and when they are expanded (and there probably are a lot of small files) the AV will check them all too.
When creating a 26200.5670 image via a "convert-UUP.cmd" script, boot.wim fails to integrate with the 26100.5670 patch, suspected due to interference from Microsoft adding new components to the DISM folder in Windows 11.
@mustafa gotr project posts moved to https://forums.mydigitallife.net/threads/discussion-powershell-gui-uupdump-downloader-project.89441/ Please continue there. Keep this topic to the original subject, please.
A solution has been found and tested. Verify that the Boot.wim file for the 26200.5670 image has no integration error issues. Also, try tweaking boot.wim to integrate PE and SETUP (similar to the official two-volume Boot)
I think you will find that Posts #5883 Jul 6, 2025 and #5884 Jul 7, 2025 above, also applies to said thread The first post refers to the GUI and the second one has been responded to twice in that thread... maybe, both best moved there for continuity... just a thought