Pre-installed apps and shortcuts — commonly labeled
bloatware — can turn a fresh Windows 11 experience into a cluttered, slower one within minutes of first boot. This article provides a practical, source-verified playbook to identify, remove, and prevent bloatware on Windows 11 using built-in tools and vetted third-party utilities, while weighing the benefits and risks of each approach so readers can choose the method that matches their comfort level and system needs.
Background / Overview
Bloatware refers to any preinstalled software — trial packages, OEM utilities, store app shortcuts, or Microsoft components that are not essential to the average user’s workflow. These programs consume disk space, may run background services, and can increase the system’s attack surface. Removing unnecessary apps often yields measurable improvements in boot time, responsiveness, and available storage, especially on devices with limited RAM and slower drives.
Windows 11 exposes several tiers for dealing with bloatware:
- Beginner: manual uninstall through Settings and disabling startup/background tasks.
- Intermediate: using Windows Package Manager (winget) or third-party GUI tools to uninstall multiple apps safely.
- Advanced: PowerShell and DISM commands to remove app packages for current users or provisioned packages for all users and future profiles.
This article verifies the commands, explains when to use each tool, and highlights where Windows updates or OEM behavior can reintroduce apps — so readers can debloat safely and sustainably.
What counts as bloatware in Windows 11?
Bloatware typically includes:
- Trial or promotional software (antivirus trials, trials for office suites).
- OEM utilities (brand-specific updater/assistant apps).
- Preinstalled games and entertainment titles.
- Microsoft Store quick-install tiles and “installer links” that are not full apps until clicked.
- Optional Microsoft apps like Clipchamp, preinstalled weather/News apps, or the Xbox app for users who don’t use Xbox services.
Not all preinstalled items are safe to remove. Libraries and runtimes (e.g., Visual C++ redistributables, .NET runtimes) are often required by other software. Removing these can cause crashes or break functionality.
Safety checklist before removing anything
Always perform these safety steps before debloating:
- Create a System Restore Point and a file backup. This is the single best precaution for accidental breakage.
- Note which OEM utilities manage firmware or battery profiles — keep those until confirmed unnecessary.
- Document the exact list of removals (screenshots or a text list) so apps can be reinstalled later.
- If using scripts or third‑party tools, prefer official project pages or GitHub releases, and verify community reputation.
Overview of removal methods
Beginner: Manual uninstall via Settings (safe, reversible)
This is the default method for most users and should be the first step.
Steps (brief):
- Open Settings (Win + I) → Apps → Installed apps.
- Find the app, click the three-dot menu (⁝) and select Uninstall.
- For Start Menu tiles: open Start → All apps → right-click the tile → Uninstall for shortcuts/installer links.
Why use it:
- Minimal risk.
- Reversible by reinstalling from Microsoft Store or vendor website.
- Works for most third‑party and many Microsoft Store apps.
Limitations:
- Some system apps show the Uninstall option as disabled or are not listed.
- Removes the app only for the current user (default behavior for many UWP packages).
Intermediate: Use Windows Package Manager (winget) for cleaner bulk removals
winget is a modern, supported command-line package manager included with recent Windows 11 versions. It can list installed apps and uninstall by name or ID.
Key facts (verified):
- The official uninstall syntax is
winget uninstall [[-q] <query>] and accepts options like --name, --id, --source, and --scope. The tool may prompt to disambiguate if a query matches multiple packages.
winget list shows installed packages; winget uninstall "App Name" removes them. If the uninstall command triggers Microsoft Store prompts, using --source winget can avoid store agreement interruptions.
When to use:
- To remove multiple non-system apps quickly.
- When preferring repeatable, scriptable workflows.
- When GUI tools are not available or permission to automate removals is needed.
Caveats:
- Some legacy apps or OEM utilities may not be manageable by winget.
- Winget metadata or uninstallers can fail in edge cases; community bug reports exist, so verify results after running.
Advanced (per-user): PowerShell and Get-AppxPackage (targeted, powerful)
PowerShell commands remove built-in UWP/MSIX apps for the current user (or all users with the right flags). Use these only with administrator privileges and caution.
Core commands:
- List packages:
Get-AppxPackage | Select Name, PackageFullName
- Remove for current user:
Get-AppxPackage [I]XboxApp[/I] | Remove-AppxPackage
- Remove for all users (requires elevated session):
Get-AppxPackage -AllUsers [I]AppName[/I] | Remove-AppxPackage -AllUsers
Microsoft documentation and community guidance confirm these cmdlets and the
-AllUsers parameter for system-level removals. Removing packages critical to the system or shared frameworks can break Store apps that depend on them, so avoid packages with names like Microsoft.VCLibs or core runtime names. When to use:
- To remove an app from the currently logged-in profile that Settings cannot uninstall.
- When selectively targeting Microsoft Store apps (UWP/MSIX).
Caveats:
- Removing a package this way may not prevent the app from being provisioned to new user accounts unless the provisioned package is removed (see DISM section).
- Do not remove runtime libraries unless certain they’re unused.
Advanced (system-wide & permanent): DISM Remove-ProvisionedAppxPackage
For a long‑term removal that prevents apps from being added to new user profiles (including freshly created accounts), use DISM to remove
provisioned Appx packages from the Windows image.
Core workflow:
- List provisioned packages:
DISM /Online /Get-ProvisionedAppxPackages | Select-String PackageName
- Remove a provisioned package verbatim:
DISM /Online /Remove-ProvisionedAppxPackage /PackageName:FULL_PACKAGE_NAME
Official Microsoft documentation explains these DISM options and warns that
/Remove-ProvisionedAppxPackage removes the auto‑registration behavior for new accounts; if the app is already registered for existing users,
Remove-AppxPackage must be used first to remove it from those profiles. When to use:
- When building or maintaining images for many users.
- To permanently stop OEM or Microsoft apps from reappearing for future accounts.
Risks:
- This operation changes the system image and is difficult to reverse without a restore point or reinstall.
- Incorrect package names or removing shared frameworks can destabilize the Store or dependent apps.
Fresh Install / “Fresh Start” / Reset this PC (cleanest, but disruptive)
Windows no longer exposes "Fresh Start" as a separate flow in some releases; its functionality has been folded into
Reset this PC. The Reset experience (accessible under Settings → System → Recovery → Reset PC) provides
Keep my files and
Remove everything choices. During the process, the
Restore preinstalled apps? toggle (if present) controls whether OEM apps are restored — set it to
No to replicate the old Fresh Start behavior and remove manufacturer-supplied applications. Microsoft’s documentation and multiple independent guides confirm this approach. Why use it:
- Best when the system is cluttered beyond manual repair or when a fully refreshed base is desired.
- Preserves personal files (with Keep my files) while removing apps.
Downsides:
- Requires reinstalling all desired apps and may restore certain device-specific drivers or services only via OEM pages.
- Time-consuming and disruptive for daily workflows.
Third-party GUI tools (O&O AppBuster, Talon, BloatyNosy, Win11Debloat scripts)
Several community-reviewed tools provide a friendly interface to select and remove many items in batches. Tools like O&O AppBuster or community utilities such as Talon and curated debloat scripts can speed the process.
Best practices:
- Download from the official project page or GitHub release.
- Inspect the tool’s list and deselect anything you don’t understand.
- Ensure a restore point is created automatically or do so manually before proceeding.
Risks and caveats:
- Scripts and custom ISOs (Tiny11-style) are unsupported by Microsoft and may remove security components or alter update behavior; avoid using them as a primary machine’s default unless fully understood and tested in a separate environment.
Practical, step-by-step workflows (ranked by user level)
1) Quick & safe (Beginner) — 10–20 minutes
- Settings → Apps → Installed apps: remove obvious third‑party apps and games.
- Settings → Apps → Startup: disable unnecessary startup items to improve boot times.
- Task Manager → Processes: identify background processes using CPU and memory; research any unknown names before uninstalling.
- Optional: run a Storage Sense cleanup (Settings → System → Storage) to remove temporary files.
Results: immediate, low-risk gains in boot time and storage.
2) Targeted UWP clean-up (Intermediate, comfortable with PowerShell)
- Open Windows Terminal (Admin) → PowerShell.
- List UWP packages:
Get-AppxPackage | Select Name, PackageFullName
- Remove a package for current user:
Get-AppxPackage [I]clipchamp[/I] | Remove-AppxPackage
- If needed for all users (administrator):
Get-AppxPackage -AllUsers [I]xbox[/I] | Remove-AppxPackage -AllUsers
Note: To prevent reinstallation for new accounts, remove provisioned packages with DISM (next workflow).
3) System-wide, permanent removal (Advanced — DISM)
- Admin PowerShell or CMD:
DISM /Online /Get-ProvisionedAppxPackages | select-string PackageName to identify full package names.
- Remove the provisioned package exactly:
DISM /Online /Remove-ProvisionedAppxPackage /PackageName:FULL_PACKAGE_NAME
- Reboot and verify.
Important: If the package is already registered with existing user profiles, remove it from those profiles first with
Remove-AppxPackage. DISM removal is for the image and future profiles.
4) Bulk GUI method (Intermediate to Beginner)
- Download a trusted debloater (e.g., O&O AppBuster, Talon).
- Review and deselect anything unfamiliar.
- Create a restore point when prompted.
- Execute the removal and reboot.
Tip: Use portable versions when available so no new apps are added to the system.
How Windows updates and OEM behavior affect debloating
- Major feature updates or OEM recovery images can reintroduce provisioned apps. Be prepared to reapply DISM removals or script-based cleanups after major updates. This behavior is common enough that guides advise re-running debloats after feature upgrades.
- Reset workflows that include the “Restore preinstalled apps?” option can be used intentionally to control whether OEM apps are returned. If the option is missing, the device likely has no OEM-provisioned apps to restore. Microsoft documentation explains how Reset this PC handles preinstalled apps.
Troubleshooting and recovery
- If an app removal breaks functionality, restore the System Restore Point or perform an in-place upgrade using the Media Creation Tool to repair system files without affecting personal data.
- If a required runtime (Visual C++/NET) is removed inadvertently, reinstall runtimes from Microsoft’s official download pages or reinstall affected apps to restore dependencies.
- If a DISM operation failed, double-check the package full name string — it must match exactly, including version/architecture/publisher suffixes. Microsoft’s DISM docs show exact syntax to avoid errors.
Security and privacy considerations
- Fewer installed apps reduce the number of potential vulnerabilities and background telemetry sources. However, removing security-related OEM tools without understanding their function (e.g., firmware update agents) can delay critical updates. Keep at least one method to update drivers/firmware (Windows Update or vendor site).
- Use only well-known, community-reviewed debloat tools. Avoid downloading “debloated” Windows ISOs or unknown installers from third-party stores — these are high-risk and can introduce malware. Community projects can be audited when open-source and actively maintained.
Recommended minimal commands (copy-ready)
- List installed app packages for current user:
Get-AppxPackage | Select Name, PackageFullName
- Remove an app for current user:
Get-AppxPackage [I]clipchamp[/I] | Remove-AppxPackage
- Remove an app for all users (admin PowerShell):
Get-AppxPackage -AllUsers [I]xbox[/I] | Remove-AppxPackage -AllUsers
- List provisioned packages:
DISM /Online /Get-ProvisionedAppxPackages | findstr /i Packagename
- Remove a provisioned package (exact name required):
DISM /Online /Remove-ProvisionedAppxPackage /PackageName:Contoso.App_1.0.0.0_neutral__8wekyb3d8bbwe
- Uninstall using winget:
Code:
winget list
winget uninstall --name "Microsoft To Do"
(Use --source winget to bypass Store agreement prompts if needed.
Strengths and risks — critical analysis
Strengths:
- The multi-tier approach lets users choose risk/reward levels: Settings for safety, PowerShell/DISM for thoroughness, winget and GUI tools for automation.
- DISM enables true image-level control, preventing re-provisioning for new accounts — essential for administrators or technicians building standardized machines. Microsoft’s DISM docs make the intended behavior clear.
- winget is now a robust, documented tool for package management and integrates well into scripted workflows. Its uninstall command and options are maintained in the official docs.
Risks and caveats:
- Overzealous removal can break Store apps or dependent runtimes; guarding against removing shared libraries is critical. Official guidance and community experience both warn strongly about removing Microsoft.VCLibs/.NET-native packages.
- Major Windows feature updates or OEM recovery procedures can reintroduce provisioned apps; permanent-looking removals may not survive every update path unless the image is adjusted (DISM) or a reset is correctly configured.
- Third-party scripts, ISOs, or unofficial “lite” builds of Windows carry serious security and support risks and are not recommended for primary machines; community consensus advises testing in VMs or spare hardware first.
FAQs (timely answers)
- Will removing bloatware materially speed up my PC?
- Yes, particularly on low-RAM machines. Decreasing background services and startup apps often yields the most noticeable improvements. Removing store shortcuts yields storage gains but little performance change.
- Will Windows reinstall apps after updates?
- Major feature updates or a factory recovery can reintroduce apps; expect to check and reapply debloats after big upgrades. Use DISM to change the provisioned image to reduce recurrence.
- Is it safe to use debloat scripts or Tiny11?
- Community tools can help power users, but modified Windows distributions or unsupported ISOs are risky for primary devices. Prefer curated, open-source tools from reputable GitHub repos and test in a VM first.
- How do I restore something I removed?
- If a System Restore Point exists, use it. Otherwise, reinstall the app from Microsoft Store or vendor site, or perform an in-place repair using Microsoft’s Media Creation Tool to restore system components.
Final recommendations
- Start with manual removals and startup tweaks; these are low-risk and often solve the worst performance problems.
- Use winget for repeatable uninstall tasks and PowerShell for targeted UWP cleanup, but avoid removing runtime libraries. Confirm each package name before running destructive commands.
- Use DISM only when comfortable editing the system image or when preparing machines for multiple users; always create a system restore point first.
- If the system is severely cluttered, prefer Reset this PC with Restore preinstalled apps? = No (when available) instead of untrusted third‑party ISOs. This approach gives a clean base while remaining supported by Microsoft.
- When in doubt, test on a spare machine or a virtual machine before applying broad removals to the primary device. Community tools and scripts are powerful, but the safest path is conservative, informed action.
Following these tactics will help reclaim performance and restore control over a Windows 11 system while avoiding common pitfalls that come with aggressive or uninformed debloating.
Source: WinBuzzer
How to Remove Bloatware From Windows 11 - WinBuzzer