this post was submitted on 02 May 2025
342 points (87.2% liked)
Technology
69658 readers
3238 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's extraordinary, even for Microsoft.
If you're on Win 11 Pro, up to 23H2, follow these steps to prevent 24H2:
win+R, type GPEDIT.MSC, press enter Locate "Computer Configuration\Administrative Templates\Windows Components\Windows Update\Manage updates offered from Windows Update\Select the target feature update version"
Now click the "Enabled" button, type "Windows 11" in the first prompt and "23H2" in the second prompt and click "Apply"
That will prevent 24H2 from being downloaded and installed. When they've fixed this and the "Recall" mess, you can go back and undo the setting.
You can still do the "bypassnro" thing, it's just a script that's been removed. All it did was write a registry entry and reboot. This is the registry key entry - you can still press shift-F10 at the same point and type this manually:
another method to try is this, instead of the registry entry:
start ms-cxh:localonly
but I haven't tried that one yet.
I love how Windows fix has terminal and GUI configurations mixed as an unholy concoction directly from the HQ.