Uninstall Microsoft Store Apps

By Daniel Carter · Published September 25, 2026 · Updated September 25, 2026

Handle Store apps separately from classic Win32 programs and preserve shared Windows components. The scope is intentionally limited to Store apps so this page does not compete with general download, edition, or broad troubleshooting guides.

A normal vendor uninstall is usually the safest starting point because it understands the application’s own services, drivers, and shared components. Additional scanning is a review stage, not permission to delete every matching result automatically.

What to establish first

Record the exact program name, publisher, version, installation source, Windows edition, and whether the PC is personally managed or controlled by an organization. Save active work and close the target program. If removal could affect projects, profiles, a network adapter, a device, or licensed data, make a separate backup before proceeding.

Confirm the publisher and installation path.
Check whether the application has its own documented removal procedure.
Create a recovery option appropriate to the risk; personal files require a real backup.
Do not approve a long list of leftover items without reviewing paths and ownership.

Decision point for Store apps

Before taking action, decide whether the goal is simply to stop the application, reclaim disk space, correct a damaged installation, protect privacy, or prepare a clean reinstall. Those outcomes are not interchangeable. For Store apps, some provisioned or system apps can be restored by Windows and should not be forced out. If the normal uninstall completes and the original symptom is gone, additional deletion may add risk without providing a measurable benefit. If the process fails, keep the error and installation evidence before moving to a forced-removal path.

Compare the cost of leaving a harmless remnant with the cost of removing a shared component incorrectly. A conservative decision is especially important on work PCs, systems with specialized hardware, and machines that cannot be restored quickly. Document the choice so a later administrator knows which files, services, profiles, and settings were intentionally retained.

Recommended workflow

Start with the normal path. Use Windows Settings or the application’s own uninstaller unless the page’s specific failure state prevents it.
Read every prompt. Decide separately whether to keep user data, settings, projects, shared components, or licensing information.
Restart when required. Services, drivers, and locked files may not be removed until Windows restarts.
Review leftovers conservatively. some provisioned or system apps can be restored by Windows and should not be forced out. Compare each proposed path with the known publisher, install directory, and user profile.
Validate the result. Confirm that Windows starts normally, dependent software still works, and the intended program no longer runs or registers at startup.

Safety checks

A deep scan should not be treated as an automatic cleaning command. Parent registry keys and common folders may contain entries used by other software. Prefer individually identified child items over broad containers. Avoid manual deletion from Windows system folders and do not disable security controls globally merely to run an unverified executable.

System Restore can help with some configuration changes, but it is not a complete image backup and does not protect every personal file. For business or managed devices, follow the administrator’s process instead of attempting to bypass policy or elevation requirements.

How to verify success

Open Settings › Apps and confirm the target entry is gone. Check Task Manager only for processes clearly associated with the removed product, then inspect startup entries and relevant services if the original problem involved background activity. Do not use an empty search result as the sole proof of complete removal; shared packages and user data can intentionally remain.

If a reinstall is planned, test the new installation before restoring the old profile. Reintroducing all prior settings at once can bring back the same corruption or incompatible extension that caused the original failure.

Common mistakes

Using forced removal before trying a normal vendor uninstall.
Deleting folders because their names look similar to the product.
Assuming every registry remnant slows Windows.
Removing drivers, runtimes, or shared components with an ordinary application.
Continuing after an unexpected warning without preserving logs or creating a recovery path.

If the procedure fails

Stop repeated deletion attempts and preserve the exact error. Check for a pending restart, active service, damaged installer cache, vendor repair option, or dedicated removal tool. Test one change at a time. When requesting help, provide the error text, application version, Windows build, installation source, and the last successful step without sending license keys or personal data.

Related guides

Primary sources

Microsoft Windows support
VS Revo Group product documentation and current release information
Our Windows testing methodology

Revo Cleaner is independent and is not affiliated with VS Revo Group. It distributes a clearly labeled installer copy through its own FileDrop button and does not sell licenses or provide product support.