Home » How To » Reduce State Repository Service High CPU Usage

Reduce State Repository Service High CPU Usage

Is the State Repository service causing high CPU usage? Follow these steps to fix the State Repository Service high CPU usage problem.

Recently, one of my friends encountered a strange problem where the State Repository service’s CPU usage is pretty high. In fact, from time to time, the State Repository service CPU usage is touching 95 to 99 percent. In his case, the problem occurred after a sudden system crash and restart. As you can guess, high CPU usage by a single process can severally slow down the system and make even the simplest of tasks slow and unbearable.

Thankfully, it is really easy to fix the State Repository Service’s high CPU usage. Follow the below steps to reduce State Repository Service’s high CPU usage.

Jump to:

  1. What is the State Repository Service?
  2. Restart the State Repository Service
  3. Reset all Microsoft Store apps

What is State Repository Service?

State Repository Service is a system service, and Windows automatically starts and stops it as and when needed. Windows uses the State Repository service to render some browser components in the background and keep track of the browsing sessions and other activities. This information is regularly used to sync and restore browsing sessions.

Wherever the default browser engine is invoked or used, Windows automatically uses the State Repository service. For example, Windows uses this service to track the browsing session when you open the Edge browser. If you open the Microsoft Store, Windows uses the State Repositor Service to render specific browser components and keep track of your activity. The same is true for any other apps or programs that use the default browser engine.

1. Restart the State Repository Service

When the State Repository Service is causing high CPU usage, restarting it will often fix the issue. Under certain circumstances, the service might get stuck on a specific task which in turn causes high CPU usage. When you restart the service, the process is forcefully unhooked, solving the problem. Here is how to restart the State Repository Service.

  1. Search for “services.msc” in the Start menu
  2. Click on the “Services” result to open it.
  3. Find “State Repository Service.”
  4. Right-click on the service.
  5. Select the “Restart” option.

First, we need to open the Windows Services tool. To do that, search for “Services” in the Start menu or execute the “services.msc” command in the Run dialog box (Win + R). After opening the Services tool, find the “State Repository Service,” right-click on it, and select the “Restart” option.

restart state repository service to fix high cpu usage

As soon as you click the option, Windows will restart the service. Once restarted, you will no longer see high CPU usage by the State Repository Service.

2. Reset all Microsoft Store apps

As I said earlier, Microsoft Store and other Store apps use the built-in browser functionality to render components. When an app misbehaves, it can sometimes cause the State Repository Service to use the CPU overly. In that case, you have to reset Microsoft Store apps. Thankfully, it is straightforward to do using a single-line PowerShell command.

First, right-click on the Start menu and select the “Windows PowerShell (Admin)” option. This action will open the elevated PowerShell window.

open PowerShell as admin

Here, paste the below command in the PowerShell window and press the Enter button on your keyboard to execute it. As soon as you run the command, Windows 10 will reinstall or reset all store apps.

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Once done, you will no longer see State Repository Service high CPU usage.

That is all. It is that simple to reduce State Repository Service CPU usage.

I hope that helps.

If you are stuck or need some help, comment below, and I will try to help as much as possible.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top