How to Reinstall a Pre-Installed Store App Without a Local Account

Quick fix: Use PowerShell’s Add-AppxPackage -Register against the package manifest in C:\Program Files\WindowsApps to reinstall a pre-provisioned Store app without needing to sign in to a Microsoft account. The app is restored from local files Microsoft already ships with Windows.

Some Windows 11 PCs use a local account for everything — no Microsoft account, no work account. Microsoft Store opens but won’t let you install apps without signing in. You uninstalled Mail or Calculator or Photos at some point and now need it back. The standard re-add path (open Store, search, install) requires authentication. The local-account path uses the provisioned package files already on disk.

What “provisioned” means

Microsoft ships a set of UWP apps with every Windows install — Calculator, Photos, Mail, Maps, Weather, and others. These are stored under C:\Program Files\WindowsApps as signed packages and registered with each new user during first sign-in. If you uninstall one with Remove-AppxPackage, the files are deleted for your user but stay in the WindowsApps store. You can re-register them without going through the Store at all.

The hidden bit: WindowsApps is locked down. You can’t browse it in Explorer without taking ownership. PowerShell can list it because the cmdlet runs in a different security context.

Method 1: Re-register a single app via PowerShell

1. Open PowerShell as Administrator.
2. Find the package family name. Run:
   
   Get-AppxPackage -AllUsers | Where-Object { $_.Name -like “*Calculator*” }
3. Note the PackageFamilyName and the InstallLocation (e.g., C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_11.2402.0.0_x64__8wekyb3d8bbwe).
4. Register it for your user:
   
   Add-AppxPackage -Register “C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_11.2402.0.0_x64__8wekyb3d8bbwe\AppxManifest.xml” -DisableDevelopmentMode
5. Open Start and search for the app name. It launches normally.

If Get-AppxPackage -AllUsers doesn’t list the app, the provisioned package was removed entirely (a previous “debloat” script or in-place upgrade can do this). Move to Method 3.

Method 2: Re-register all default apps at once

For PCs where multiple apps were stripped and you want them all back without searching for each manifest:

1. Open PowerShell as Administrator.
2. Run:
   
   Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
3. The command iterates every package present in WindowsApps and re-registers each one for the current user. Errors for packages that are already registered are safe to ignore.
4. Reboot for the full set of apps to appear in Start.

This is the “reset bloat” command often shared online. It restores defaults without touching user data.

Method 3: Restore a missing provisioned package from install.wim

If the app is gone from WindowsApps entirely, you need to extract it from a Windows install image.

1. Download the Windows 11 ISO from https://www.microsoft.com/software-download/windows11.
2. Mount the ISO (double-click in File Explorer).
3. Open elevated PowerShell.
4. List provisioned packages in the install image:
   
   Get-WindowsImage -ImagePath “D:\sources\install.wim” -Index 1 | Format-List
   
   (D: is the mounted ISO; Index 1 is the first Windows edition in the image.)
5. Extract the specific package. For Calculator:
   
   dism /Get-ProvisionedAppxPackages /Image:D:\ (lists all)
   
   dism /Add-ProvisionedAppxPackage /Online /PackagePath:“D:\sources\Microsoft.WindowsCalculator….appxbundle” /LicensePath:“D:\sources\Microsoft.WindowsCalculator….xml”
6. Re-run the Method 1 register command to register it for your user.

This is the only path for apps that were fully de-provisioned. Keep the ISO around — you’ll want it again if you de-bloat in the future.

How to verify the fix worked

• Open Start and type the app name. It appears in results.
• Click to launch. The app opens without sign-in prompts.
• Run Get-AppxPackage -Name *AppName* in PowerShell. The output shows the package as registered for the current user.
• Open Settings → Apps → Installed apps. The app is in the list.

If none of these work

If Add-AppxPackage -Register fails with Package could not be registered, the package files in WindowsApps may have been corrupted by an earlier failed install. Run sfc /scannow followed by dism /online /cleanup-image /restorehealth, then retry. For apps that complain about missing dependencies (e.g., Microsoft.UI.Xaml not found), install the corresponding framework package first — it’s in the same WindowsApps folder, just registered earlier in the dependency chain. As a last resort, an in-place repair upgrade reinstalls all provisioned apps without touching your user data.

Bottom line: Pre-installed Store apps are local files. PowerShell’s register command rebinds them to your user without needing the Store. For fully deprovisioned apps, the Windows ISO contains the original packages you can re-add.