Windows 10: Problems downloading with Edge

I tried the in-place upgrade. Didn't help. The problem is moving your user folders using sysprep.

It did work on legacy Windows versions (not that Edge existed of course) but sysprep doesn't work reliably on 10240.

If you have existing accouts then sysprep corrupts your Edge profile in %localappdata%/Packages and I can't find a way to replace (even parts of it) that works. I've tried replacing some or all from a new account but it didn't work. The only solution that worked for me is to delete the existing account and make a new one.

All new accounts are fine. Any that existed before moving with sysprep have this issue.

 

The next step would be the obvious for simply nuking the present account you are having the problem with and see if creating the same account only brand new will solve the problem. That makes a bit more sense then going with a repair install of 10 when this is only seen with one account.

Here I never even use Sysprep but simply slap a clean install of any version of Windows on when and if it should become buggy! Sysprep is something you tend to use more for server application as well as corporate deployment over the home desktop to begin with. The very top of one blog seen at The WIndows Club quoted here for example explains how that works. How to use Sysprep Tool in Windows 10 / 8 / 7

The MS Answers as well as TechNet and MSDN forums have a number of threads regarding problems withe Sysprep on the TP builds as well as on the present RTM.

 

I already marked this solved with the solution, thanks anyways.

 

This problem re-occurred and at the same time Edge started freezing when opening some new pages.

In case it is of use to someone else it can be resolved by deleting the following file (instead of creating new user):

%USERPROFILE%\Appdata\Local\Microsoft\Windows\INetCache\counters.dat

As counters.dat is locked need to change the value of the key Cache at "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" to something else, reboot, delete the INetCache folder and then change the key back. The folder is recreated automatically in the location specified on the key.

 

Thank you! Thank you! Thank you!

I was having the same problem you posted in the original message, evidently because I changed a user's username and folder name. It's weird that this would cause that problem, but it's solved now thanks to you!!!

Incidentally, I logged out of the account I was having problems with, logged into my account and deleted the folder from there rather than messing with the registry. It work just as well.

Again, thank you! *Smile

 

You are right - deleting it is easier. It seems to break for me every few weeks and I'm not sure what I do to cause it. Deleting the INetCache folder from another account is quick and easy fix.

 

@lx07
Just wanted to post to say "Thank you" as well. I had this problem today and it drove me nuts till I found your post!

@DesertRambler
Handy approach you have to the problem as well! Kudos

 

Very interesting.

 

Nice read.

 

I have had similar issues, but not fixed by the INETCACHE removal. As I had a full clone backup on another disk in the desktop, (taken prior to the problem state)I decided to try the MS Support route, via the CHAT and remote support. Interestingly, the support tech used this program:<br>Windows Repair (All In One) Download <br>It did a LOT of stuff (he ticked just a few items in the "tool set" main GUI, related to EDGE and apps) - and it took over an hour (he disconnected once it was running). It needed a restart, and although it did not do any other apps or system damage, it actually made the EDGE browser worse (in that it only stayed active for a few seconds, then crashed and exited).<br><br>For some problems, that (AIO "All In One") fixer might work for specific problems, but as MS level are a continuous moving target, I would advise that anyone contemplating using it, has a full backup, or ideally, a full bootable clone from a known working state before using it, AND ensure you have the latest version (always check for updates from the AIO site before using it).