OK, just rename appropriately --- Check. Integration is running .... Need another SSD for that, is the Gaming Partition on System NVMe, not ideal ... could be faster .
Was there a picky one? Code: Tool zur Imageverwaltung für die Bereitstellung Version: 10.0.26100.1150 Abbildversion: 10.0.26100.1 Processing 1 of 3 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 2 of 3 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 3 of 3 - [==========================100.0%==========================] [========= 17.0% ]
Result: Code: Abbildversion: 10.0.26100.1 Processing 1 of 3 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 2 of 3 - [==========================100.0%==========================] [==========================100.0%==========================] Processing 3 of 3 - [==========================100.0%==========================] [==========================100.0%==========================] Der Vorgang wurde erfolgreich beendet. Means: Process successful. Unmounting atm, should i upload?
ISO is the OEM one from here - hash match verified. 3,35 to 6,83 GB .... one index .....needs some wimlib-imagex love.
OK, even wimlib-imagex says: Code: Optimizing WIM WIM: m:\Test\install.wim ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Verifying integrity of "m:\Test\install.wim": 6998 MiB of 6998 MiB (100%) done "m:\Test\install.wim" original size: 7166304 KiB Using LZX compression with 24 threads Archiving file data: 15 GiB of 15 GiB (100%) done Calculating integrity table for WIM: 6955 MiB of 6955 MiB (100%) done "m:\Test\install.wim" optimized size: 7122491 KiB Space saved: 43812 KiB ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Not much . Hmm, just realizing the 5900X is a beast here. Peeks to ~4.8 GHz in Single-Load and dism converts and wimlib-imagex .... ....................................ready.
works fine even with renamed files: windows11.0-kb5038575-x64_LCU_961.1.3.msu windows11.0-kb5038603-x64_LCU_1252.1.4.msu windows11.0-kb5040543-x64_LCU_1330.1.0.msu I guess only LCU updates should be in that folder and nothing else so no need to sort all the updates, just copy all LCUs to some folder and install it the same logic should apply to reinstalling the LCU after nfx35 integration, at least we could try it also it installed all SSU updates old SSU were removed after resetbase, so it's fine well, if they are integrating all SSU anyway then I guess we should integrate all SSU as well with W10UI and uup-converter, old versions should be removed after resetbase (or regular cleanup, didn't tested, doesn't matter) anyway no idea if SSU installation order matters
My findings above confirm that . Thing is size it's DOUBLED and even an recompress/cleanup-run with wimlib-imagex bought some >100MB . I am missing anything?
No, It needs to have either one single index which you fiddle with, or you have to perform the same operations for all 3 indexes. Install.wim stores the difference between indexes. Having one 3 26100.1 indexes, of which you update one and leave the rest untouched, isn't exactly a minimum difference.
@watchman.waldo @Paul Mercer thanks this will make the code for 24H2 LCUs much easier i will still try to sort SSUs by version and install the highest only i believe LCUs will skip the others SSUs (based on each SSUCompDB metadata which check the minimum version)
Ya know me ... is all™ still here (dusty not rusty ) aaaaaaaaaaaaaaand my R9 5900X (unlimited then!) ...32 GB soon™ ~64, ..... RTX 4070Ti, doggie was a stubborn digital hermit™ ... NOT LAZY! and he saved some money meanwile ... Then my old Ivy Bridge i5 3570K, 16GB 'HTPC' plus two machines from the 'RUBBLE' (japanese say GOMI == useful, but not used atm ). So any vitual System running here and 2 machines i can misuse™ . ONE is CLOUD™! so.
How did you run ResetBase? just one /StartComponentCleanup /ResetBase command without modifying registry? in my test for .1252 & .961 with modifying DisableResetbase/SupersededActions registry, /StartComponentCleanup removes all .1 & .961 packages not staged as yours, so i guess the registry mod is the reason
Your brains getting slowly elder™ --- i made my self 'disappear' (lit.) . Reads (doggie™), when done™ --- please do not forget the condensed summary and snippets .... ).
no, I didn't messed with the registry at all, just mounted Pro index, installed 3 LCU and then run resetbase 1 and 961 were removed, 1252 are staged Code: Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1252 | Staged | OnDemand Pack | 30.07.2024 5:06 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1330 | Installed | OnDemand Pack | 30.07.2024 5:13 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~~10.0.26100.1252 | Staged | OnDemand Pack | 30.07.2024 5:06 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~amd64~~10.0.26100.1330 | Installed | OnDemand Pack | 30.07.2024 5:13 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~ru-RU~10.0.26100.1 | Installed | OnDemand Pack | 01.04.2024 16:33 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~~10.0.26100.1252 | Staged | OnDemand Pack | 30.07.2024 5:06 Microsoft-Windows-WMIC-FoD-Package~31bf3856ad364e35~wow64~~10.0.26100.1330 | Installed | OnDemand Pack | 30.07.2024 5:13 OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.26100.1252 | Staged | OnDemand Pack | 30.07.2024 5:06 OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.26100.1330 | Installed | OnDemand Pack | 30.07.2024 5:13 Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1252.1.4 | Staged | Security Update | 30.07.2024 5:06 Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1330.1.0 | Installed | Update | 30.07.2024 5:13 Package_for_ServicingStack_1330~31bf3856ad364e35~amd64~~26100.1330.1.0 | Installed | Update | 30.07.2024 5:10 some .1 packages are installed, almost all .1 were removed all 961 were removed as well so there are only staged 1252 (checkpoint) and 1330 as installed
Thanks yeah, it was explained that 24H2 keeps minimum base version as Staged https://forums.mydigitallife.net/goto/post?id=1844036#post-1844036 i guess i will skip registry modification for 24H2 cleanup then
Hello. I am using W10MUI. First i have a question. 1-)Does this tools support install.wims that does not have any language pack integrated. Mui clean? I need this function too much I thought that could be problem because it not worked. So i added my languagepack to install.wim at least has one language. Removed language pack from language packs folder. let basic,speech etc language packs and fod language packs. i thought it could continue. Not worked too. I take this error. Code: Could Not Find D:\W10MUITEMP\extract\langcfg.ini ============================================================ ERROR: Microsoft-Windows-LanguageFeatures-Basic-tr-tr-Package~31bf3856ad364e35~amd64~~.cab is not a valid Windows NT 10.0 LangPack ============================================================ Is this langcfg.ini equal to lang.ini? why it needs that. 2-)Can it add only fod language packs if there is language packs integrated?