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

This hidden folder sits outside traditional program directories because Windows treats Store apps differently—like modern web apps with built-in security. 🔥 The package identifier (like Microsoft.WindowsCalculator_8wekyb3d8bbwe) acts as a digital fingerprint, letting Windows manage updates and permissions automatically.

Unlike regular programs, you can't just drag these files to another drive; they're tied to your Windows license and system architecture.

Most users never need to touch this folder, but power users or IT admins often access it to troubleshoot corrupted apps or recover files. Windows 11 actually organizes these apps slightly differently than Windows 10, grouping them by architecture (x86 or ARM64) in subfolders.

Always back up important data before making changes, since modifying these files can break app functionality.

How Windows manages Microsoft Store app locations

Windows uses a sophisticated virtualization system called Windows Runtime (WinRT) to handle Microsoft Store apps, treating them like modern web applications rather than traditional desktop programs. This system creates isolated environments for each app, preventing conflicts and enhancing security.

When you install an app from the Microsoft Store, Windows assigns it a unique package identifier (like Microsoft.WindowsCalculator8wekyb3d8bbwe) that maps directly to its installation folder in Program Files\WindowsApps. This identifier isn't just a name—it's a cryptographic fingerprint that Windows uses to manage permissions, updates, and dependencies.

The folder structure follows strict naming conventions: Program Files\WindowsApps\PackageIdentifierArchitectureVersion. For example, the Calculator app might appear as Microsoft.WindowsCalculator8wekyb3d8bbwe1.23.1.0_x64__8wekyb3d8bbwe. The architecture (x64, x86, or ARM64) and version number are embedded in the filename itself.

This design prevents manual relocation because Windows tracks these apps through their package identifiers rather than physical paths. 💫 If you try to move the folder, Windows will recreate it during the next update or restart, breaking the app's functionality.

Security plays a critical role in this system. Windows enforces strict sandboxing for Store apps, isolating them from other system processes. Each app runs with limited permissions, and its files are protected by Windows' built-in security mechanisms.

Unlike traditional programs that can be freely copied or modified, Store apps are tied to your Windows license and system architecture. This is why you can't simply install a Store app on another PC—it requires the same architecture and a valid Microsoft account for activation.

Windows 10 and 11 handle these locations slightly differently. In Windows 10, all Store apps are stored directly in Program Files\WindowsApps, while Windows 11 introduces subfolders organized by architecture (e.g., Program Files\WindowsApps\x64). This change improves performance by grouping apps with similar requirements.

However, the core principle remains: these folders are hidden by default and require administrative privileges to access, ensuring users don't accidentally modify critical system files.

Here's what happens under the hood when you install a Store app: Windows downloads the package from the Microsoft Store, verifies its digital signature, and then extracts it to the designated folder. The app's executable and resources are stored in a compressed format, which Windows decompresses on-demand to save space.

This is why Store apps often have smaller footprint sizes compared to their traditional counterparts—some apps can be 90% smaller due to this compression.

For advanced users, understanding this system is key to troubleshooting. If an app crashes, you can often recover by resetting it through the Microsoft Store or manually deleting its folder (after backing up important data).

However, modifying these files improperly can lead to system instability or app failures. Always use built-in tools like PowerShell or Command Prompt with administrative privileges to interact with these locations safely. 🔥

Finding and accessing Microsoft Store app files

To locate Microsoft Store apps manually, start by opening File Explorer and navigating to View > Hidden items to reveal the protected Program Files\WindowsApps folder. This directory contains all your Store apps, but you'll need to run File Explorer as administrator to access it.

Once inside, you'll see folders with cryptic names like Microsoft.WindowsCalculator_8wekyb3d8bbwe—these are your installed apps. 🔥

For a quicker method, use PowerShell with this command: Get-AppxPackage | Select Name, PackageFullName. This lists all installed Store apps alongside their package identifiers, which you can then cross-reference with the folder names.

On Windows 11, apps are organized by architecture (x64, ARM64) in subfolders, so check those too if you don't see your app immediately.

If you encounter permission errors, right-click File Explorer and select Run as administrator. For stubborn access issues, try taking ownership of the folder via Command Prompt: takeown /f "C:\Program Files\WindowsApps" /r /d y, then grant full control with icacls "C:\Program Files\WindowsApps" /grant administrators:F /t.

Always back up important data first—modifying these files can disrupt app functionality.

Advanced users can use third-party tools like WinAero Tweaker or Universal Apps Manager to manage Store apps more easily. These utilities provide GUI interfaces for uninstalling, repairing, or resetting apps without diving into the command line. Just be cautious—removing the wrong files can break system components. 💫

Pro tip: If you're troubleshooting a specific app, note its package identifier from PowerShell first. This makes it easier to find the correct folder later, especially since Windows 11's architecture-based organization can be confusing at first glance.