Yeah, it's odd how silent they are, and I also find this new branch/build number odd at such a late stage of 22621's development. I guess they have their reasons. Hopefully we will find out what they are.
If i install 22H2 ISO (clean install) outside of Windows Insider program, will it download cumulative updates via Windows Update?
I don't really see how it can be a 'dead end' now it's out there, unless they can release another EP that changes the version back to 22621. Seems to me they're much more likely to bump everyone to 22621 eventually.
Had a small driver package update this morning, logitech usb and an updated driver package from CU .290, like same build number but installed a package This was updated or reinstalled yesterday ...Online Service Experience Pack — Windows.Settings.Account — version 2.1.223.0 I dont know if its newer or same build. I didnt bother blacking out email because it passwordless and you need my sim card or my fingerprint
Oh i dont open emails on that account, have a different one for emails, bring on the spam lol Im also hoping that traffic that comes through this forum are normal everyday human beings
start 22621 > release an EP to bump it to 22622 > now skipping all entirely? Or like now with Server LTSC IP builds, run tests for 3 years and then release it?
I ment the "The new Windows roadmap" article Zac says new version every three years, and he counts from v21H2, while v22H2 is 1-year apart, and v24H2 will be 2-years apart they should have never changed that 3-years model
Maybe it's 3 years since 22H2 and he got it wrong? They are already testing the "feature updates" within the same build now by using enablement packages and virtual build jumps with 22621->22622.
As the build switch is virtual, it could even flip back to 22621 for everyone, without any consequences.