High CPU usage in state repository service after clean install of Fall Creators Update while online via ethernet

Anonymous
2017-10-21T09:08:14+00:00

Why do apps including Microsoft Edge and Settings freeze when clicking on hyperlinks and make CPU usage reach 100% on state repository service after a totally clean install including deleting all partitions of the Fall Creators Update while online via Ethernet.  The only fix is to reinstall the ISO media with the Ethernet cable unplugged and wait until the OOBE setup asks for the region before reconnecting the Ethernet cable.  I have to physically unplug the Ethernet cable from the router to prevent it from accessing the internet during the first just a moment phase of the OOBE setup before the region setup.

Moved from: (Windows / Windows 10 / Install, upgrade, & activate)

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

45 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-11-24T01:02:20+00:00

    Didn't help me at all :(

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-11-08T20:50:23+00:00

    After workaround with disabling "Open site in Apps" in Edge settings, I still observe this issue, for example, after clicking href in Skype message. Still the same process "State bla-bla-bla" loads my CPU. It is very-very-very annoying bug, really.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-11-07T22:15:57+00:00

    Or, reinstall Windows with Ethernet unplugged - it works for me.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-11-05T14:50:23+00:00

    @AlexLouka_508

    Thanks so much! I been pulling my hair out since Installed fresh..

    Any external link i.e help buttons, URL's in chat or hyperlink takes like 20 seconds to open in any browser and it chows the CPU.

    What's strange is that chrome was my default browser and when i repaired and reset MS Edge, it worked flawlessly.

    Whoever is reading this, just try this.

    Was this answer helpful?

    0 comments No comments