Paul Thurrott just dropped a bombshell for Windows 11 users who want out from under Microsoft’s watchful eye. His May 18, 2026 “Switcher 2026” walkthrough isn’t another tired registry hack—it’s a methodical dissection of how to slim down the OS to a core functional state without Microsoft services constantly phoning home. The guide arrives as Windows 11 becomes an increasingly dense thicket of ads, telemetry, and cloud dependencies, leaving privacy-conscious users and IT pros scrambling for a clean baseline.

The problem isn’t new, but its urgency is. Every cumulative update stealthily re-enables Edge, restores OneDrive prompts, and resets default apps. Thurrott’s walkthrough tackles this from a fresh angle: start with a local account, strip the bloat immediately after install, and lock down policies before a single byte of data leaks. The result is a Windows 11 PC that behaves more like a traditional tool and less like a subscription funnel. This article breaks down the key phases of that process, interweaving Thurrott’s recommendations with practical context for users who might not have a dedicated test bench.

Why Minimize Microsoft’s Footprint?

Windows 11 ships with at least 20 preinstalled apps that no one asked for. TikTok, Instagram, Spotify, and various trialware occupy the Start menu while delivering zero productivity. Behind the scenes, telemetry services gather usage data, typing patterns, and app compatibility telemetry—all of which feed Microsoft’s backend analytics. For enterprises, this raises compliance flags; for individuals, it’s a slow erosion of control over their own hardware.

Thurrott frames the effort not as paranoia but as self-defense. “You paid for the license, not for a perpetual advertising platform,” he writes. The goal is a machine that boots without signing into a Microsoft account, runs productivity software without nag screens, and respects local privacy preferences across reboots. Achieving that demands more than flipping a few toggles in Settings—it requires deliberate, sequenced steps.

Phase 1: Preparation and Clean Installation

Before touching any settings, back up your files. Thurrott emphasizes a full image backup using a tool like Macrium Reflect or Veeam Agent, because the debloating process can occasionally break side‑by‑side dependencies. If you’re starting fresh, create a Windows 11 installation USB using the Media Creation Tool, but download it from a clean machine to avoid injecting existing bloat.

During setup, the crucial moment arrives at the network connection screen. Thurrott insists on the bypass: press Shift+F10 to open Command Prompt, type OOBE\\BYPASSNRO, and reboot. This unlocks the “I don’t have internet” option, which in turn permits creating a local account. Without this step, Windows 11 Home forces a Microsoft account, linking your device ID to the cloud from day one. For Pro or Education editions, you can select “Domain join instead,” but the OOBE bypass guarantees no accidental linkage.

Once on the desktop, pause Windows Update immediately. Open Settings > Windows Update and hit “Pause for 1 week.” This prevents automatic downloads from interfering while you strip the system. Thurrott then recommends disabling driver updates via Windows Update by setting a Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update > Do not include drivers with Windows Updates to Enabled). This stops Windows from fetching manufacturer‑branded bloat drivers that bundle extra software.

Phase 2: Slashing the App Bloat

Windows 11 comes with two layers of unwanted software: provisioned Store apps and system‑packaged components. The walkthrough tackles both. For the obvious culprits, right‑click uninstall works for apps like Spotify, but many require PowerShell. Thurrott provides a script that removes all non‑essential store apps while keeping the Microsoft Store itself (for those who need it for paid apps or updates). The script iterates through a safe list of packages to keep—such as the Store, Photos, and Calculator—and purges everything else.

$appXPackages = @(
    \"Microsoft.BingWeather\",
    \"Microsoft.BingNews\",
    \"Microsoft.GamingApp\",
    \"Microsoft.GetHelp\",
    \"Microsoft.Getstarted\",
    \"Microsoft.MicrosoftOfficeHub\",
    \"Microsoft.MicrosoftSolitaireCollection\",
    \"Microsoft.MixedReality.Portal\",
    \"Microsoft.Office.OneNote\",
    \"Microsoft.People\",
    \"Microsoft.ScreenSketch\",
    \"Microsoft.SkypeApp\",
    \"Microsoft.StorePurchaseApp\",
    \"Microsoft.Wallet\",
    \"Microsoft.WebMediaExtensions\",
    \"Microsoft.WebpImageExtension\",
    \"Microsoft.Windows.Photos\",
    \"Microsoft.WindowsAlarms\",
    \"Microsoft.WindowsCalculator\",
    \"Microsoft.WindowsCamera\",
    \"Microsoft.WindowsCommunicationsApps\",
    \"Microsoft.WindowsFeedbackHub\",
    \"Microsoft.WindowsMaps\",
    \"Microsoft.WindowsSoundRecorder\",
    \"Microsoft.Xbox.TCUI\",
    \"Microsoft.XboxApp\",
    \"Microsoft.XboxGameCallableUI\",
    \"Microsoft.XboxGamingOverlay\",
    \"Microsoft.XboxIdentityProvider\",
    \"Microsoft.XboxSpeechToTextOverlay\",
    \"Microsoft.YourPhone\",
    \"Microsoft.ZuneMusic\",
    \"Microsoft.ZuneVideo\"
)

A more aggressive cleanup removes system‑level packages like Cortana, Quick Assist, and Microsoft Teams (personal) using DISM. Thurrott’s walkthrough includes remove-appxpackage for current user and remove-appxprovisionedpackage for new accounts, ensuring no bloat resurrects when another user logs in.

He also tackles the hidden Windows Copilot integration. Even if you never invoke it, the Copilot runtime consumes memory and phones home to Bing. Disabling it requires a Group Policy (User Configuration > Administrative Templates > Windows Components > Windows Copilot > Turn off Windows Copilot) or a registry key under HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsCopilot.

Phase 3: Privacy Settings and Telemetry Lockdown

With the apps gone, Thurrott pivots to the more insidious telemetry pipeline. He doesn’t trust the “Diagnostic data” toggle in Settings because Microsoft has re‑labeled “Optional diagnostic data” to “Send optional diagnostic data” without actually changing what gets collected. Instead, he zeroes in on Group Policy.

Navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds. Set Allow Diagnostic Data to Enabled and choose Diagnostic data off (Enterprise, Education, and Windows Server only). Windows 11 Pro misses this option, but Thurrott notes a workaround: setting Configure Authenticated Proxy usage for the Connected User Experience and Telemetry Service to Enabled and then adding a dummy proxy can block telemetry at the network level, though it may throttle updates.

The walkthrough goes further into the App Privacy section of Settings. Thurrott disables everything under “Let apps access” for camera, microphone, notifications, account info, and background apps—except for a short allowlist of critical tools. This prevents pre‑installed Store apps from silently activating permissions. He also recommends turning off “Inking & Typing Personalization,” “Speech Recognition,” and “Tailored Experiences” because they feed cloud‑based language models.

One often‑missed step: Disable Delivery Optimization. By default, Windows uses peer‑to‑peer networking to share updates with other PCs on your local network and the internet. Thurrott turns this off both for downloading and uploading, citing bandwidth and privacy reasons. The setting lives under Settings > Windows Update > Advanced options > Delivery Optimization; disable “Allow downloads from other PCs.”

Phase 4: Browser and Search Decoupling

Microsoft Edge is notoriously difficult to dislodge. Thurrott doesn’t try to uninstall it—modern Windows versions embed EdgeWebView and the Edge updater so deeply that removal can destabilize the OS. Instead, he neutralizes it. Set a different default browser (e.g., Firefox, Brave) through Settings > Apps > Default apps, and then use Group Policy to disable Edge’s first‑run experience, startup boost, and background running.

Group Policy path: Computer Configuration > Administrative Templates > Microsoft Edge. Enable “Prevent First Run web page from opening on Microsoft Edge,” “Disable background mode when Microsoft Edge closes,” and “Control communication with Microsoft Dynamics.” These cut the browser’s ties to Microsoft services without breaking WebView‑based components like Windows widgets.

For local search, Thurrott’s walkthrough addresses Windows Search indexing. By default, Windows 11 indexes your entire user folder and sends queries to Bing. Turn off “Search online and include web results” via Group Policy or Registry under HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\Windows Search. Then, restrict indexing to just the Start menu and document folders—not your entire drive—to limit what Windows catalogs locally.

Phase 5: Account and Sign‑In Isolation

With a local account already in place, Thurrott reinforces the separation by disabling Windows Hello and passwordless sign‑in. Those features, while convenient, tie biometric data to your Microsoft account if you ever accidentally link it. Under Settings > Accounts > Sign‑in options, turn off Windows Hello Face, Fingerprint, and PIN. Stick to a strong, complex password stored in a local password manager.

He also recommends disabling “Allow my Microsoft account to be used for sign‑in to apps” under Settings > Accounts > Email & accounts. This prevents apps like Mail or OneDrive from silently authenticating with a linked Microsoft account, which could re‑establish cloud ties.

Phase 6: Maintenance and Update Strategy

A stripped‑down Windows 11 needs a different update cadence. Thurrott suggests setting Windows Update to “Notify to download” via Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experience > Configure Automatic Updates set to 2 – Notify for download and auto install). This gives you control over when patches arrive, avoiding out‑of‑band updates that might reintroduce bloat.

He further advises using the Windows Update MiniTool (WUMT) or the open‑source WAU Manager to hide unwanted driver and feature updates. For cumulative patches, always read the release notes—Thurrott links to the official Windows 11 update history page—to check for known issues that might conflict with your debloated configuration.

Finally, the walkthrough recommends creating a baseline system image after all optimizations. If a future update corrupts your setup, you can revert to this clean state in minutes rather than repeating the hours‑long process.

Real‑World Caveats from the Community

Users on the WindowsForums thread accompanying Thurrott’s original piece highlight several friction points. Several report that the OOBE bypass no longer works on the latest Insider builds—Microsoft is constantly patching these loopholes. Others note that disabling telemetry can break Xbox Game Bar and certain modern games that require ongoing diagnostic data for “performance optimization.” A workaround is to re‑enable telemetry temporarily for game sessions, then disable it again.

There’s also the elephant in the room: Windows 11 Home edition. Thurrott’s walkthrough relies heavily on Group Policy, which is absent from Home. Community solutions include using third‑party tools like O&O ShutUp10++ or WPD, but these can introduce their own instability. One forum member posted a script that simulates Group Policy settings via Registry keys—a hacky but effective alternative.

Perhaps the most common gripe: after a major feature update (say, 24H2 to 25H2), many of these customizations reset. Thurrott acknowledges this and suggests pinning a checklist next to your monitor for post‑update reapplication. “Think of it as seasonal house cleaning,” he quips. “Twice a year, you haul out the garbage Windows brought back in.”

What This Walkthrough Means for Windows Users

Thurrott’s 2026 walkthrough is more than a set of instructions—it’s a statement. It exposes how far Windows has drifted from its roots as a user‑centric operating system. Every step detailed here challenges Microsoft’s assumption that your PC is a conduit for its services. The fact that a veteran tech journalist must publish a 5,000‑word guide just to achieve a baseline of privacy signals a deep‑seated design philosophy clash.

For power users and IT administrators, this process is now a rite of passage. It’s likely to become part of the standard imaging sequence for organizations that can’t switch to Linux but need to lock down Windows for compliance. For everyday users, it’s a gateway to understanding just how much of their digital life they’ve ceded by clicking “Accept.”

Looking ahead, the tools may change. Microsoft will continue hardening OOBE, burying settings deeper, and intertwining AI services into every mouse click. But the principles Thurrott outlines—local accounts, aggressive app removal, telemetry lockdown, and controlled updates—will remain the foundation for anyone who wants a Windows PC that works for them, not the other way around.