Why Store Apps Refuse to Update on a Hibernated Windows 11 PC

Quick fix: The Microsoft Store update service uses Windows Push Notification (WNS) connections that don’t survive Hibernate — after wake, WNS reconnects but the Store update scheduler doesn’t re-arm. Sign out and back in, or restart the Microsoft Store via Get-Process *WindowsStore* | Stop-Process -Force to kick the scheduler.

You hibernated your laptop for a few days. On wake, you open Microsoft Store and notice that pending updates from before haven’t installed and no new updates appear. Click Get updates and it stays stuck on Checking for updates… indefinitely. The Store service hasn’t crashed — it just hasn’t reconnected to its update backend after the long sleep.

What breaks during hibernation

Microsoft Store uses three things in the background: a persistent WNS (Windows Push Notification Service) socket, a scheduled task (Microsoft Store Update) that fires every few hours, and a background service (WindowsUpdate) that gets called for shared download infrastructure. During Hibernate, the WNS socket closes cleanly. On wake, Windows expects WNS to reconnect, the scheduled task to fire on its next trigger, and the Store to refresh its update list. In practice, WNS reconnects reliably but the Store’s update scheduler sometimes thinks it’s already running and skips the wake-up refresh.

The fix is to kick the Store into refreshing its state — either by signing out (which forces a full reconnect) or by restarting the Store process.

Method 1: Restart the Microsoft Store process

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Find Microsoft Store (search the Processes tab; it groups under the Store app name).
3. Right-click and choose End task.
4. Wait 5 seconds, then reopen the Store from Start.
5. Click Library → Get updates. The list refreshes within 30 seconds.

This is the lightest path and resolves most post-hibernate stuck cases. The Store app reinitializes its WNS connection and re-arms the update scheduler.

Method 2: Reset the Windows Update / Delivery Optimization services

If Method 1 doesn’t help, the shared download infrastructure used by the Store may also be stuck.

1. Open elevated Command Prompt.
2. Run:
   
   net stop wuauserv

net stop dosvc

net start dosvc

net start wuauserv
3. Open the Microsoft Store and click Get updates again.
4. Wait 2 minutes — the queue should populate.

The Store delegates downloads to the same Delivery Optimization service that Windows Update uses. Restarting it forces both Store and Windows Update to renegotiate their queues.

Method 3: Sign out and back in to the Microsoft account

For chronic post-hibernate Store failures, sign out completely.

1. Open Microsoft Store. Click your profile icon (top-right).
2. Click Sign out.
3. Close the Store.
4. Open Microsoft Store again. Click the profile icon and sign in with your account.
5. Wait for the home page to populate, then click Library → Get updates. The queue should be active.

This is more invasive but reliably clears any stale authentication tokens from before the hibernate.

How to verify the fix worked

• Microsoft Store Library page shows pending updates with download progress, or reports Your apps and games are up to date.
• Within 5 minutes of clicking Get updates, at least one app finishes updating.
• Run Get-AppxPackage -Name Microsoft.WindowsStore | Select-Object Version — the version is current.
• Open Task Scheduler → \Microsoft\Windows\WindowsUpdate\sih and \Microsoft\Windows\InstallService\ — the tasks have recent run timestamps.

If none of these work

If updates remain stuck after process restart, service cycle, and re-sign-in, the issue may be a corrupted Microsoft Store cache. Run wsreset.exe from the Run box to clear it. If that doesn’t help, try Get-AppxPackage *windowsstore* | Reset-AppxPackage in elevated PowerShell, which fully reinitializes the Store app. For managed devices, the Intune company portal may interfere with Store updates if both are competing for the same APIs — coordinate with IT to determine which tool should manage Store apps. Long-term, if hibernation regularly breaks Store updates, consider using Sleep instead — the RAM-resident state stays connected and the issue doesn’t occur.

Bottom line: Post-hibernate Store stalls are a scheduler/WNS reconnection issue. Restart the Store process; if that fails, restart the supporting services; if those fail, sign out and back in. One of those three resolves nearly every case.