The impression I'm getting is that checkpoint updates are true LCUs. A true Latest Cumulative Update (LCU), only needs to be installed once. So you don't need to install every LCU from 26100.1 up to 26100.1742. Otherwise, it wouldn't be cumulative. Once your on 1742, it's a cumulative checkpoint, and you can delta update to 1876. And you will only need to delta update from 1876 to the next update version. But there will be future LCUs (checkpoints). Feel free to correct me if I'm wrong about this. Edit: It's not called "delta update" now. It's being referred to as "binary differential" update. MSFT must have fancy names to ensure that the egos of younger developers are fed.
MSFT is the one who needs to be corrected, the morons need to overcomplicate all only because some turd came up with this. They should not release 10 year supported stuff and next worry about the bandwith the updates would take, like the 1.7GB for the 2015/2016 LTSB updates containing multiple cab files....
Yes, I agree. It seems like an LCU version for Windows 10 of 4957 is also a bit large. It may be due to the idea of loading up feature updates and enabling them with an EP over and over again. I dunno. I can't keep track of what they are doing and why they are doing it. It can be frustrating to try and figure it out.
the problem is there are 3 checkpoint updates on the Dev channel now, you should install all 4 in total so nope, it wouldn't work this way windows11.0-kb5038575-x64_LCU_961.1.3.msu windows11.0-kb5038603-x64_LCU_1252.1.4.msu windows11.0-kb5041872-x64_LCU_1542.1.1.msu windows11.0-kb5043185-x64_LCU_1843.1.3.msu 1.3 Gb. for all 4 things, and there is no "true" cumulative 1542.1.1 update
That's it, to have the 26100.1742, I just integrated the KB5043080 (1742) from 26100.1 At the next patch Tuesday, I will just have to integrate the KB of this patch to 26100.1 Etc...
So your thinking is that installing only KB5043185 wouldn't be enough, prior to the last incremental update after KB5043185 on the Dev channel. Keep in mind that I was not referring to any Dev install or Dev channel updates. I was only referring to GA or RP channels (i.e. 26100.XXXX). To me, it doesn't make sense to require 1.3 Gb of LCUs, because it does not significantly reduce the bandwidth for downloading from MSFT update servers. It would only make sense to have the first install as a checkpoint, and then the last true LCU as a checkpoint, and then incremental updates after 26100.1742 as incremental updates. For example, 26100.1 was an initial checkpoint. Running cleanup on every LCU update before 26100.1742 left 26100.1 modules in a "staged" state in component store alongside the latest LCU modules. As soon as 26100.1742 was installed, it became the new checkpoint. Running cleanup after 26100.1742 removed the 26100.1 modules from component store, and left only 26100.1742 modules. Now with the 26100.1876 LCU update installed, it is not a checkpoint. If you run cleanup, you get 1742 modules "staged" and 1876 modules "installed" in component store. I'm on Windows 10 right now, so I can't run the dism command lines. But I bet if you are on Windows 11 26100.1876, you'll see a component store with 26100.1742 and 26100.1876 modules with the 1742 modules "staged" and the 1876 modules "installed", side by side. I'll run the command lines on a 26100 machine tomorrow, and see what happens. dism /online /cleanup-image /startcomponentcleanup dism /online /get-packages /format:table
thinking? lmao, open LCU MSU with 7-zip and check update.mum yourself and all other 3 LCUs as well in short: there will be a lot of checkpoint updates, expect to see ~5+ next year they are not going to release one big fat checkpoint update https://forums.mydigitallife.net/posts/1853030 btw you can't cleanup it without waiting 2 hours
KB5043185 is for the DEV channel (26120.1843), so it is not recommended to use it for build 26100 (mixed DEV and "GA")
anyone have a problem making the iso for 1876 from uup no matter how many times i tried it always got stuck at 72% when making it only 1 i had a problem with