Where Are Microsoft Store Apps Installed: Default Locations on Windows 10 and 11

Windows stores these apps in a protected folder because they run in a sandboxed environment, isolating them from your core system files. 🔥 This setup means updates happen automatically without you lifting a finger—no more manual reinstalls.

The hidden location also prevents accidental deletions, though you can safely uninstall apps via Settings or PowerShell if needed. I’ve seen many users surprised to learn their favorite Store apps live here, especially when troubleshooting performance issues.

For deeper control, you can use built-in tools like WinGet to manage installations or WSReset to refresh the Store cache when apps misbehave. Just remember: never delete files manually from WindowsApps—that can break system stability. Instead, use the official uninstall process to keep everything running smoothly.

How Windows manages Microsoft Store app locations

Windows uses a clever system called AppX package containers to store Microsoft Store apps in the WindowsApps folder. These containers act like virtualized environments, isolating apps from your core system files.

Unlike traditional Win32 applications (like those installed via .exe files), Store apps run in a sandboxed space with restricted permissions—this prevents one app from crashing your entire system or accessing files it shouldn't. The folder itself is hidden because it's managed by Windows Update and other system processes behind the scenes.

Here's why the location matters: Each app gets its own subfolder under WindowsApps (like Microsoft.WindowsCalculator_8wekyb3d8bbwe), containing all its executable files, dependencies, and resources. This structure makes updates seamless—Windows can replace just the app's files without touching your documents or other programs.

For comparison, traditional Win32 apps install directly into Program Files, where they might share system libraries and require manual updates. The WindowsApps folder typically sits on your system drive (usually C:\), but some apps may install on secondary drives if configured that way.

The sandboxing approach also explains why you can't just delete Store app files like regular programs. When you uninstall through Settings or PowerShell, Windows cleans up the entire package container and updates its registry entries. This prevents orphaned files that could bloat your system.

For example, if you uninstall the Photos app, Windows removes all its components from WindowsApps and resets any associated system settings—something that would be messy if apps installed directly into shared folders like traditional programs do.

Security plays a huge role here too. Store apps run under a low-integrity permission level by default, meaning they can't modify system files or access user data without explicit permission.

This is why apps like Microsoft Edge or Spotify (when installed from the Store) behave differently than their Win32 counterparts—they're constrained by design. Even if an app gets compromised, the sandbox limits damage to just that app's container.

Updates work silently because Windows downloads and installs them in the background, often while you're using other apps—no prompts, no interruptions.

What most users don't realize is how this system interacts with Windows Update. When Microsoft pushes an update for a Store app, it downloads the new package container and replaces the old one atomically—no partial updates that could break functionality.

This is why apps like Mail or Calendar seem to update instantly without you noticing. The trade-off? You lose some control compared to traditional installations, but the stability and security benefits make it worth it for most users.

For power users who need more flexibility, tools like WinGet (Windows Package Manager) provide a middle ground between the Store and manual installations.

One interesting quirk: Some Store apps (like Microsoft Teams) can also install Win32 components alongside their AppX package for full-featured functionality. These hybrid apps might create additional folders in Program Files, but the core app still runs from WindowsApps.

This dual-installation approach explains why some Store apps feel more integrated with Windows than others—it's not just about the location, but how the app was designed to interact with the system.

Accessing and managing Store app files safely

First, you’ll need to reveal the hidden WindowsApps folder since it’s tucked away by default. Open File Explorer, press Alt to show the ribbon, then go to View > Hidden items. This reveals all hidden folders, including the Program Files\WindowsApps directory.

Pro tip: Create a shortcut to this folder on your desktop for quick access—just right-click the folder, select Send to, then Desktop (create shortcut). 🔥

When navigating the folder, you’ll see apps stored with long, seemingly random names like Microsoft.WindowsCalculator8wekyb3d8bbwe. Don’t panic—this is normal! The format follows Publisher.AppNameVersionID. To find a specific app, use the search bar in File Explorer and type part of the app name.

For example, searching for "calculator" will quickly locate the folder. Remember, you’ll need admin rights to view or modify files here, so always open File Explorer as administrator if you encounter permission issues.

Uninstalling apps manually from this folder is risky and can break your system. Instead, use PowerShell for safe removal. Open PowerShell as admin and run Get-AppxPackage AppName (replace AppName with part of the app’s name). Then use Remove-AppxPackage PackageFullName to uninstall it cleanly.

For example, to remove the Calculator app, you’d first run Get-AppxPackage Calculator, note the full package name, then run Remove-AppxPackage Microsoft.WindowsCalculator8wekyb3d8bbwe. This method ensures Windows properly cleans up all associated files and registry entries.

And if you’re curious about app sizes, use winget export -o applist.xml to generate a report of all installed Store apps and their disk usage. This helps identify space-hogging apps you might want to remove. ✨