Uninstalled chrome and edge. Using Firefox with zero issues
Windows 10- Locks up "waiting for cache"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
Answer accepted by question author
Anonymous
62 additional answers
Sort by: Oldest
-
Anonymous
2020-08-08T07:51:33+00:00 I had to remove Edge Chromium as well. Was periodically freezing and Google Chrome kept saying "waiting for cache" (Googling that said to turn off cache on the ssd's, didn't help)
And when I removed Edge Chromium, Google Chrome starting freezing like Edge did.
Now I run Firefox without an issue.
Only thing similar to other posts is I have an AMD cpu and SDD's.
I have also edited my registry to prevent Edge Chromium being re-installed without my permission.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2020-08-08T15:27:47+00:00 Don't know if it was because of updates, but no issues in the past two weeks. Everything has been running fine and I've been using Edge and MWB
-
Anonymous
2020-08-08T17:10:51+00:00 Update observation issue with "waiting for Cache"
- If I start my PC session and exclusively use only Google Chrome, I don't encounter this issue.
- If shut down Google Chrome and I launch Edge Chrome, the issue immediately occurs with annoying frequently. The Win-10 Home OS + any apps that are currently running lock up until the "Waiting for Cache" has cleared.
- If I have both Google Chrome and Edge Chrome running concurrently the issue occurs frequently and affects both browsers.
- If I shut down Google Chrome and continue using Edge Chrome (*without restarting Win-10 OS) the issue continues to occur frequently.
- If I shut down Edge Chrome and keep using Google Chrome (* again without restarting Win-10 OS), the issue continues to occur frequently.
- If I shut down both Google Chrome and Edge Chrome and then perform a restart Win10-OS, then launch only Google Chrome, I don't encounter this issue.
So what does this little DYI test tell me? There is something embedding in the Win Edge Chrome browser code that seems to cause this issue and it also affects Google Chrome (some shared files?) until there is a restart and fresh install of Win-10 OS. I hope there is some computer expert out there that can use this observation to help diagnose a cure (it is not COVID-19). I think the source is MS Edge Chrome.