46
Disabling Windows 11 Recall, AI "Click to Do", and Telemetry via Group Policy - 2026 Manual Guide (the.unknown-universe.co.uk)
submitted 3 months ago by to c/technology@lemmy.ml
10 comments fedilink hide all child comments
 

As a Linux user forced into a temporary truce with Windows for gaming handheld compatibility, I refuse to run the OS in its "out of the box" state. I’ve put together a manual optimisation guide that skips the "one-click" de-bloat scripts and focuses on permanent Group Policy (gpedit) and system-level tweaks to make the OS semi-tolerable.

The Guide Covers:

Killing AI Spyware: Disabling the "Recall" background service, snapshot recording, and "Click to Do" screen scraping.

Telemetry Lockdown: Redirecting "Allow Diagnostic Data" to the Security level (0).

Start Menu Surgery: Decoupling search from Bing to keep local file searches actually local.

Performance recovery: Disabling Virtualization-Based Security (VBS) and background hypervisors for bare-metal gaming speed.

Edge/Widget Removal: Stopping background "loitering" and accidental UI stutters.

This is a reproducible, manual workflow for those who want a clean(er) environment without relying on third-party scripts.

all 10 comments

sorted by: hot top controversial new old
[–] 19 points 3 months ago (3 children)

Man, that's a whole lot of homework just to access a Microsoft account. In addition, Windows has a nasty habit of rolling back changes every time there's a major update (like upgrading from build 24H2 to 25H2), so the tweaks listed might not even stick.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] [S] 10 points 3 months ago (2 children)

    It is a fair bit of homework but for those of us who use Linux on a daily basis, we'd rather do the legwork once to have a private, predictable system than deal with the out-of-the-box bloat.

    Regarding updates: that’s exactly why I focused on Group Policy tweaks rather than simple registry hacks or UI toggles. Policies are designed for enterprise environments where IT managers would be furious if an update reset their security configurations, so they tend to survive major build updates much better than standard settings, it's not foolproof but it is the best way to stay ahead!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] 14 points 3 months ago (3 children)

    Just a reminder, more likely than not Linux can do everything you do on Windows. Statistically your weird internal corpo program that was made bespoke over a decade several decades ago can just be run on a locked down VM. Everything else needs WINE, at most.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 1 point 3 months ago (1 child)

    Statistically your weird internal corpo program that was made bespoke over a decade several decades ago .....

    Won't work at all because it lives on a shared drive that needs your windows login and your PC to be joined to the domain to reach it, and IT just said "lol no" to your request to join your home made windows VM to the domain.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 months ago

    IT said no

    Affected exactly zero people ever, just ask a manager higher than the service desk manager. Then suddenly whomever said no will be doing the work with a fake smile of their face.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 10 points 3 months ago

    My guide is even simpler - don't install windows in first place. If you have one, format the disk.

  • permalink
  • fedilink
  • source
    •
    [–] 6 points 3 months ago

    Step 1: switch to Linux

  • permalink
  • fedilink
  • source
    •