I think this "slowness" will occur with any checkpoint LCUs reinstallation with cleanup because it always try to generate files for all baseline LCU regardless
I prefer to skip NetFx3, file size matters this is because Local Experience Pack installation triggers LCU reinstallation
I agree with @Paul Mercer's comment. Quite apart from that, this topic will probably keep us busy, in one way or another, for some time to come!? Because, as MS writes in a blog post: "We're excited to continue optimizing the delivery of continuous innovation in Windows 11 with new cumulative checkpoint updates. As early as the end of 2024, you will automatically receive this optimization on all devices running Windows 11, version 24H2 or later, as well as on Windows Server 2025." https://techcommunity.microsoft.com...11-checkpoint-cumulative-updates/ba-p/4182552
In my opinion, you should skip the cleanup. The chance that MS will add something is simply too great. Previous tests have shown that if you skip the cleanup, the converter runs through (without 90% CPU load)....
you are forgetting that there are now 3 LCUs and the wim size is significantly larger, if you need that legacy nfx35 stuff then config your settings and enjoy 9 Gb. install.wim nfx35 is useless, update your software Actually, it's better to check if nfx35 is enabled in the msft iso, I bet it's not, so it's obvious which variant is more correct
It's not about the stupid NetFx. The tests have shown that the converter causes fewer or no problems at all if you leave out the cleanup. Apart from the problem that you can't install any more LCUs later in the installed system... If you clean up, too much is deleted and the chance increases that something is going wrong. It's better to stay on the safe side than having to constantly tinker with the system.
There are literally no problems in all tests with cleanup without "stupid NetFx" This is not about cleanup, it's about cleanup+nfx35 Nfx35 is the main issue here, it's not needed in 2024 year
regardless cleanup, multi-LCU reinstallation seems to always generate the files for all of its baseline LCUs and this is very unneeded hustle on the other hand, cleanup will also cause issues for the multi-LCU reinstallation, whenever it's needed (added FOD, enabled feature...)
But again, this is not about cleanup in general, it's about cleanup+netfx35 combo It should be much simpler: if nfx35 is not enabled in the MSFT ISO, you should skip it in any case
Normally I only compile Multi Edition ISOs. But due to the lively discussion here, I just started a test with the 26120.1330 PRO + LXP Workaround + Cleanup. WITHOUT NetFx integration. I would like to know whether this installed ISO will then fetch and install the subsequent update via Windows Update. And / or whether an LCU can be installed manually. This has also not worked with some attempts, but may take some time, hardware is not particularly fast..
Tbh, it's not fair to test this stuff on Dev channel updates, msft could fix that 90%+ cpu usage bug and all other stuff All we have now is single lcu on RP channel
Yes but the results could be different in the future, 24h2 simply wasn't even GA yet, and we don't have checkpoint updates on RP channel At this moment they are avoiding checkpoint updates for some reason
I prefer to do not rush with w10ui and uup-converter updates and wait for the first checkpoint update on rp or retail channel Current situation is a pure mess Dev tests may still be useful if no problems are discovered, chances that they break something are lower in this particular case
I can agree with that. And confusion is a “friendly” way of putting it. Well, let me put it this way: I've now become curious and since I haven't tested it so extensively yet, it could at least be an interesting experience. (Maybe just for me? Maybe not!?)
@abbodi1406 @Paul Mercer 26120.1330 created with converter v108, cleanup, LXP workaround and WITHOUT NetFx..... First surprise: Could not boot from the stick. The problem could be solved by copying the install.wim to an old 26100. After that the ISO boots as usual. Installation without any special features. Manual installation of KB5041872 fails. No reasons given. Next comes the 26100.1457 PRO..... EDIT: In contrast to the first ISO, 26100.1457 could be created and installed without any problems. Also created with converter v108, cleanup and WITHOUT Netfx. Only the LXP workaround was omitted as it was not needed. And the .msu KB5041865 could be installed manually without any problems. So far no problems could be detected.