if that’s true, then we can go for some frankenbuilds (to get updates) i wonder if this theory could be the same for windows 7
Updates will be published as usual frankenbuilds is needed only if they decided to modify .mum files (like the situation with Windows 8.0) if they go with ESU licenses-keyless route, then ESU Bypass project will be enough
I used jDownloader, which handles such situations fine. Other download managers will do the trick, too.
I can say, that I tried "Save Link As", tried IDM, tried WGET, all three times download success. Next time, will first leave file for few days on web3.storage, maybe then will be better.
@adric Apparently, yes although the MU catalog metadata shows that 2022-11 Rollup replace 2022-10 Rollup & 2022-07 Rollup
Secure Boot updates KB4535680 and KB3172729 (with SSU KB3173424) are expired along with most setup dynamic updates Spoiler KB2891213 KB2892082 KB2898464 KB2936897 KB2958265 KB2953600 KB3034394 KB3048100
But that caused oldest update KB2920189 (with SSU KB2975061) to show up in WU just hide it p.s. the update is preinstalled with latest ISO/ESD (Devember 2015)
Yes but they did not add supersedence metadata to KB5012170, hence KB4535680 or KB3172729 was still requsted by WU
Although 2022-12 Monthly Rollup supersede them, they didn't add replacement metdata for updates 3060716, 3146723, 3175024 (all related to basesrv/csrsrv components) they also didn't fix the metadata for 2022-10 KB5018549 .NET Rollup (now 3.5 KB5016268 also still needed with 4.8 KB5018519)