Flamingo Raises $4.5M Seed Round

Skip to content

How to debloat Windows 11 without breaking it

Best Practices
Technology
IT Operations
"Fae" Grace Meadows"Fae" Grace Meadows
September 29, 2026
760 views
How to debloat Windows 11 without breaking it

How to debloat Windows 11 on company PCs: Microsoft's removal policy for Enterprise and Education 24H2 and later, cleaning the image without breaking Sysprep, what Win11Debloat, WinUtil and Tiny11 change as of November 2026, and what not to remove.


Updated: November 2026

To debloat Windows 11 on work PCs, use Microsoft's built-in removal policy on Enterprise and Education (version 24H2 and later) or one reviewed PowerShell script on Pro, and clean the image instead of every desktop. Win11Debloat, Chris Titus Tech's WinUtil and Tiny11 go further, and their stronger settings can switch off Windows Update, turn off Offline Files or remove apps your users still need. Below are both routes, what each tool changes as of November 2026, and the keep list that saves you the tickets.

What bloat is on a business PC

Bloat on a work machine comes in three piles. OEM extras, like the Dell, HP and Lenovo support and "optimizer" utilities. Consumer Store apps, like Solitaire, the Xbox apps, Clipchamp and News. And the nudges: Start menu suggestions, tips and ads in Settings.

Here's the part the YouTube thumbnails skip: removing it barely changes how fast the PC runs. When PCMag's Chris Hoffman tested four debloat tools in April 2026, a fresh Windows 11 25H2 install in a virtual machine used 1.9 to 2.1 GB of RAM on boot, and the tools saved 100 to 200 MB at most.

So the case for debloating a business PC comes down to fewer apps to patch, fewer "what's this?" tickets, less attack surface, and a Start menu your users can find things in. That changes how you should do it.

Microsoft's supported way to debloat Windows 11

Microsoft now ships a policy that does the job it used to take a script for. It's called Remove Default Microsoft Store apps (KB5065996, first published in August 2025), and it became available to Enterprise and Education devices in October 2025.

In Group Policy it lives at Computer Configuration > Administrative Templates > Windows Components > App Package Deployment. In Intune it's a settings catalog policy under the same path, backed by the ApplicationManagement/RemoveDefaultMicrosoftStorePackages CSP. If the setting hasn't reached your tenant's catalog yet, Microsoft's workaround is a custom OMA-URI profile. You tick the apps you don't want from a fixed list of 25, including Copilot, Clipchamp, Solitaire, the Xbox apps, News and Weather, and since April 2026 you can add any other MSIX or APPX app by its package family name. Apps come off at the device level, and each successful removal logs Event ID 762.

Four rules matter. It only works on Windows 11 Enterprise and Education, version 24H2 or later, so Pro is out, and since October 2026 it covers multi-session hosts too. It's off by default, and it removes apps at setup or at the next sign-in, so existing users keep them until they sign out and back in. Removing an app also deletes its local data, and per Microsoft's documentation, unticking it later only unblocks it, so you reinstall it from the Store or redeploy it yourself. And set it from Intune or Group Policy, never both, because whichever arrives last wins.

If your fleet runs Pro, you're still in script territory, which is where the next section starts.

Clean the image, not every desktop

Windows tracks built-in apps in two places. Provisioned apps sit in the image and install for every new user at first sign-in. Installed apps belong to a profile that already exists. Removing one doesn't remove the other, and that's where scripted debloats go wrong.

Remove-AppxProvisionedPackage takes an app out of the image, so new users never get it. Profiles that already have it keep it. To clear those too, pair it with Remove-AppxPackage -AllUsers for the same package.

Get the pairing wrong on a reference machine and Sysprep stops you. Microsoft documents the error as "A fatal error occurred while trying to sysprep the machine", with 0x80073cf2 in the log. The cause: an app was deprovisioned from the image but is still installed for a user. The fix is to remove it for that user as well, then run Sysprep again.

This r/sysadmin thread asks how other Windows shops debloat workstations. The top answer scripts the AppX removals, then adds that if you can't live with any bloat at all, Enterprise licensing is the cleaner route.

Are Win11Debloat, WinUtil and Tiny11 safe for work PCs?

The tools that dominate this search are community projects: Chris Titus Tech's Windows Utility (WinUtil), Raphire's Win11Debloat, and Tiny11 Builder for stripped-down ISOs. All three shipped releases in October 2026, and WinUtil and Win11Debloat are MIT-licensed. On a personal PC they're a reasonable weekend project. On 200 company laptops they're code from someone you've never met, running with admin rights.

PCMag's April test showed what that looks like: Tiny11 Core disabled Windows Update, Win11Debloat's default settings switched off Fast Startup (true when PCMag tested, and changed since), and WinUtil's standard selection set a batch of services to manual start. Each one is the author's opinion about how Windows should behave, applied to your fleet. The projects have moved since, so here's what each one does as of November 2026, checked against their GitHub repositories:

  • WinUtil (release 26.10.28). All three of its presets include a "Services - Set to Manual" tweak that disables Offline Files, Internet Connection Sharing and the telemetry service, and sets two more services to manual. On PCs that use Offline Files, that switches the feature off. The Advanced preset also removes OneDrive. Its recommended update mode delays feature updates by 365 days and quality updates by 4 through Windows Update policy, which is the job your Intune or Group Policy update rings already do, and its Disable Updates mode stops Windows Update altogether.
  • Win11Debloat (release 2026.10.30). Its defaults create a restore point, then turn off telemetry, tips and ads, Bing web search, Copilot, Recall, Click to Do and widgets, among other settings. Fast Startup came out of the defaults on 19 April 2026, six days after PCMag's test was published. Optional settings switch off early updates, block driver updates through Windows Update, turn off Delivery Optimization and disable BitLocker's automatic device encryption, so leave those boxes clear on managed PCs and let your management tool own them.
  • Tiny11 Builder (0.2.0). The standard Tiny11 image keeps Windows Update, Defender and recovery. Tiny11 Core removes update and recovery support and disables Defender, and the project says Core "cannot be updated or serviced" and is meant for disposable test VMs. Keep it off any PC that holds company data.

Other changes don't stick. Microsoft's "Diagnostic data off" setting only works on Enterprise, Education and Server editions (LTSC included), so on Home and Pro, Windows keeps sending required diagnostic data whatever a script sets. New Windows versions also bring apps of their own, and Microsoft's removal list now includes Copilot and the new Outlook, which an older script won't know about. The removal policy runs again at the first sign-in after an OS upgrade. A one-off script doesn't.

If you do use a community script, treat it like any other change. Read it, pin the version you tested, and run that copy from your own repository. Both projects' quick-start commands download and run the newest code from the author's site, so a release you never tested lands on the next machine.

Britec09 tested the same promises on camera in September 2026, with frame rates and memory on one side and the things that broke on the other.

What not to remove

Every debloat list needs a keep list next to it. These are the ones that come back as tickets:

  • Microsoft Store and App Installer. winget depends on App Installer, and line-of-business apps that update through the Store need it too.
  • Edge WebView2 Runtime. Teams, the new Outlook and third-party apps built on WebView2 render inside it.
  • Windows Security. Pulling it apart leaves Defender half configured.
  • Photos, Notepad, Calculator, Snipping Tool, Terminal. Users open these daily. Removing them saves nothing and costs you tickets.
  • Quick Assist. Keep it if your help desk uses it for remote support.
  • OneDrive. If you use Known Folder Move, removing it stops Desktop and Documents syncing. WinUtil's Advanced preset removes it.
  • Offline Files. Keep the service running on PCs that use it. WinUtil's presets disable it.
  • Xbox Identity Provider. Xbox sign-in and Game Pass for PC depend on it, and Microsoft's removal policy pre-selects it, so untick it on devices that need either.

The safest workflow is boring on purpose. Remove from a pilot group of ten machines, wait a week, read the tickets, then widen the ring.

In this r/sysadmin thread, one admin who had to clean Dell bloatware and extra Office language packs off 100 computers wrote their own script after finding nothing that worked. The comments are a good list of what else people strip, and what they regretted.

Run it across the fleet

Pick the route by edition. On Enterprise or Education, version 24H2 or later, use the policy through Intune or Group Policy, and let Windows do the removal. On Pro, keep one reviewed PowerShell script in your own repository, pair the provisioned and installed removals, and log what it touched. Check the version first: Windows 11 24H2 Home and Pro are past end of updates, so move those machines to 25H2 or 26H2 before you clean them.

Then roll it out like a patch. A pilot ring first, the rest of the fleet a week later, and a re-check after every feature update, because that's when new inbox apps arrive and removed ones can return. For OEM junk, the cleanest fix is upstream: order devices with a clean image from the vendor, or reimage them on arrival.

Whatever runs the script needs to show you what happened on each machine. OpenFrame, our open, AI-native infrastructure for IT and security, runs that script on a few devices before the rest, logs every action, and holds anything your rules mark "ask first" until a technician approves it. Our PowerShell commands guide covers the Get-AppxPackage checks worth running before and after.

How to debloat Windows 11 safely

A safely debloated business PC has nothing on it that nobody asked for, and nothing missing that users need. Use the policy where your licensing allows it, clean the image rather than every desktop, keep a keep list, and leave Windows Update, Offline Files and BitLocker to your management tool.

If Copilot is on your removal list, see how to uninstall Copilot.

For the patching side of keeping a clean fleet clean, read our guide on stopping Windows Update without losing security fixes.

"Fae" Grace Meadows

"Fae" Grace Meadows

Lead AI Fairy

Some things defy easy explanation: magic dust, the northern lights… and Flamingo’s AI Angels. Think Charlie’s Angels, reimagined with automation brains and serious RMM (Remote Monitoring & Management) chops. Weird? A little. Effective? Absolutely. That’s the job.

Related Content

Frequently Asked Questions

/blog/how-to-debloat-windows-11

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions