# Windows App Removal: Installers, Packaged Apps and Portable Copies

Removing one Windows app launches a vendor wizard, another disappears through Settings, and a third has no uninstall button. Identify how this copy was installed before choosing a removal method. Deleting its desktop shortcut only removes that entry point.

## Identify the installation form

A traditional installer typically registers an uninstall entry and installs program files. It may also create services, startup entries and file associations. Packaged applications use Windows package management. Portable software generally runs from a folder, but where it stores settings depends on the product.

| Form of this copy | First removal route | What that route does not imply |
| --- | --- | --- |
| EXE/MSI installer | Installed apps, Control Panel or vendor uninstaller | Deleting its folder does not undo registrations and services |
| Windows-managed app package | Start menu or Installed apps | Store account history does not establish a current installation |
| Extracted portable copy | Vendor's portable instructions | Running from a folder does not prove all data stays there |

[Microsoft's uninstall guide](https://support.microsoft.com/en-us/windows/uninstall-or-remove-apps-and-programs-in-windows-4b55f974-2cc6-2d2b-d092-5905080eaf98) describes Start, Settings and Control Panel routes. Availability varies by app. Distribution source is also different from installation form: an app installed with WinGet can still depend on its vendor's uninstaller.

## Identify the copy you actually use

User installations, machine-wide installations, portable builds and previews can share a name. Check the installed entry's name, version and publisher, then inspect the running program's file location. Similar icons and old shortcuts make it easy to target the wrong copy.

VS Code provides an example: its installer and extracted ZIP have different removal procedures in the [official uninstall guide](https://code.visualstudio.com/docs/setup/uninstall). Deleting the ZIP program folder does not automatically remove separately stored settings and extensions. If the app still launches afterward, check whether the path belongs to another copy before declaring removal unsuccessful.

## Read the portable-data rules

VS Code's [Portable Mode](https://code.visualstudio.com/docs/editor/portable) uses a `data` folder beside the ZIP build to hold user data and extensions. That differs from a normal extracted build using user directories. Before moving or removing it, check whether portable mode is enabled and whether its settings, extensions and workspace state are needed.

Other portable apps may write to AppData, the registry or startup locations. VS Code's design cannot establish another product's behavior. Follow the product's instructions; retain uncertain external data if there is no documented removal route. A brand-like folder name is not proof of exclusive ownership.

<figure class="blog-diagram">
  <picture>
    <source media="(max-width: 900px)" srcset="/img/blog/windows-windows-app-installation-types-en-mobile.webp" type="image/webp" width="768" height="1180">
    <img src="/img/blog/windows-windows-app-installation-types-en.webp" width="1360" height="454" loading="lazy" alt="Identify how this copy is managed">
  </picture>
  <figcaption>The installation form selects the removal mechanism; personal and shared data need a separate decision.</figcaption>
</figure>

## WinGet is an entry point, not one universal uninstaller

List installed entries first. The first command below reads information; the second performs removal and should run only after verifying the target ID. Replace the illustrative ID with the exact one from the list.

```powershell
winget list
winget uninstall --id Vendor.ExampleApp --exact
```

[WinGet's uninstall documentation](https://learn.microsoft.com/en-us/windows/package-manager/winget/uninstall) explains that it can find apps installed through other routes. Its `--purge` behavior concerns portable packages, not a promise to erase every application's personal data. Complete vendor prompts and requested restarts; a wizard appearing is only the start of removal.

## Verify program removal and retained data separately

Bookmarks, editor extensions, chat history, databases and generated documents may remain intentionally. Use the product's export or backup tools before removal and open the exported copy to verify it. Store purchase and download history belongs to the account rather than the local installed-app list.

After uninstalling, refresh the list and inspect the original program path and processes. Check whether personal data remains according to your choice. Verify process paths and ownership instead of ending every process with the same name. Shared runtimes and vendor components may still serve another app; an empty folder tree is not the sole criterion for successful removal.

Continue with [uninstall failures](/windows/blog/windows-uninstall-fails) or [retained data](/windows/blog/what-apps-leave-after-uninstall) after identifying the installation involved.


Canonical: https://mole.fit/windows/blog/windows-app-installation-types