Uninstalled chrome and edge. Using Firefox with zero issues
Windows 10- Locks up "waiting for cache"
Window 10 was working very well until recently after upgrading to Windows Edge chrome (or at least the is the only event that I can associated to this issue) I am getting persistent OS stalls or "not responding" that affect all applications when running Edge. Common to see "waiting for cache" in lower left browser window when the the entire system stalls and stops responding. Common to see the cursor hour glass for 30 or more seconds before system and affected applications start to respond normally.
Windows for home | Windows 10 | Install and upgrade
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.
62 additional answers
Sort by: Most helpful
-
Anonymous
2020-06-05T17:16:40+00:00 Kevin,
I also have AMD mother board and SSD for my home drive and I am sure SSD is not the root issue here. That said, this debilitating "waiting for cache" issue was never observed while using several different browsers over several years with same hardware/drivers and WIN10 OS,, until, the very day I downloaded Edge chrome, so in my book Microsoft Edge Chrome is the root cause that developers need to figure out, not my system's Hardware or drivers.
Ok to your question-
I simply followed standard protocol for uninstalling applications in WIN10. Before uninstalling I did clear all caches created by both Google chrome and Edge Chrome and restarted the OS. Immediately after restart I uninstall Edge Chrome. When completed I restarted OS again and the Original version of Edge was still intact.
While I am familiar with registry tweaking I avoid it. If applications are properly installed than the uninstall should be easy and the reg should handle the changes without user intervention (under most common situations).
I wish I could say all this is a true resolution of this issue, but it has not, however the frequency of "waiting for cache" incidents has been dramatically reduced to rare, but there is still a bad taste in my mouth regarding Windows that maybe only a bite of the Apple will resolve.
-
Anonymous
2020-09-06T23:43:19+00:00 Let me elaborate a bit, because this resolved my problem! No waiting for cache or system lock-ups anymore.
I have a motherboard with BIOS (not UEFI) , an SSD and the Windows 10 is a fresh installation not an upgrade. I discovered, it was in IDE mode and I was willing to change it in order to test the results.
The moment I changed the mode I came face-to-face with the well known "BSOD" , so I followed the procedure below which had good results.
- Run Command Prompt as Admin
- Invoke a Safe Mode boot with the command: bcdedit /set {current} safeboot minimal
- Restart the PC and enter your BIOS during bootup.
- Change from IDE to AHCI mode then Save & Exit.
- Windows 10 will launch in Safe Mode.
- Right click the Window icon and select to run the Command Prompt in Admin mode from among the various options.
- Cancel Safe Mode booting with the command: bcdedit /deletevalue {current} safeboot
- Restart your PC once more and this time it will boot up normally but with AHCI mode activated.
-
Anonymous
2020-06-05T20:36:30+00:00 My hardware is also AMD - AMD Phenom(tm) II X6 1100T 3.31GHz with 16.0 GByte Ram. I just mention it because although it is a Chromium Edge software issue they may not have accounted for any subtle difference in the code needed to run with Intel/AMD processors.
-
Anonymous
2020-06-04T16:47:27+00:00 Very upset. I got the insider update back in January and had to revert because of the constant loss of using my computer. Now it was forced on me with the last few updates and I have switched to firefox. It doesn't work on my older AMD System with a SSD. I've tried so many trouble shooting steps to no avail. I miss the old edge that was streamlined and had quick load time and responses. Not a fan of chromium anything. Fix it Microsoft.
Edit:
I don't have an easy uninstall path for it. How are you uninstalling it without editing the registry?