this post was submitted on 06 Feb 2024
825 points (98.2% liked)
Technology
59312 readers
5006 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's a registry setting for telling Windows that the target feature release is a specific version (it should be 22H2) which also will stop it from trying to push win11 upgrades
If anybody is curious, here are the details on how to do that: https://www.pdq.com/blog/how-to-block-the-windows-11-upgrade/
If you want to take it a step further, write a Powershell script that checks that the registry entry is what you want it to be, and then changes it if it is not. Then create a scheduled task to run at login that runs the script. That way if/when Microsoft pushes an update that switches the registry entry back, the scheduled task will flip it back after installing updates/rebooting/logging in.
I am currently fighting this battle with New Outlook in Win 11 23H2. It's really annoying. I can get rid of it with registry entries, but when windows does updates it reverts the registry changes back. So scheduled task it is. It would be great if there was an Intune configuration profile to deal with this, but that would go against Microsoft's current methods of shoving new products down your throat.
But 11 wants sometjing from my computer that it doesnt have, so it cant "upgrade"...