Since Windows 10, Windows includes many preinstalled Microsoft Store apps such as Clipchamp, Xbox, Weather, and Feedback Hub. Although these apps can be useful for some users, many IT administrators and power users view them as unnecessary bloatware that increases clutter on managed devices.
Starting with Windows 11 25H2, Microsoft introduced a new built-in policy: Remove Default Microsoft Store packages from the system. This policy gives administrators a simple and automated way to remove unwanted Microsoft Store apps by creating an Intune policy. By enabling this setting, organizations can keep Windows 11 devices clean, optimized, and consistent from the first login. No longer needs to deploy a PowerShell script to do it.
This blog post will guide you through the process of creating the Intune Remove Default Microsoft Store packages from the system policy and deploy it to a test group.
This feature is only available for Windows 25H2 Enterprise and Education and later.
The Remove Default Microsoft Store packages from the system policy. It lets you pick from a Microsoft app list that should be stripped out when a new user profile is created.
It currently supports the removal of the following apps:
The list will be updated as appropriate for future releases.
The policy is also available through Group Policy, but our post will focus on the Intune implementation.
The Group Policy setting showed up under: Computer Configuration > Administrative Templates > Windows Components > App Package Deployment

In Intune, the Remove Default Microsoft Store packages from the system policy is a Configuration Policy. (Device / Windows / Configuration)
Let’s create this policy to test it out.






Once deployed, the removal logic is triggered when a new user profile is created or when the user logs off and then logs back on.
The logic writes telemetry to the Microsoft \ Windows \ AppXDeployment-Server/Operational event log. If the policy or removal fails, you’ll see detailed errors there.
If it works, you will see Event ID 762 stating that the RemoveDefaultPackages uninstall override policy successfully removed the package.


Adjust to your linking, and if you’re happy with the result, you can deploy this in production.
As stated at the beginning of the blog post, no more script is needed going forward.
Please fill out the form, and one of our representatives will contact you in Less Than 24 Hours. We are open from Monday to Friday.
Thank you for subscribing to our newsletter or requesting a quote. You will receive our next month's newsletter. If you have requested a quote, we will get in touch with you as soon as possible.
Something went wrong!
Thank for your reply!