What is causing the ‘Waiting for cache’ issue on Chrome?

We investigated this particular issue by looking at various user reports and the repair strategies that other affected users have used to get the issue resolved. From what we gathered, there are several common scenarios that will end up triggering this particular error message: If you’re looking for ways to resolve this annoying Google Chrome behavior, this article will provide you with several troubleshooting steps. Down below, you will discover a collection of methods that other users struggling to resolve the same problem have used. Since the ‘Waiting for cache’ issue has multiple potential culprits that might trigger this behavior, we advise you to follow the methods below in the order that they are presented. We ordered them by efficiency & severity, so one of them is bound to resolve the issue for your particular scenario.

Method 1: Disabling Write Cache on the SSD drive

Some users encountering this particular issue have reported that the issue was no longer occurring after they disabling the write cache on their SSD (Solid State Drive). While disabling the write cache on your SSD might seem like a quick fix, keep in mind that doing so might end up slowing your drive writes. This feature allows data to be initially stored in DRAM or SLC NAND and then written on the drive NAND, which ends up accelerating the writes considerably. If you are prepared to live with these repercussions for the sake of resolving the ‘Waiting for cache‘ error, follow the steps below to disable the write cache on your SSD drive: If you’re still encountering the issue after following the steps above or you’re looking for a different method that doesn’t involve disabling write caching, move down to the next one below. Note: If this method is not effective, remember to reverse engineer the steps above to re-enable the writing cache before starting with the next methods below.

Method 2: Creating a new user browser profile

Another fix that is sometimes effective in resolving the “Waiting on cache” issue on Google Chrome is to create a new user browser profile on Chrome. This will make you lose your user preferences and bookmarks, but you can easily import them to your new profile if this method ends up resolving the issue for you. Here’s what you need to do in order to create a new user browser profile on Google Chrome: If this method didn’t allow you to resolve the ‘Waiting on cache’ error, move down to the next method below.

Method 3: Reset Chrome’s browser settings to defaults

Several users have reported that the issue was no longer occurring after they reset their Chrome browser settings. As you can imagine, this will irreversibly reset all user preferences, startup items, and extensions, so only do it if you understand the consequences. Here’s how to rest Chrome’s browser settings to the default: If you’re still encountering the same ‘Waiting on cache’ issue, move down to the next method below.

Method 4: Using a ‘cache killer’ extension

If none of the methods above have managed to get the issue resolved, you’ll most likely be able to do it via an extension. Classic Cache Killer is a Chrome extension that will automatically clear your browser cache before loading a page. This will end up resolving the problem if the issue is caused by corrupted cache data. Here’s what you need to do to install Classic Cache Killer:

How to Fix iMessage or Facetime waiting for activationFix: Waiting on Another Installation or Update (Battle.net)Fix: Smite is Waiting for VerificationHow to Fix the Battlefield 3 ‘Waiting for Game to Exit’ Error on Windows? Fix  Google Chrome  Waiting for cache  - 52Fix  Google Chrome  Waiting for cache  - 97Fix  Google Chrome  Waiting for cache  - 45Fix  Google Chrome  Waiting for cache  - 60Fix  Google Chrome  Waiting for cache  - 70