The latest release of Win11Debloat has landed, and it marks a decisive shift toward safety-first system tweaking. Version 06.24.2026, published on June 24 by open-source developer Raphire, removes support for legacy custom application lists entirely while introducing new policy warnings that guide users away from potentially harmful modifications. The PowerShell utility, popular among Windows 10 and 11 enthusiasts for stripping out unwanted features and pre-installed software, now relies exclusively on Microsoft-endorsed group policies and configuration service providers—a move that the developer calls a necessary evolution.

Win11Debloat began life as a community-driven answer to Windows bloatware. Over the years it evolved from a simple set of removal scripts into a modular framework capable of disabling Cortana, OneDrive, Xbox services, and the ever-growing suite of Copilot AI integrations. With each major Windows feature update, the tool had to adapt, often through trial and error, as hard-coded app removals sometimes led to broken system components or update failures. The 06.24.2026 release confronts that fragility head-on by jettisoning the old method.

“Legacy custom app-list support was essentially a list of package names we’d forcibly remove,” Raphire explained in release notes posted on the project’s GitHub repository. “But Microsoft’s continuous changes meant that list was never truly safe. A seemingly harmless removal could cascade into missing DLL dependencies, break shell extensions, or prevent cumulative updates from installing. Switching entirely to policy-based configuration eliminates that risk.”

The new policy warnings feature is the linchpin of this approach. When a user selects a debloat option that could conflict with system stability—such as completely disabling Microsoft Edge, removing Widgets, or neutering Windows Search—Win11Debloat now presents a detailed pop-up explaining the potential consequences. Each warning cites the specific group policy or registry key involved, its intended behavior according to Microsoft documentation, and known side effects observed during testing. Users must explicitly confirm they understand the risks before the script proceeds.

This change was driven by a surge of support requests on the repository’s issue tracker, where less experienced users often ran the tool with all options enabled and then complained about broken context menus, missing file associations, or failed updates. By coupling every aggressive tweak with a policy-aware warning, the tool effectively educates users while still giving them the control they crave.

Why Legacy Custom App-Lists Had to Go

The old custom app-list method allowed users to maintain a text file of Windows Package Manager package names that would be uninstalled during script execution. While flexible, it required constant maintenance. A package name valid in Windows 11 24H2 might be absent in 25H2, replaced by a new component, or integrated into a cumulative update. Users who forgot to update their lists often ended up with partial removals or, worse, broken installations.

Microsoft’s own shift toward servicing stack updates and feature-on-demand packages made static package lists increasingly dangerous. For example, removing the “MicrosoftWindows.Client.CBS” package in earlier builds sometimes gutted the Camera app; later updates merged that functionality into a different package, rendering the old removal ineffective but still consuming disk space as a dead registry entry. The new policy-only approach sidesteps these pitfalls by not touching package installations at all. Instead, it applies group policies and registry tweaks that instruct Windows to hide, disable, or suppress features without altering the underlying binary footprint—a technique that has been standard practice in enterprise IT for years.

How the New Policy Warnings Work

When the script detects a user has selected a “high-impact” action, it pauses execution and displays a multi-line warning. The system classifies actions into three tiers:

  • Low risk: Tweaks that disable telemetry, remove taskbar search icons, or hide the Copilot button. These use well-documented policies and are unlikely to cause side effects.
  • Medium risk: Disabling background services like Windows Update Medic, turning off Widgets completely, or removing Xbox Game Bar. These may affect specific apps or system behaviors but rarely break core OS functions.
  • High risk: Completely disabling Windows Update, removing Microsoft Defender integration, or stripping Edge WebView2 components. These can prevent security patches, cripple authentication flows, or cause application crashes.

For medium and high-risk actions, the warning not only explains the possible fallout but also offers an alternative—such as using a “soft disable” policy that can be reversed with a single click rather than a permanent removal. The script also generates a timestamped log file in the user’s Documents folder, detailing every policy applied and any warnings triggered, so troubleshooting later is straightforward.

One notable example in the 06.24.2026 release is the handling of Copilot. Early versions of Win11Debloat blindly removed the Copilot app package, which occasionally left behind orphaned shortcuts and broke taskbar search suggestions that relied on the same WebView2 runtime. Now, the tool applies a group policy (TurnOffWindowsCopilot) and hides the icon from the taskbar, leaving the underlying framework intact. The policy warning explicitly notes that Copilot’s web results in Windows Search may still function but can be separately disabled if desired.

What This Means for Windows 11 Users

For the average enthusiast, the updated tool represents a safer entry point into system tweaking. The removal of custom app-lists means users no longer have to hunt down accurate package names or worry about version compatibility. Instead, they run the script, select from pre-defined options, and receive real-time guidance if they’re about to do something reckless.

Power users who relied on the old custom app-list feature will need to adapt, but Raphire has provided a migration path. The project’s documentation now includes a mapping of common package removals to their policy equivalents. For example, instead of removing the “Microsoft.BingWeather” package, the tool sets Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent\DisableWindowsConsumerFeatures to 1, which hides the Weather app and prevents it from re-installing during updates. The developer has also promised to maintain a regularly updated JSON file mapping legacy package names to the corresponding policy paths, hosted on the repository.

Community reaction to the change has been largely positive, though some long-time users on the Win11Debloat subreddit expressed frustration at losing the fine-grained removal capability. “I know the risks, just let me nuke everything,” one user wrote. Another countered: “You say that now, but you’ll be back here in a month asking why your start menu is blank. The warnings are actually useful for once.”

Verified Improvements Over Previous Versions

Raphire’s release notes highlight several specific fixes that stem from the new approach:

  • Windows Update Medic service is no longer fully disabled by default, avoiding conflicts with cumulative update installation. Users who still want to suppress it receive a warning about potential update delays.
  • OneDrive “abandoned scope” errors that appeared after aggressive sync client removal have been eliminated by switching to a policy that simply hides the sync folder and disables the startup task.
  • Widget board removal no longer causes a cascade of Event Viewer errors about missing Web Experience Pack components.
  • The script can now detect if certain policies are already applied by group policy objects from a domain controller and will skip conflicting modifications, preserving enterprise-managed settings.

The tool also introduces a “what-if” preview mode that simulates the selected actions without making any changes, generating a report of policies that would be applied. This feature is aimed at IT professionals who may want to evaluate the script’s impact before deployment.

How to Get Started with Win11Debloat 06.24.2026

Using the tool remains straightforward. It requires an internet-connected Windows 10 or 11 machine with PowerShell 5.1 or later. The recommended method is to download the script from the official GitHub repository (github.com/Raphire/Win11Debloat) and run it with powershell.exe -ExecutionPolicy Bypass -File .\Win11Debloat.ps1. An alternative one-liner is available for users who prefer to pipe the script directly from the web, but Raphire cautions that the official repository is the only safe source; third-party mirrors may inject malicious code.

Upon execution, an interactive menu offers three primary modes:

  1. Default Debloat: Applies a curated set of tweaks that remove bloat without touching critical features. This mode is tested against the latest Windows 11 cumulative updates and targets pre-installed apps, telemetry, and interface clutter.
  2. Advanced Debloat: Allows granular selection of which categories to modify, with risk warnings enabled for dangerous options.
  3. Undo All Changes: Reverts every policy and registry tweak applied by the tool, restoring Windows to its original state.

A new addition in version 06.24.2026 is the “Policy Audit” option, which scans the current system and reports which group policies are already configured, helping users understand whether any previous tweaks might conflict with Win11Debloat’s actions.

Part of a Broader Trend Toward Policy Tweaking

Win11Debloat’s pivot mirrors a larger shift in the Windows customization community. Projects like O&O ShutUp10++, WPD, and even Microsoft’s own Security Compliance Toolkit have long favored policy-based configuration over file deletions. As Windows becomes more modular and tightly integrated with cloud services, the days of safely “ripping out” components are waning. A guided policy approach preserves the ability to receive updates, reduces helpdesk headaches, and aligns with Microsoft’s official guidance for managing Windows in enterprise environments.

That alignment is particularly important as Windows 11’s feature rollout accelerates. The operating system now updates several interface components—such as the Widgets board and Copilot—through the Microsoft Store, completely bypassing traditional cumulative updates. A policy that disables the Widgets service will persist across these store updates, whereas an app removal would need to be repeated every time a new version is pushed.

What’s Next for Win11Debloat

Raphire has indicated that future releases will focus on expanding the policy library to cover newly discovered tweaks and providing better documentation for each policy’s effect. There’s also discussion of a community-driven repository of “safe policy sets” that users can share, akin to the custom app-lists of old but validated against multiple Windows builds.

A companion GUI is not planned; the tool will remain a PowerShell script for transparency and auditability. However, integration with winget or the Windows package manager could simplify installation, and a signed version may be submitted to the Microsoft Store for enterprise convenience.

For now, the 06.24.2026 release of Win11Debloat stands as a significant milestone in the project’s maturity. By trading brute-force removal for education and policy enforcement, it empowers users to debloat their systems without sacrificing the stability that keeps Windows 11 humming along. Whether you’re a seasoned IT pro or a newcomer frustrated with pre-installed clutter, the new warnings and policy-only design make it harder to break things—and that’s a win for everyone.