Clean install of Fall Creators Update and State Repository Service

Just finished another clean install of 1709 on the same machine, this time leaving the Ethernet cable unplugged from start to finish. The problematic behavior is gone.

I have the same issue like OP. MS Edge is unusable now as it freezes everytime I click on a link. I did a clean install with an ethernet cable plugged in.
State Repository Service always makes cpu 100% and I have to restart pc in order to get rid of it. I think State Repository Service is related to MS store.
I am not gonna do a clearn install now because it took me 8 hours to get all my software installed.

What changes are made to the StateRepository-Machine.srd file if the Ethernet cable is left plugged in during clean install that causes the cpu to max at 100%?

Found the solution!!!

1. Press Windows Key + R on your keyboard.
2. Key in PowerShell and hit Enter.
3. Right click on the PowerShell icon on the taskbar and select Run as Administrator.
4. Now paste the following command in the Administrator: Windows PowerShell window and press Enter key:Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Source: FIX Windows 10 taskbar not working - Microsoft Community

DEVOPS said:

Just finished another clean install of 1709 on the same machine, this time leaving the Ethernet cable unplugged from start to finish. The problematic behavior is gone.

Confirmed i just clean install with out the internet cable my problem is gone...
i did install 4 times my windows today because of that problem of hight cpu from State Repository Service

Thanks

coch said:

Thanks a lot, I confirm this works for me, despite the powershell command throwing an error towards the end of it's routine (it processes many packages and I suspect the error only affects one of them).

However, do you have any insight as to why a fix for "Taskbar not working" as per your link would fix anything in this case given that this is a different problem?

I'm also trying to isolate the problem further and see if there's a way to fix just the problematic package as opposed to processing all packages with this powershell command.

Well, surprise, surprise, this is no longer working for me after reformatting and re-installing Windows 10.
So it must have been a combination of this fix, and whatever else I had previously tried (prior to reformatting) for fixing the issue. none of what I had previously tried had worked, but I suspect it may need a number of different things.
Tried to run the command several times, no errors were seen and the command completes its work, but issue still not resolved.

coch said:

Well, surprise, surprise, this is no longer working for me after reformatting and re-installing Windows 10.
So it must have been a combination of this fix, and whatever else I had previously tried (prior to reformatting) for fixing the issue. none of what I had previously tried had worked, but I suspect it may need a number of different things.
Tried to run the command several times, no errors were seen and the command completes its work, but the issue still not resolved.

Have you tried the clean reformat without an internet connection?
I couldn't use the powershell command at first because I turned off some of the services (messing with registry editor). If you don't do a clean format, the OS probably still keep your settings.

amiracle2 said:

Have you tried the clean reformat without an internet connection?
I couldn't use the powershell command at first because I turned off some of the services (messing with registry editor). If you don't do a clean format, the OS probably still keep your settings.

Yes, clean install is what I always do: Boot from Windows install media (USB drive), reformat target drive, install Windows from scratch.


Sadly, I tried without the ethernet cable connected this time and it didn't change a thing. I'm getting the same problem.
The powershell script still does not fix the issue either. Not sure why the powershell trick worked the first time I used it.

coch said:

Yes, clean install is what I always do: Boot from Windows install media (USB drive), reformat target drive, install Windows from scratch.


Sadly, I tried without the ethernet cable connected this time and it didn't change a thing. I'm getting the same problem.
The powershell script still does not fix the issue either. Not sure why the powershell trick worked the first time I used it.

weird, I start to think maybe it's your hard disk problem. try to use "chkdsk /r" in command prompt to check your hard disk