Windows 11 Gets Native App Removal: Bye-Bye Bloatware via Group Policy
Microsoft has introduced a long-anticipated feature in Windows 11 that allows administrators to remove preinstalled Microsoft Store applications via official Group Policy. The new functionality, titled Remove Default Microsoft Store Packages, is already available in the latest Insider Preview builds.
Previously, the only way to eliminate bundled applications — such as Xbox, Clipchamp, Sticky Notes, and others — was through manual PowerShell commands. This method often resulted in installation failures, disrupted Autopilot and Enrollment Status Page processes, and in some cases, prevented users from signing in properly. Now, Microsoft offers a native and streamlined solution.
The Remove Default Microsoft Store Packages policy can be found in Group Policy under:
Computer Configuration > Administrative Templates > Windows Components > App Package Deployment.
When enabled, the system creates a registry key at:
HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx\RemoveDefaultMicrosoftStorePackages,
where packages can be listed for removal by specifying their unique Package Family Names.
The removal process takes place only when a new user profile is created. This mechanism is detailed within the appxalluserstore.dll library, which has been decompiled by researchers. The system checks for the enabled states of Feature_RemoveDefaultMicrosoftStorePackages and Feature_UxAccOptimization, then proceeds to delete the specified applications, relocating them to a special folder named DeletedAllUserPackages and logging the operation in AppXDeploymentServer.
Although the policy comes with a limited list of supported built-in apps by default, it can be manually extended. Administrators can include any Package Family Name — such as LinkedIn or Copilot — in the registry to ensure automatic removal during the creation of new user accounts. This approach is particularly advantageous for IT administrators using Intune: by integrating a PowerShell script into the Autopilot profile before the first sign-in, a clean environment can be deployed effortlessly.
However, some rough edges remain. Despite the removal, shortcuts for certain applications may still appear in the Start Menu. Attempting to launch them results in failure, and Event Viewer logs corresponding errors with code 0x80073D01.
Intune support is currently limited. Although a CSP setting is available (./Device/Vendor/MSFT/Policy/Config/ApplicationManagement/RemoveDefaultMicrosoftStorePackages), it has not yet been integrated into the Intune UI catalog. Nevertheless, PowerShell continues to serve as a viable workaround, offering flexible configuration until full integration arrives.
While still considered experimental and not recommended for production use, the Remove Default Microsoft Store Packages feature marks a significant step toward cleaner, more minimalist Windows deployments — without the burden of writing and debugging custom scripts.
