Well MS has never maintained a decision in history, they keep changing idea on decisions taken as definitive just a year or two earlier. Remember "W10 is the last major version of windows"? BTW they used to have SAC channel and LTSC channel as separate channels, possibly they switch from semi annual channel to annual channel, but still way different from 5/10 years cycles.
no but u can add the big packages from uup all files and make gui almost almost cos i couldnt make settings to work
It would probably be more fitting to keep separated from LTSC/VNEXT. Hoping there's a new build of slightly more interest coming here soon than those to be honest.
It would be pretty simple to have one thread for Server 11 and one for Server 23Hx just like we had separate threads For Server 2019 and Server 1809 (and so on). But seem that obfuscating what's discussed here was a priority since the beginning.
I've actually done this on a few of the variants (Validation OS etc) from your advice in the past, and keep the .vhd's ready to run from boot menu in case anything goes wrong - a nice small emergency option that doesn't take up much space.
For that purpose a 32bit OS put on a LZX compressed VHDX is by far the best option. The first one is a virgin, untouched .0 build The second one is a fully updated OS, with a bunch of basic SW installed (including VMware, VBox, partitioning sw, and alike). Less footprint and no constraints (except the lack of Hyper-V)
253xx became Azure Stack HCI 23H2, Server core build 25398. These server builds seem to have small window every 2 weeks where they are released or not, considering 25379 came out June 2 would be this week is the potential window for a release. So I think there is a good chance we see a 259xx Server build released tomorrow or Thursday.
Is anyone able to install KB5028172? I have four fresh Azure Stack HCI 23H2 installations. All of them fail when trying to install the update. EDIT: No issues installing on Windows Server Core 23H2.