Windows 10: Clean install of Fall Creators Update and State Repository Service

FWIW, I tried all these fixes and nothing worked. It feels like the "state repository service" has some relationship to the firewall or defender, which causes the hanging when you click on a weblink. Tried reinstalling Fall Creators several times and several different ways. Didn't fix the behavior.

I was able to find the may 2017 windows 10 release, installed that, then let it upgrade itself and all is good. It has other problems, but is completely usable

 

After testing many more times (always 1709 clean installs), as I wrote in my previous post this issue always goes away by itself for me. My previous observation was that the issue resolved by itself 24 to 36 hours after installing Windows 10 but it seems like only 8 to 20 hours are enough after all.

I can reproduce this every time. I reproduced at least a dozen times since my previous post, and it never behaved in a different way.

I have all auto-updates turned off (Windows 10 Pro), including drivers, etc... so what Windows does to fix the problem isn't due to installing updates.
To me it looks like after installing Windows 10, Windows needs some time to "settle" during which it does other operations, possibly meaning that after a clean install, even when you boot into Windows it may not be fully installed. That's just my guess and I don't know that for sure, but certainly looks like it since the problem is present after clean install, but goes away after several hours, even without installing any driver, any update, any software, or changing any configuration in Windows.

Anyone knows what post-install operations Windows does? Anyone with knowledge/insight about the Windows install routine? I'd be very curious to see if we can narrow down to whatever Windows does at some point post-install in order to fix this problem. Obviously, with the goal of being able to trigger the change or issue a command earlier and not having to wait for many hours for the change to happen.

 

Also ran into this problem and associated frustrations; like others reinstalling/repairing/updating made no difference. Was resigned to wait out the 8-20 hours after seeing your encouraging post. On a whim opted to do a comprehensive disk clean up using using the integrated tool including nearly everything else listed under "Clean up system files". The Windows update reconciliation took an inordinate amount of time given the fresh install status. However, when complete the system responded as normal. Elapsed time <1 hour. Might have been coincidental but thought I would post findings (err...1 data point) here as a possible aid to others.

 

Aha! you might be on to something. I'll reformat/clean install again tonight or tomorrow and test this out.


EDIT:
Ok I was too curious and had to try right now, and unfortunately this didn't help for me.
Just to make sure, you used the "Disk Cleanup" utility that it finds when typing disk cleanup in the start menu right? Then check off every box in the cleaner and run this?

This is what I did and it didn't help.
I also tried another cleanup, in case this is the one you referred to: Under "Storage" in Windows settings, you have the option to free up space.

I tried that one too, rebooted, and problem still exists.
Same if I manually start Automatic Maintenance from the control panel + reboot, issue still present.

So it might have been your Windows Update process that changed something. I may have to try that. I always apply updates via pre-downloaded .msu files (via batch file of my own), so Windows updates finds nothing, but maybe I ought to try without the .msu updating and let Windows Update do it's thing.

 

Sorry it didn't work out for you. As noted in my original post I might have been the beneficiary of fortuitous timing although the 'wait' period in my case was about an hour vs 8-20 hours suggested in your post. I didn't take any 'normal' OTA Windows updates following the initial 1709 install as prior attempts suggested this action provided no relief. So the glitch remains a mystery for now as I have no immediate need to rebuild any Win 10 machines. A Microsoft engineer somewhere knows why but he/she isn't talking. Hopefully a 'fix' will be quietly rolled into 1803.

 

TL;DR: PowerShell fix worked for me after 24 hours.
Had the same with a fresh 1709 install, tried the powershell command multiple times to no avail ( it would usually give errors in the end that it is unable to write to file because it is used by another process - usually Edge and/or Photos ).
Also tried to disable the state repository service ( msconfig wouldn't let me disable it ), tried running powershell command in safe mode, tried repair/reset Edge in "Apps & Features" menu, and rebooting lots of times.
Then, the next day, approx 20-24 hours after installation, I ran the powershell command again right after reboot and followed by another reboot.
This time, it ran through without any red errors, and problem was gone.

Thanks to those who reported and contributed to this thread, you can count me as another example of "fixed after xx hours" ( even though I did run the command to fix it in the end ).

powershell command
Code: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}[/quote]