Version 07.11.2026 of the open-source Win11Debloat PowerShell script is now available, giving Windows users a safer way to strip out unwanted apps and a new option to block manufacturer driver software. The update introduces a -WhatIf simulation mode so you can see exactly which apps, services, and settings the script will touch before any changes are made, and a -BlockDriverApps switch that stops Windows from automatically installing printer drivers, audio suites, and other companion packages when new devices are plugged in.
The release, posted to GitHub on November 7, 2026, keeps the tool’s core promise: a single, community‑audited script that removes preinstalled bloat, dials back telemetry, and disables several Microsoft AI features—all without breaking the operating system.
What’s new in Win11Debloat 07.11.2026
The headline feature is safe experimentation. PowerShell’s built-in -WhatIf parameter has been part of the language for years, but this release is the first to wire that support deeply into every removal and configuration module inside Win11Debloat. Instead of parsing a help dump, you can pipe the script’s output into a readable preflight report.
The second major addition is -BlockDriverApps. When the flag is set, the script adds registry keys that prevent Windows Update from fetching manufacturer‑provided driver add‑ons. Those add‑ons are often harmless, but they can also include nag screens, trialware, or background services that users never asked for. By default, Win11Debloat targets common offenders: Realtek audio control panels, Intel graphics assistants, printer ink‑level monitors, and OEM‑specific updaters.
Several smaller improvements round out the release:
- Updated app lists. The script now recognizes and can remove newer versions of Clipchamp, Dev Home, Microsoft Teams (personal), and the Windows Backup utility.
- Selective AI opt‑out. A new -DisableAIFeatures switch lets you individually suppress Copilot icons, Windows Recall snapshots, and the system‑wide “ask Copilot” toolbar, without disabling other components.
- Log granularity. Each run now generates a detailed time‑stamped log in %TEMP%\Win11Debloat\, distinguishing simulated and real actions.
The WhatIf preview: try before you commit
Microsoft’s -WhatIf parameter is available on any PowerShell function that supports ShouldProcess. Win11Debloat’s developer, who goes by the handle Raphire, restructured the script’s internal functions so that every privacy tweak, app removal, and registry edit is wrapped in a “ShouldProcess” block. When you pass -WhatIf, the script writes out the operation it would perform—for example, What if: Removing package Microsoft.BingWeather—without actually touching your system.
The preview output is color‑coded in recent terminal versions: green for removable apps, yellow for config changes, and red for services that will be stopped. You can redirect it to a text file with a simple Out-File command, making it easy to share the report with colleagues or review it before a scheduled task.
For enterprise environments, this is a game‑changer. A sysadmin can run Win11Debloat.ps1 -WhatIf on a reference machine, vet the proposed changes, and then deploy the exact same parameter set across a fleet. Because the preview output is machine‑readable, it can be parsed in compliance audits to confirm that no business‑critical telemetry was mistakenly targeted.
Blocking unwanted driver applications
Windows’ plug‑and‑play behavior silently installs driver packages that often come bundled with branded software. When you connect an HP printer, for instance, you might get driver‑installation packages that also include the HP Smart utility. That utility can be useful for some, but for others it merely consumes disk space and pops up registration reminders.
-BlockDriverApps works by adding exclusion policies to the Device Installation Restriction group‑policy keys. Specifically, it creates a set of device‑setup‑class GUIDs under HKLM:\SOFTWARE\Policies\Microsoft\Windows\DeviceInstall\Restrictions\DenyDeviceClasses and DenyDeviceIDs. Admins can later adjust the block list by editing a plain‑text file that the script reads on each invocation.
This approach is reversible: running the same command with the -UnblockDriverApps switch deletes the entries. And because the blocks are applied via Group Policy, they survive Windows feature updates.
Other changes and improvements
While the -WhatIf and driver‑block features grab the spotlight, the 07.11.2026 release also fine‑tunes existing behavior:
| Area | What changed |
|---|---|
| Cortana removal | Now also cleans up leftover scheduled tasks that could recreate the app after a cumulative update. |
| OneDrive | Two new sub‑flags: -UninstallOneDrive and -PreventOneDriveReinstall. The second adds a block to the Windows Registry so feature updates don’t bring OneDrive back. |
| Suggested content | The “Windows tips”, “lock screen fun facts”, and “finish setting up your device” nudges are all silenced with a single new switch, -DisableNags. |
| Performance | The script parallelizes package removals where possible, trimming execution time by roughly 30 % on a clean install. |
Who benefits most from this update
Home users. If you’ve bought a new laptop loaded with OEM shovelware, you can run Win11Debloat with -WhatIf first, confirm the list looks sane, and then let it do the heavy lifting. The script requests elevation automatically, so the experience is little more than a right‑click and “Run with PowerShell”.
Power users. The ability to block driver‑app bundling is a long‑standing request from r/Windows10 and the ElevenForum. Many advanced users prefer Microsoft’s built‑in class drivers and use third‑party tools like NVCleanstall for graphics. -BlockDriverApps closes the gap.
IT admins. The structured logging and WhatIf support make Win11Debloat easier to integrate into MDT task sequences or Intune remediation scripts. Because it’s a single .ps1 file, it can be signed with an internal code‑signing certificate and distributed via existing management channels.
How we got here: the debloat movement
Win11Debloat first appeared on GitHub in late 2021, shortly after Windows 11 launched with a renewed focus on Widgets, Teams Chat, and other cloud‑linked experiences. Its early versions were essentially curated lists of Get-AppxPackage pipelines. Over time, the project grew to include registry tweaks, service configuration, and scheduled‑task removal.
The script never attempted to be a full‑fledged UI application. That minimalism protected it from the feature‑creep that plagued heavier tuning suites. Because every action is written in plain‑text PowerShell, users could inspect the code before running it—a transparency that earned the project thousands of stars and a network of contributors who helped maintain compatibility across Windows 10 and Windows 11 builds.
Microsoft’s own push toward AI integration—Copilot, Recall, and the system‑tray “ask me anything” box—sparked a new wave of interest in late 2024 and 2025. Win11Debloat responded by adding targeted switches for AI features, letting users opt out of specific services rather than blindly disabling a broad “AI” category.
The 07.11.2026 release is the culmination of that iterative refinement. It incorporates pull requests from over a dozen contributors and represents the first version that fully validates its modifications against Windows’ Component-Based Servicing stack, reducing the risk of bricking future cumulative updates.
How to get started with Win11Debloat 07.11.2026
- Download the script. Go to the official GitHub release page and save the
Win11Debloat.ps1file. Right‑click it, select Properties, and check “Unblock” if the option is present. - Review the documentation. The GitHub wiki (linked in the release notes) lists every parameter and explains what each tweak does. If you’re unsure about a particular switch, the wiki is your friend.
- Run WhatIf first. Open an elevated PowerShell prompt in the folder containing the script and run:
powershell .\Win11Debloat.ps1 -WhatIf
You’ll see a complete list of actions without any actual changes. Pipe the output to a file if you want to review later:
powershell .\Win11Debloat.ps1 -WhatIf | Out-File -FilePath ".\preview.txt" - Choose your switches. The default run removes common apps and disables telemetry. To block driver apps and disable AI features, use:
powershell .\Win11Debloat.ps1 -BlockDriverApps -DisableAIFeatures
If you only want to block driver apps and skip everything else:
powershell .\Win11Debloat.ps1 -OnlyBlockDriverApps - Reboot and verify. Some changes require a restart. Check the log file in
%TEMP%\Win11Debloat\to confirm what was done. - Rollback if needed. The script doesn’t keep a restore point, but you can reverse most app removals by running
wsreset -i(for Store apps) or re‑enabling services via the Services MMC. The driver‑app block can be undone with-UnblockDriverApps.
What’s next for Windows debloating
Win11Debloat’s maintainer has indicated on GitHub that future releases will explore integration with winget’s configuration manifests, potentially allowing users to describe their desired system state in a declarative YAML file. Meanwhile, Microsoft’s own approach to user choice is evolving; the company recently introduced a “Privacy dashboard” in Settings that lets some Enterprise users control diagnostic data, but consumer‑oriented options for removing inbox apps remain limited.
For now, Win11Debloat 07.11.2026 stands as the most polished and user‑friendly version of a tool that has become essential for anyone who wants Windows to work quietly in the background. The WhatIf preview takes the fear out of the process, and the driver‑app blocker addresses a real annoyance that Microsoft has yet to solve on its own.