I installed the latest cumulative update june , and requested a restart as usual, it staying at 0% for 10 mins now? Is this normal Therenalso doesnt seem to be any acitivity on the hdd Update/ against nwhatthe messege says i rebooted, so it rolled back, a 2nd update worked, took sometime though
@hceeler on some rare occasions the update process can hang at the very beginning. In my experience so far, it's ok to manually restart, you'll just start the update process from scratch. Still cwappy expewience.
RE: https://forums.mydigitallife.net/th...pc-24h2-retail-ge-release.88220/#post-1830860 I see that the 1742 LCU is listed here as an update which should be applied before the latest LCU And indeed in Enthousiast's W10MUI logs I've noticed the 1472 update being integrated even when using a 1742 iso Why is that?
Because MSFT said so, they made the checkpoint lcu mandatory when integrating/installing of updates. ps, by 1472 you probably meant 1742?
since when LCU became so freaking big, 3 and 4 gigs !!! this way downloading the iso is better than integrating updates
i thought sometime ago they said updates will get smaller in size!! for 23H2 it's different, maybe the AI takes lot of space
MSFT is changing all all the time, In 23H2 they don't put the appx stuff in the LCU, it was first in 24H2 IP updates releases and a month or 2 ago they started to put the appx in regular 24H2 updates, but Windows doesn't seem to use the included appx, yet.
If you click on lcu you have two kb 21600.1742 + latest lcu ( for every news update click on lcu and download only latest lcu kb ) And to update you need 26100.1742 as base ( kb ) for any lcu and after apply latest lcu kb
This has nothing to do with the question/remark how/why/when the 24H2 LCU's now are huge, which is explained.