Why App Installer Service Stops After Long Inactivity on Windows 11

Quick fix: The App Installer service uses connection-state caching that times out after extended idle. Reset it by running winget source reset --force and then winget source update in an elevated terminal. The service rebuilds its source cache and store communication resumes.

You haven’t installed anything from the Microsoft Store or via winget for a few weeks. You go to install a package and the operation hangs or reports a connection error. The App Installer service backed by App Installer (the appx-package handler and winget host) has timed out its session and lost connection to its catalog sources.

Why the service times out

App Installer caches authentication tokens, source metadata, and connection state to avoid round-tripping for every install. Microsoft’s default cache lifetime is several days but not weeks. After extended inactivity, the tokens expire silently. The next winget call tries to use the stale state, hangs, and eventually errors out.

Method 1: Reset winget sources and update

1. Open Windows Terminal as Administrator.
2. Run:
   
   winget source reset --force
3. Then run:
   
   winget source update
4. The sources re-register and the catalog refreshes. Wait ~30 seconds.
5. Try the original install command. It should succeed.

Method 2: Restart the App Installer package

1. Open elevated PowerShell.
2. Run:
   
   Get-AppxPackage *DesktopAppInstaller* | Reset-AppxPackage
3. Wait ~30 seconds.
4. Open a new terminal and try winget again.

Method 3: Re-register App Installer with fresh state

1. In elevated PowerShell:
   
   Get-AppxPackage -AllUsers Microsoft.DesktopAppInstaller | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
2. Reboot.
3. winget should work cleanly after reboot.

How to verify the fix worked

• winget source list returns sources (winget, msstore) with timestamps.
• winget search vscode returns results quickly.
• winget install <package> succeeds.

If none of these work

If winget still fails after all three methods, check Internet connectivity to https://cdn.winget.microsoft.com — corporate firewalls sometimes block winget’s CDN. For managed devices, the policy may disable user-initiated winget; check Group Policy under Microsoft Desktop App Installer. As a workaround, install packages manually from the Microsoft Store or the publisher’s site until the service issue is resolved.

Bottom line: winget inactivity timeouts are common. Reset sources, update, and you’re back. For chronic issues, a full re-register fixes the package state.