[Guide] Fix MS Store Issues script causes corrupt system if interrupted

[Villoh]

[Guide] How to recover from a broken system after "Fix MS Store Issues" script interruption

TL;DR: If you interrupted the Fix MS Store Issues.cmd script mid-execution and your system is now broken, this guide will get you back on track using only the Task Manager.

---

What happened?

The Fix MS Store Issues.cmd script works by:

1. Saving the original start types of critical services (ClipSVC, AppXSvc, StateRepository and their dependents)
2. Disabling and stopping all those services
3. Deleting StateRepository-Deployment.srd
4. Restoring everything in a finally block
5. Running wsreset.exe -i to reinstall the Store

The script insists "DO NOT CLOSE THIS SCRIPT!!!!" in red for a good reason: if the process is killed or the PC is restarted while it is trying to stop services (step 2–3), the finally block never runs. This leaves critical services permanently disabled and the system in a broken state.

---

Symptoms

• Black screen / broken desktop after reboot
• Taskbar missing or unresponsive
• UWP apps (Calculator, Photos, Store...) not launching
• wsappx-related errors in Event Viewer

---

Prerequisites

You need access to Task Manager. If your desktop is completely dead, you can still open it with:

Ctrl + Shift + Esc

Or, if that doesn't work:

Ctrl + Alt + Delete

This opens the Windows security screen — click Task Manager from there. This shortcut is intercepted directly by the kernel, so it works even when the desktop/shell is completely unresponsive.

Note: If you have no access to Task Manager at all, boot into Safe Mode (see the Prevention section at the end) and follow the same steps from there.

---

Step 1 — Open an elevated PowerShell

In Task Manager → File → Run new task

Type powershell, check "Create this task with administrative privileges", and click OK.

![Task Manager Run new task dialog with powershell typed and admin checkbox checked]

---

Step 2 — Restore service registry values

Set-Service will fail on these services because they are protected by TrustedInstaller. We need to patch the registry directly instead:

# Start values: 2 = Automatic, 3 = Manual, 4 = Disabled
$fixes = @{
    'StateRepository' = 3
    'AppXSvc'         = 3
    'ClipSVC'         = 3
}

foreach ($svc in $fixes.Keys) {
    $path = "HKLM:\SYSTEM\CurrentControlSet\Services\$svc"
    Set-ItemProperty -Path $path -Name 'Start' -Value $fixes[$svc] -Type DWord -Force
    Write-Host "Patched registry: $svc" -ForegroundColor Green
}

Expected output:

Patched registry: AppXSvc
Patched registry: StateRepository
Patched registry: ClipSVC

---

Step 3 — Start the services and run wsreset

Start-Service StateRepository -ErrorAction SilentlyContinue
Start-Service AppXSvc         -ErrorAction SilentlyContinue
Start-Service ClipSVC         -ErrorAction SilentlyContinue
wsreset.exe -i

---

Step 4 — Restart

Restart-Computer -Force

Or from Task Manager: Run new task → shutdown /r /t 0

---

Step 5 — Verify everything is healthy

After rebooting, open PowerShell and run:

# Check service states
@('StateRepository', 'AppXSvc', 'ClipSVC') | ForEach-Object {
    $s = Get-Service $_ -ErrorAction SilentlyContinue
    if ($s) { "$($s.Name) -> $($s.Status) / $($s.StartType)" }
    else     { "$_ -> NOT FOUND" }
}

Expected output:

StateRepository -> Running / Manual
AppXSvc         -> Running / Manual
ClipSVC         -> Running / Manual

The script also disables dependent services discovered dynamically at runtime via Get-AllDependents. The three above are the only ones guaranteed to be affected on every system.

Then run a full system integrity check:

sfc /scannow

If sfc reports errors it cannot fix, follow up with:

DISM /Online /Cleanup-Image /RestoreHealth

Finally, open the Microsoft Store and do a test search to confirm it works.

---

Root cause

The script stops services that are normally protected and held open by the system. On a running Windows installation (even AtlasOS), some of these services have dependents that resist stopping, causing the script to loop on WaitForStatus. If the user restarts during this loop, the finally block responsible for restoring everything never executes.

---

Prevention (recommended workflow)

To safely run this script in the future:

1. Create a Restore Point first

Via PowerShell:

Checkpoint-Computer -Description "Before Fix MS Store Issues" -RestorePointType "MODIFY_SETTINGS"

Via UI: Search for "Create a restore point" in the Start Menu → click Create... → give it a name → OK.

2. Run the script in Safe Mode

In Safe Mode, AppX/UWP services do not start, so the script never gets stuck trying to stop them. Once in Safe Mode, navigate to the AtlasOS folder and run the script normally — it will complete without issues.

---

How to boot into Safe Mode

✅ System is working normally

Option A — msconfig: Win + R → msconfig → Boot tab → check Safe boot (Minimal) → OK → Restart.

To go back to normal after: open msconfig again and uncheck Safe boot.

Option B — Command: Win + R (or Task Manager → Run new task):

shutdown /r /o /t 0

Then: Troubleshoot → Advanced options → Startup Settings → Restart → F4 (Safe Mode)

🆘 Only the login screen is available

On the Windows login screen, hold Shift and click Power → Restart. This forces Windows into the recovery environment without needing a working desktop.

Then: Troubleshoot → Advanced options → Startup Settings → Restart → F4 (Safe Mode)

---

References

• Script source: [9. Troubleshooting/Fix MS Store Issues.cmd](https://github.com/Atlas-OS/Atlas/blob/new-update/src/playbook/Executables/AtlasDesktop/9.%20Troubleshooting/Fix%20MS%20Store%20Issues.cmd)
• AtlasOS Microsoft Store docs: https://docs.atlasos.net/faq/general-faq/microsoft-store/

---