Friday, May 19th 2023
Microsoft Will Force Windows 10 22H2 Upgrades Next Month
Microsoft is determined to get the entirety of its Windows 10 userbase onto the final version - 22H2 - by early summer. Older iterations including 21H2 (issued in November of 2021), will not receive official support beyond the date: June 13 2023. The announcement crept out quietly last week, via the company's Learn Documentation center: "Home, Pro, Pro Education, and Pro for Workstations editions of Windows 10, version 21H2 will reach end of servicing. The upcoming June 2023 security update, to be released on June 13, 2023, will be the last update available for these versions. After this date, devices running these version will no longer receive monthly security and preview updates containing protections from the latest security threats."
The reminder does not give specific details about rollout timings, but news outlets reckon that OS-focused enforcements will begin in early June: "To help keep you protected and productive, Windows Update will automatically initiate a feature update for Windows 10 consumer devices and non-managed business devices that are at, or within several months of, reaching end of servicing. This keeps your device supported and receiving monthly updates that are critical to security and ecosystem health. For these devices, you will be able to choose a convenient time for your device to restart and complete the update." Microsoft provides further advice and recommends that users update (manually) to version 2H22 at the earliest opportunity, or take the larger step of transferring to Windows 11. Last month TPU reported on a similar official advisory blog entry, where the author/product manager (in effect) proposed "that current Windows 10 users move to 11 as soon as possible, in order to enjoy a continued stream of feature updates."
Source:
Windows Central
The reminder does not give specific details about rollout timings, but news outlets reckon that OS-focused enforcements will begin in early June: "To help keep you protected and productive, Windows Update will automatically initiate a feature update for Windows 10 consumer devices and non-managed business devices that are at, or within several months of, reaching end of servicing. This keeps your device supported and receiving monthly updates that are critical to security and ecosystem health. For these devices, you will be able to choose a convenient time for your device to restart and complete the update." Microsoft provides further advice and recommends that users update (manually) to version 2H22 at the earliest opportunity, or take the larger step of transferring to Windows 11. Last month TPU reported on a similar official advisory blog entry, where the author/product manager (in effect) proposed "that current Windows 10 users move to 11 as soon as possible, in order to enjoy a continued stream of feature updates."
53 Comments on Microsoft Will Force Windows 10 22H2 Upgrades Next Month
I lost count how many times i said i didn't want W11.
atlasos.net/downloads/w10_22h2
but this would be an excellent time to start considering AtlasOS. It's basicly W10 but stripped with all it's nonsense and most important telemetry.
Intel's CSME checking utility, failed on that laptop and then I banhammered that laptop.
Windows 12 is expected in 2024 which is quite rapid of a release model, my guess would be maybe 2-3 years support of 11 after that date so 2026-2027 end date. That would indeed be shorter than ME potentially. o_O
An indication of the direction of lifespans is looking at LTSC.
Windows 10 1809 LTSC has a later EOL than 21H2 LTSC. I think Office had similar issues when they made adjustments.
OTOH, if 11 continues at least near a decade with only security fixes, then that's fine with me. ;) Otherwise, I could be on Linux for all systems in my room!
May I suggest also checking out the Slimdown10 script by wkeller. His previous Integrate7 script was great for creating an updated Windows 7 ISO. I have used the Slimdown10 script and created a stripped Windows 10 22H2 ISO which I installed and have used for a few weeks, and am quite happy with it. It's lighter then even my attempts using ntlite or the msmg toolkit on various Windows 10 versions over the years (I started modding Windows back in the days of 98lite). It's also probably a lot safer as well. With some additional tweaking and service disabling I'm down to about 70 processes / 1GB memory used after Windows finishes loading to the desktop and stabilizing. And my old system runs fantastic, fastest I've ever seen it go. Keep in mind I'm old school, I don't care about 90% of the stuff that 10 comes with. I want a light OS that gets out of my way, as my system is used for browsing and gaming and that's it. If you are looking for something that just removes the bloat without any weird stuff going on, check it out. This basically turns Windows 10 into something like Windows 7. You will need an account to see the first post with all the info on the script, what is needed, and how to use it.
forums.mydigitallife.net/threads/slimdown10-%E2%80%93-turn-windows-10-22h2-into-classic-legacy-windows.86552/
I do run my internet through a thin client running Adguard Home, and I have practically all Microsoft internet addresses blocked. With this Slimdown10 install Windows is very quiet, looking at my outbound connection log, and my event viewer doesn't have much in the way of continuous errors that can be seen with many lightweight Windows versions. I get a complaint about Software Protection service not running (which is fine by me) and a few complaints about Windows components not being able to access Microsoft servers, and that's about it.
Some didn't get patched and that was a critical mistake. (no patch in latest UEFI-BIOS available)
With startisback it was quite usable, but I think I did stay on it too long. In the end was forced to upgrade when I got my RTX 3080.
I planned to continue using startisback on Win10, but ended up liking the Win10 menu enough to keep using it (primarily the pinning).
admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.ServiceControlManager::SvchostProcessMitigationEnable