The State Repository Service<\/strong> is a core Windows component that provides infrastructure for the modern app model and stores state data for UWP apps and system components (including parts of Microsoft Edge). When something goes wrong with app state, system files, or Edge, this service can misbehave and hammer your CPU, sometimes in short but frequent spikes that freeze games, browsers, and even the desktop for a few seconds.<\/p>\n This tutorial is for:<\/p>\n You\u2019ll learn:<\/p>\n If you just want to make your PC usable again as fast as possible, start here. You can come back later for deeper fixes.<\/p>\n 1.1. Save everything and restart your PC. 2.1. Press Win + R, type 3.1. Open Settings \u2192 Apps \u2192 Installed apps<\/strong> (or Apps & features<\/strong>). 4.1. Right-click Start<\/strong> \u2192 Windows Terminal (Admin)<\/strong> or Command Prompt (Admin)<\/strong>. 4.3. Wait for it to finish. If the spikes keep coming back, move on to the full step-by-step guide.<\/p>\n Before diving deeper, make sure you have:<\/p>\n 1.1. Press Ctrl + Shift + Esc to open Task Manager<\/strong>. 1.4. Symptoms you might see:<\/p>\n If that\u2019s exactly what\u2019s happening, proceed with the fixes below.<\/p>\n Restarting the service often clears transient issues or stuck operations.<\/p>\n 2.1. Press Win + R, type 2.4. Switch back to Task Manager<\/strong> and monitor CPU for a few minutes. Corrupted system files are a common cause of misbehaving Windows services.<\/p>\n 3.1. Run SFC (System File Checker)<\/p>\n 3.2. Run DISM to repair the component store<\/p>\n Edge is frequently linked to State Repository Service high CPU and is one of the primary things to repair.<\/p>\n 4.1. Repair Microsoft Edge (non-destructive)<\/p>\n 4.2. Reset Microsoft Edge (more aggressive)<\/p>\n 4.3. Retest after Edge repair\/reset<\/p>\n If specific UWP apps or system apps are corrupted, the State Repository Service can get stuck handling their state. Re-registering built-in apps is an advanced but often effective fix.<\/p>\n Warning:<\/strong> This can reset default apps and some built-in app settings. Create a restore point first.<\/p>\n 5.1. Right-click Start<\/strong> \u2192 Windows Terminal (Admin)<\/strong> or PowerShell (Admin)<\/strong>. 5.3. Wait until the command completes (it may take several minutes).![\"State](\"https:\/\/myspybot.com\/wp-content\/uploads\/2025\/12\/State-Repository-Service-high-CPU.png\")
<\/a><\/p>\n\n
\n
Quick Triage (do this first if you\u2019re in a hurry)<\/h2>\n
1. Reboot once, then check again<\/h3>\n
\n1.2. After logging in, open Task Manager<\/strong> (Ctrl + Shift + Esc) \u2192 Processes<\/strong>.
\n1.3. Watch CPU usage for a few minutes.
\n1.4. If the State Repository Service is only briefly active and CPU looks normal, it may have been a one-time glitch.<\/p>\n2. Restart the State Repository Service<\/h3>\n
services.msc<\/code>, press Enter.
\n2.2. Find State Repository Service<\/strong>.
\n2.3. Right-click it and click Restart<\/strong>. If Restart<\/strong> is greyed out, click Stop<\/strong>, wait a few seconds, and then click Start<\/strong>.
\n2.4. Check Task Manager to see if CPU usage drops.<\/p>\n3. Repair Microsoft Edge<\/h3>\n
\n3.2. Find Microsoft Edge<\/strong> and open Modify<\/strong> or Advanced options<\/strong>.
\n3.3. Use Repair<\/strong> first (keeps your data).
\n3.4. If high CPU persists and you\u2019re okay losing local Edge data, use Reset<\/strong> instead.<\/p>\n4. Run a quick system file check<\/h3>\n
\n4.2. Run:<\/p>\nsfc \/scannow\r\n<\/code><\/pre>\n
\n4.4. Reboot and see if CPU usage is back to normal.<\/p>\nPrerequisites<\/h2>\n
\n
\nMost fixes require administrative rights (services, PowerShell, system file repair).<\/li>\n
\nAt minimum, create a System Restore Point<\/strong> before doing advanced steps like re-registering built-in apps.<\/li>\n
\nSFC\/DISM scans and Windows updates can take a while. Avoid interrupting them.<\/li>\n
\nYou\u2019ll run a few commands, but everything in this guide is safe and reversible if you follow the steps.<\/li>\n<\/ol>\nStep-by-Step Guide to Fix State Repository Service High CPU<\/h2>\n
1. Confirm that State Repository Service is the culprit<\/h3>\n
\n1.2. On the Processes<\/strong> tab, sort by CPU<\/strong>.
\n1.3. Look for:<\/p>\n<\/a><\/p>\n\n
\n
2. Restart the State Repository Service cleanly<\/h3>\n
services.msc<\/code>, and press Enter.
\n2.2. In Services<\/strong>, scroll to State Repository Service<\/strong>.
\n2.3. Check Status<\/strong>:<\/p>\n<\/a><\/p>\n\n
\n2.5. If the service behaves after a restart, you can stop here. If the high CPU comes back, continue with the next fixes.<\/p>\n3. Repair corrupted system files (SFC + DISM)<\/h3>\n
\n
sfc \/scannow\r\n<\/code><\/pre>\n<\/li>\n\n
\n
DISM \/Online \/Cleanup-Image \/CheckHealth\r\nDISM \/Online \/Cleanup-Image \/ScanHealth\r\nDISM \/Online \/Cleanup-Image \/RestoreHealth\r\n<\/code><\/pre>\n<\/li>\n4. Repair or reset Microsoft Edge<\/h3>\n
<\/a><\/p>\n\n
\n
\n
\n
5. Reinstall or re-register built-in apps (advanced)<\/h3>\n
\n5.2. Run:<\/p>\nGet-AppxPackage -AllUsers | ForEach-Object {\r\n Add-AppxPackage -DisableDevelopmentMode -Register \"$($_.InstallLocation)\\AppXManifest.xml\"\r\n}\r\n<\/code><\/pre>\n
\n5.4. Reboot your PC.
\n5.5. Check CPU usage again during a typical workload (browsing, gaming, etc.).<\/p>\n6. Install the latest Windows updates<\/h3>\n