Where Are Microsoft Store Apps Installed: Default Locations and How to Find Them

Windows stores these apps in a protected sandbox to keep your system secure, which is why you can't just drag them like traditional programs. 🔥 The folder names encode the app's identity—like Microsoft.WindowsCalculator8wekyb3d8bbwe—so you can spot them easily.

Since they're updated automatically, their paths stay consistent even after upgrades, which is handy for troubleshooting or reinstalling.

If you ever need to find one manually, I recommend using File Explorer with hidden items enabled or running a PowerShell command like Get-AppxPackage—it’s faster than digging through folders.

Just remember, you’ll need admin rights to peek inside, and some apps might feel "locked down" because of Windows' built-in protections.

How Windows handles Microsoft Store app installation paths

Windows uses a specialized architecture called Universal Windows Platform (UWP) to isolate Microsoft Store apps in the Program Files\WindowsApps folder. This isn't just a random location—it's a security measure. Each app gets its own sandboxed environment, preventing one app from interfering with others or your system.

The folder structure encodes critical metadata like the publisher, app name, and version (e.g., Microsoft.WindowsCalculator1.23.456.0x64__8wekyb3d8bbwe), making it easy to identify and manage individual apps.

The versioning system works differently than traditional desktop apps. When an update arrives, Windows doesn't overwrite the existing files—it creates a new version folder while keeping old data intact. This means you'll often see multiple versioned folders for the same app (e.g., AppName1.0, AppName1.1).

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateChange tracks which version is active, ensuring smooth transitions without data loss. 💫

Here's why this differs from traditional Win32 apps: those install to Program Files with simple paths like C:\Program Files\AppName, and updates typically replace files directly. Store apps use AppxPackage manifests stored in the registry, which define permissions, dependencies, and sandbox rules.

This system prevents conflicts between apps and makes it easier for Microsoft to push updates silently in the background—no manual reinstalls needed.

You might notice some apps appear in WindowsApps but don't show up in File Explorer by default. That's because Windows hides the folder by default (it's marked as "system protected"). To access it, you'll need to enable "Hidden items" in File Explorer or use PowerShell commands like Get-AppxPackage.

The folder's location also explains why you can't just drag Store apps to another drive—they're tightly integrated with Windows' virtualization layer.

For advanced users, the AppxManifest.xml file inside each app's folder contains detailed permissions and capabilities. For example, a camera app might request access to your webcam hardware, while a game might need internet permissions.

These declarations are enforced by Windows' AppContainer sandbox, which restricts apps to only the resources they've been granted. This is why some Store apps feel "locked down"—they're designed to be secure by default. ✨

What most people don't realize is how this system enables seamless updates. When Microsoft pushes a new version of an app (like Edge or Calculator), Windows downloads the update to a temporary location, then atomically switches the active version by updating registry pointers.

Your data stays in a separate LocalState folder (usually in %LocalAppData%\Packages), so upgrades never wipe your settings or saved files.

This architecture also explains why you can't just "uninstall" Store apps by deleting their folders. Windows tracks installed apps through registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateChange, and the Store maintains its own uninstall records.

To properly remove an app, you must use either the Store itself or PowerShell's Remove-AppxPackage command—anything else risks breaking system dependencies. 🔥

Finding and accessing Microsoft Store app files manually

If you need to locate a Microsoft Store app's files, start by opening File Explorer and navigating to C:\Program Files\WindowsApps. You'll need to enable "Hidden items" in the View tab first—this folder is normally hidden for security.

Look for folders with names like Microsoft.WindowsCalculator8wekyb3d8bbwe, where the publisher and app name are encoded. For a faster search, use the address bar's search function to filter by keywords like "Spotify" or "Edge."

One common mistake is trying to delete Store app folders directly—this can break system dependencies. Instead, use PowerShell's Remove-AppxPackage command or uninstall through the Microsoft Store. For apps that refuse to uninstall, check for leftover registry entries under HKEYLOCALMACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateChange and clean them manually (backup first!).

• List all installed apps: Get-AppxPackage | Select Name, PackageFullName
• Reinstall a specific app: Add-AppxPackage -Register "C:\Path\To\App.appx"
• Force a repair: Get-AppxPackage AppName | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register $.InstallLocation\AppXManifest.xml}

Remember: Store apps are designed to be self-contained. If you're troubleshooting, always work with the official tools first before diving into manual edits. 🔥