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: Oldest
-
Anonymous
2020-07-19T19:17:44+00:00 After starting this thread some time ago here is my updated. After uninstalling Edge Chrome several months ago the issue "waiting for Cache" also was resolved. I continued to use Google Chrome without any issues and could also use the original Windows Edge without any issue. That said I have been monitoring this thread and would add that I don't have any 3rd party malware apps installed (except for Win Security aka defender). So I can rule that out in my case.
Now I am p'd off again, because MS pushed out yet another Tue. update that re-installed Edge Chrome (and if I understand it correctly also total disabled Original Edge).
After the unwanted change, I refused to launch Edge Chrome and continued to use Google Chrome without any issue related to "waiting for cache" or Window OS and other running apps locking up.
Yesterday I accidentally launched Edge Chrome and when I decided to proceed using the browser (sucker) and visited some commonly used websites guess what? yep, all apps that were running and Win OS stopped cold "Waiting for Cache" for at lease a full minute before it recovered and I could immediately shut down and restart system.
I continue to only use Google Chrome hoping Edge chrome will not conflict again as long as I don't run it, but I won't know for several days of heavy use.
Win 10 Home 2004 build 19041.388
Root Drive Samsung SSD 840 EVO 120GB ATA (Win Driver Ver. 10.0.19041.1)
I am convinced that the issue must be related to Edge Chrome platform build, or maybe Windows Driver for SSD is
-
Anonymous
2020-07-19T19:53:42+00:00 I do not have Malwarebytes so that is not my issue. I have updated my computer from Hard drives to SSD's. I ran a program called Crucial Storage Executive and it suggested I should use ACHI. I didn't know what this was or how to change it but have since found the setting in the bios and changed it from IDE to ACHI and then on boot up it couldn't find windows which apparently is normal. So I had to reinstall windows to cater for this new setting in the bios. Crucial Storage Executive also suggested disabling 8.3 file name creation which I did by going to elevated cmd prompt and typing fsutil.exe behavior set disable8dot3 1 and then press enter. I don't know if any of this relates to the Chromium Edge problem but at least these are two things to rule out. I have tried Chromium Edge since making all these changes and not had any problems but then I'm not using it all the time because its too much hassle when the system locks up. Therefore I am continuing to use FireFox as my main browser without any issues.
-
Anonymous
2020-07-21T13:26:13+00:00 I have tried everything that is noted for my Windows 10 Edge regarding constantly getting processing request, waiting for cache and a number of others for Facebook. This started happening over a month or so ago after they installed the latest update. Several times during the day, I click on control/shift/delete and clear the cache, etc. I also go into settings, system, storage and delete some of the files. This also does nothing in stopping those pop ups. I will never, ever allow another update on my laptop again as they are all bad and cause problems. Good thing I'm retired!
-
Anonymous
2020-07-28T19:21:53+00:00 For me i use this solution.
remove the last update via the command.
after that the old stock edge is back. :) and no problems with WAITING for cache.
(you need to stop microsoft update service he will come back next update)