New
#21
I tried this but that still didn't work.
Same here, nothing works consistently.
If I reformat and reinstall Windows, none of the fixes will work right away. But eventually the Powershell script will work, usually the next day.
I'm starting to think some time need to pass and Windows automatically fixes something.
I'm saying that because this week, I've been running the Powershell script posted above, as well as a few variants found elsewhere and nothing worked, even if I ran it dozens of times in a row, using different ways for running it (directly running script saved as a ps1 file, from a powershell window, fro a cmd window, from a batch file, from powershell ISE, etc...)
However, after a night sleep, or after coming back from work (more than 8 hours had passed), running the script fixes the issue, the first time that I run it.
I'll try to test this further to confirm, if that's the case, this could (maybe) indicate that Windows runs a scheduled task at some point which cleans up some mess or fixes something yet unidentified, and this may be needed in conjunction to running the Powershell script.
I've downloaded the ISO file of Windows 10 FCU using Media Creation Tool on my Hard Disk & transferred it to a USB drive. I've also updated the Windows 10 version to FCU on the Hard Disk. Now I want to Clean Install from the USB drive. But whenever I try I get the error message, "Sorry, Unable to Mount the file".
Create Bootable USB Flash Drive to Install Windows 10 Installation Upgrade Tutorials
Just copying an iso file to a USB drive (if that's what you've done) doesn't make it automatically bootable. It's just a data disk with a file on it.
By contrast, burning such an iso file to a DVD does create a bootable DVD.
To add to my previous post Clean install of Fall Creators Update and State Repository Service
this appears to be the case.
I reformatted and re-installed Windows and this time didn't run any script, attempt any fix, etc. I just let time pass, putting the PC to sleep at night, light browsing, etc... and 24 to 36 hours later the issue has disappeared.
Still investigating to determine what does Window do to eventually fix it, if I can identify that I could possibly accelerate the process and not have to wait over 24 hours.
I am not gonna do a clearn install now because it took me 8 hours to get all my software installed.
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.