i tried uup dump abbodi1406 batch file on my 13700 based laptop it run fine with 20 thread running, and temp' (C`) was fine 60'c - 70'c which is very good for very high load
uupdump has now implemented "missing appx replacements", a workaround for the builds that are missing apps (26100/26120, 22635/22631/22621) apps from matching working releases will be downloaded for the affected releases the fix will also remove the ISO creation block for the "Cumulative Update" variant for those builds thanks to the one
This is just saying that script work fine On my new laptop I did worried my laptop will crash .. Or will say run as 1 thread cause But for my surprise it did work fine ( Script use lot of resources. I mean a lot !!) ( Ad for what ? 13700. It's a good cpu. I must admit.)
I've noticed the option 'run component cleanup' is sometimes checked by default when creating iso. Does it have any drawback to enable it?
For patch tuesday release? no drawback unless Microsoft change and mess-up LCU, like LTSC / Server 2019 > 2024-04
my bad, I was thinking about Home China, which was recently added and uses Microsoft-Windows-EditionSpecific-CoreCountrySpecific-Package
Home China was always available with zh-cn UUP "Pro China Only" was added separately for build 26200.5001 only it's still a virtual edition, and can be created from Pro edition zh-cn for builds 25300+
What is Microsoft.SecHealthUI_8wekyb3d8bbwe & Microsoft.StorePurchaseApp_8wekyb3d8bbwe? What happens if not integrate them?
Then I can not integrate SecHealthUI, right? It shouldn't cause system damage, right? After I enter the system,I usually disable the Defender service
Windows Defender UI has much more stuff not related to the Defender service, like exploit protection and so on it's just UI app, no damage but it's just 7 Mb. anyway
For me, the script is crashing with the error message "Errors were reported during wim export.". Tried repeating it several times, disabled Windows Defender, even lowered the 14900K's power limits (just to be sure) but nothing works! EDIT: This seems to be a problem with the 22631.3880 build. Tried the older 22631.3737 version and it works fine.