Where Are Microsoft Store Apps Installed: Default Locations and Hidden Folders Explained

These installation paths reflect Microsoft's design choices to isolate Store apps from traditional Windows programs. 💻 The WindowsApps folder uses virtualization to prevent conflicts, while the Packages directories handle user-specific configurations—like saved game data or app preferences.

Unlike classic .exe installations, these folders are hidden by default because they contain system-protected files that shouldn't be manually edited without proper tools.

For example, if you install the Microsoft Edge app from the Store, you'll find its files in a folder named something like Microsoft.MicrosoftEdge_8wekyb3d8bbwe—that long string is the app's package family name, which Windows uses to track updates and dependencies.

This structure also explains why you can't simply delete these folders to uninstall apps: Windows manages them through the Store interface to maintain system integrity.

How Microsoft Store app installation folders work

Microsoft designed the C:\Program Files\WindowsApps folder to create a sandboxed environment where each Store app gets its own isolated space. Here's what's actually happening: Windows uses a technique called "virtualization" to redirect app files to this location, preventing conflicts with traditional Win32 programs.

The folder structure follows a strict naming convention where each subfolder contains the app's executable files, libraries, and dependencies - all tied to a unique package family name like Microsoft.WindowsCalculator8wekyb3d8bbwe. This naming system helps Windows track updates and dependencies without breaking other applications. 🔥

The package family name isn't random - it combines the publisher's name, app name, and a unique identifier assigned during development. For example, the Spotify app might have a path like SpotifyAB.SpotifyMusic1.141.514.0_x64__zpdnekdrzrea0. This structure allows Windows to maintain version control and roll back updates if needed.

The WindowsApps folder itself is protected by the operating system, and attempting to modify files directly can trigger security warnings or break app functionality. Unlike traditional installations that use .exe files, Store apps rely on Windows' package manager to handle installation, updates, and uninstallation.

What most people don't realize is how Windows handles app updates differently in this system. When you update a Store app, Windows doesn't overwrite the existing files - it creates a new version in the same folder while maintaining backward compatibility.

This is why you might see multiple version numbers in the folder path. The operating system uses a technique called "side-by-side execution" to ensure the updated version runs without affecting other apps. This approach differs significantly from traditional Win32 installations where updates often replace existing files in-place. 💛

For user-specific data, Windows creates separate directories in %LocalAppData%\Packages and %ProgramData%\Microsoft\Windows\Apps. The %LocalAppData% folder stores app configurations and cached data specific to your user account, while %ProgramData% contains system-wide app resources.

For example, your OneNote app might store notebook files in %LocalAppData%\Packages\Microsoft.OneNote_8wekyb3d8bbwe\LocalState. This separation ensures that app data remains accessible even if the main installation is updated or repaired.

One key difference from traditional installations is how Windows handles permissions. Store apps run with restricted privileges by default, and the operating system enforces these through the package manager. This security model prevents apps from accessing system files outside their designated folders unless explicitly granted permissions.

For instance, when you install Paint 3D, it can only access files in its designated folder and any locations you explicitly allow through the app's permissions dialog. This contrasts with classic Win32 apps that often request broad system access during installation. ✨

The virtualization layer also explains why you can't simply drag-and-drop Store apps between computers. Each installation is tied to your Windows license and the specific package family name.

When you try to transfer a Store app, Windows detects the missing virtualization layer and either prompts you to reinstall from the Store or creates a new virtualized copy. This design choice ensures app integrity but makes manual transfers impossible without specialized tools.

The system maintains this isolation even across Windows updates, preserving your app data through major OS version changes.

Understanding this structure helps explain why some troubleshooting steps differ from traditional software. For example, if an app crashes, you can't just reinstall it by running an .exe - you must use the Store interface. This ensures Windows properly updates the virtualization layer and maintains system consistency.

The package family naming convention also explains why some apps appear multiple times in the Store - each version maintains its own virtualized environment. 💫

Accessing and managing hidden Microsoft Store app files

First, you'll need to reveal these hidden folders before you can manage them. Open File Explorer and navigate to View in the top menu, then check the box for Hidden items.

This will reveal the WindowsApps folder in your Program Files directory. 🔥 Remember, these folders are protected by Windows, so you'll need to take ownership of them first if you want to modify or delete files manually.

Right-click the folder, select Properties, then go to the Security tab and click Advanced to change ownership to your user account.

For most users, the safest way to remove Store apps is through the official Microsoft Store interface. Simply open the Store, go to your library, right-click the app, and select Uninstall. This method ensures Windows properly cleans up all associated files and registry entries.

However, if you're dealing with corrupted apps or leftover files after uninstallation, you might need to use PowerShell. Open PowerShell as administrator and run Get-AppxPackage AppName to find the package name, then use Remove-AppxPackage PackageName to force removal. Always back up important app data before attempting manual cleanup. ✨

One common mistake is trying to delete the entire WindowsApps folder to free up space. This approach rarely works because Windows recreates the folder during the next system update. Instead, use the winget command-line tool to list installed apps and their sizes.

Run winget list to see all Store apps, then use winget uninstall followed by the package name to remove them safely. For stubborn leftover files, try running the DISM command DISM /Online /Cleanup-Image /StartComponentCleanup as administrator to remove orphaned components.

If you encounter permission errors when trying to access these folders, it's often because Windows is actively using the files. Close all instances of the app you're working with, then try again.

For persistent issues, boot into Safe Mode (hold Shift while clicking Restart in the Start menu) to gain temporary administrative access. Remember that manually editing these files can break your system or apps, so always use official tools when possible. 💫

For advanced users, you can use third-party tools like PowerToys or WinApp2Exe to convert Store apps to standalone executables, giving you more control over their installation paths. However, this process can void app licenses and may not work with all applications.

Always check the app's terms of service before attempting such modifications. When in doubt, stick to official uninstall methods to maintain system stability.