App
Microsoft Store apps are installed in the Program Files\WindowsApps folder by default, where each app resides in a dedicated subfolder named after its package family. Unlike traditional programs, these apps are locked in place and require special tools like PowerShell or Settings to manage them.
This hidden directory is where Windows packages all its modern apps, keeping them isolated for security and performance. 💻 The folder’s name reflects Microsoft’s Universal Windows Platform (UWP) architecture, where apps run in a sandboxed environment—meaning they can’t access other files unless explicitly permitted.
When you update an app, Windows quietly replaces the files in this folder without asking, which is why you’ll never see a traditional "Program Files" uninstall option.
💡 In This Article
- Understanding WindowsApps Folder Structure
- How to Locate and Manage Microsoft Store Apps
Understanding WindowsApps folder structure
Here's what's actually happening under the hood: Microsoft Store apps live in Program Files\WindowsApps because this directory is part of Windows' Universal Windows Platform (UWP) architecture.
Each app gets its own subfolder named after its package family name (like "Microsoft.WindowsCalculator8wekyb3d8bbwe"), which is a unique identifier combining the publisher and app name. This naming convention ensures no conflicts between apps from different developers, even if they share similar names.
The folder's locked-down nature comes from Windows' sandboxing technology. UWP apps run in isolated environments with restricted permissions—think of it like a sealed container where the app can't freely access your system files unless you explicitly grant access.
This is why you can't just drag these folders to your desktop or delete them through File Explorer. The system protects your core files while keeping apps contained. Updates work by replacing the entire app package in this folder, which is why you never see traditional "Program Files" uninstall options.
What most people don't realize is how this structure affects app dependencies. Each app bundle contains not just the executable but also its required libraries, configuration files, and even language packs—all packed together in that single folder.
For example, the Microsoft.Office.Desktop1.0.0.0_x64__8wekyb3d8bbwe folder might contain over 100MB of files just for Word alone, including shared components used by other Office apps. This modular approach makes updates seamless but also means removing one app won't necessarily free up space if other apps share those dependencies.
When you install an app, Windows creates a symbolic link (shortcut) in %LocalAppData%\Microsoft\WindowsApps pointing to the actual files in Program Files\WindowsApps. This clever trick lets the system maintain clean paths while keeping all app data in one centralized location.
The folder's hidden status isn't just for security—it's also to prevent accidental modifications that could break the app's isolated environment. If you try to move these files, Windows will silently recreate them in the original location during the next app launch.
Here's a concrete example: The Microsoft.XboxGameOverlay1.0.0.0x64__8wekyb3d8bbwe folder typically weighs around 50-70MB and contains files like GameBar.exe, XboxGip.dll, and localized resource files. Even though it's just one app, Windows treats it as a self-contained unit with its own security context.
This is why you'll see apps like this in Task Manager under separate processes even when they're part of larger suites.
The structure also explains why some apps appear "missing" after updates. When Windows installs a new version, it might keep the old files temporarily while setting up the new version in a slightly different folder path.
The symbolic links ensure your shortcuts still work while the system cleans up the old files in the background. This invisible process is why you might see duplicate folders briefly during major updates—Windows is preparing the new environment before fully activating it.