Every Windows 10 installation ships with a large set of preinstalled Universal Windows Platform (UWP) apps. While Microsoft markets these as productivity and consumer-friendly features, in real-world enterprise environments they are often:
- Unused
- Confusing for end users
- A distraction in Start Menu layouts
- Unwanted in locked-down environments
- A compliance or attack-surface concern
Unlike traditional Win32 software, most built-in apps do not appear in Programs and Features, making them harder to manage using legacy tooling. This leads many IT teams to either ignore them or aggressively remove them—sometimes with unintended consequences.
This article explains:
- How Windows 10 app provisioning really works
- Safe vs unsafe apps to remove
- PowerShell methods used in production
- Why apps reappear after feature updates
- How to reverse changes cleanly
Important Reality Check: You Should Not Remove Everything
Before diving into removal, it’s worth stating clearly:
Uninstalling built-in apps does not significantly improve system performance or disk usage.
Most UWP apps:
- Consume minimal storage
- Are not actively running
- Do not impact boot time
The primary benefit of removing them is:
- Simplified Start Menu
- Cleaner corporate images
- Reduced user confusion
- Better UI consistency
In my experience managing SOE images, removing the wrong app causes more support tickets than leaving unused apps alone.
How Built-In Apps Are Actually Installed (Why They Come Back)
This is where many guides stop short.
Windows 10 uses two layers for built-in apps:
1. Provisioned Apps
- Installed into the OS image
- Automatically deployed to every new user profile
- Controlled via
Get-AppxProvisionedPackage
2. User-Installed Apps
- Installed per user
- Controlled via
Get-AppxPackage
If you only remove apps for the current user, they will:
- Reappear for new users
- Often return after Feature Updates
👉 Enterprise takeaway:
To truly remove an app, you must remove both the user instance and the provisioned package.
Method 1: Uninstall Built-In Apps Using Standard UI (Limited Use)
Some apps can be removed normally:
Option A: Start Menu
- Right-click the app
- Select Uninstall
Option B: Settings
Start → Settings → Apps → Apps & Features
Limitations:
- Many built-in apps won’t appear
- No control over provisioning
- Not suitable for enterprise imaging
This method is fine for single-user cleanup, not fleet management.
Method 2: PowerShell – The Professional Approach
PowerShell is the only reliable way to manage built-in apps at scale.
Step 1: Open PowerShell as Administrator
Win + X → Windows PowerShell (Admin)
Removing Built-In Apps (Current User)
Below are commonly removed apps in business environments.
3D Builder
Get-AppxPackage *3dbuilder* | Remove-AppxPackage
Alarms and Clock
Get-AppxPackage *windowsalarms* | Remove-AppxPackage
Calculator
Get-AppxPackage *windowscalculator* | Remove-AppxPackage
Calendar and Mail
Get-AppxPackage *windowscommunicationsapps* | Remove-AppxPackage
Camera
Get-AppxPackage *windowscamera* | Remove-AppxPackage
Groove Music
Get-AppxPackage *zunemusic* | Remove-AppxPackage
Movies & TV
Get-AppxPackage *zunevideo* | Remove-AppxPackage
News
Get-AppxPackage *bingnews* | Remove-AppxPackage
Weather
Get-AppxPackage *bingweather* | Remove-AppxPackage
Xbox
Get-AppxPackage *xboxapp* | Remove-AppxPackage
💡 Real-world note:
Some apps will throw errors — that’s expected. Microsoft protects certain core components.
Removing Provisioned Apps (The Part Most Guides Miss)
To stop apps from installing for new users, remove them from provisioning.
List Provisioned Apps
Get-AppxProvisionedPackage -Online | Select DisplayName
Remove a Provisioned App
Remove-AppxProvisionedPackage -Online -PackageName <PackageName>
⚠️ Warning:
Removing provisioned apps affects all future user profiles. Test thoroughly.
Apps That Cannot (or Should Not) Be Removed
❌ Do NOT Remove These
Microsoft Edge
- Required for:
- Windows Settings
- Help panes
- Some third-party installers
- Deep OS integration
- Removing Edge breaks system functionality
Cortana
- Handles local indexing
- Powers Start Menu search
- Required even if voice features are disabled
Windows Store
- Required for:
- App updates
- Reinstalling removed apps
- Some Windows components
Removing the Store often creates long-term management pain.
Why Apps Reappear After Windows Updates
Feature updates (e.g., 22H2 → 23H2) behave like in-place OS upgrades.
They often:
- Re-register provisioned apps
- Restore default app packages
- Ignore previous removals
Enterprise Mitigation Options
- Re-run removal scripts post-upgrade
- Use task sequences
- Apply Start Menu layout policies
- Accept minimal app presence instead of fighting it
How to Reinstall All Built-In Apps (Recovery Option)
If things go sideways, Microsoft provides a clean recovery command.
Reinstall Everything
Get-AppxPackage -AllUsers |
Foreach {
Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
}
Even if errors appear:
- Reboot
- Check Start Menu
- Apps usually return successfully
Real-World Best Practices from the Field
From years of Windows fleet management:
✔ Remove consumer-focused apps only
✔ Leave Edge, Cortana, Store intact
✔ Document every removal
✔ Automate via scripts, not manual clicks
✔ Test feature updates early
✔ Prefer Start Menu layout control over aggressive removal
Final Thoughts: Debloating Windows 10 Without Creating Technical Debt
Uninstalling built-in Windows 10 apps is not about performance — it’s about usability, consistency, and control.
The mistake many IT teams make is:
- Removing too much
- Not understanding provisioning
- Fighting Windows updates instead of planning for them
When done correctly, app removal:
- Reduces user confusion
- Simplifies SOE builds
- Avoids long-term support issues
When done poorly, it creates:
- Broken search
- Failed updates
- Difficult recoveries
Approach it surgically, not emotionally.
From my early days on the helpdesk through roles as a service desk manager, systems administrator, and network engineer, I’ve spent more than 25 years in the IT world. As I transition into cyber security, my goal is to make tech a little less confusing by sharing what I’ve learned and helping others wherever I can.