Every time you visit a website, your browser gathers basic files to make the page load faster on your next visit. You won’t notice it because the process runs smoothly in the background. Sometimes Chrome fails to load this stored cache and ends up freezing the page.
Before you consider switching to an alternative to Chrome, you can try to fix the problem yourself. We will share some tips to help you fix Chrome pending cache error. Let’s check them out.
1. Clear Chrome cache
Cache files stored by Chrome can get corrupted, which is why Chrome may encounter an error while loading them. You can try clearing the cache on Chrome to see if that helps. Here’s how.
Step 1: Launch Chrome and click on the three-dot menu in the upper right corner, select More tools and choose Clear browsing data.
Alternatively, you can also press the shortcut Ctrl + Shift + Del to quickly open the Clear Browsing Data panel.
2nd step: Use the Time range option to select All the time from the drop-down menu. Check the boxes that say “Cookies and other site data” and “Cached images and files”.
Finally, hit the Clear Data button.
Now relaunch Google Chrome and see if the issue is resolved.
2. Prevent Chrome from writing the cache
For the most part, the wait for cache error in Chrome only occurs when the browser cannot create or access the cache files on your PC. And the problem is very prominent among PCs which use Solid State Drive (SSD) to write cache. In such scenarios, you can prevent your PC from storing cache data to see if that helps. Here’s how.
Step 1: Click on the search tool in the taskbar, type Device Manager, and press Enter.
2nd step: In the Device Manager window, expand Disk Drives, double-click your SSD drive to open the properties.
If you have multiple SSDs on your PC, choose the one you have Google Chrome installed on.
Step 3: In the Properties window, go to the Policies tab and uncheck the “Enable write caching on device” checkbox. Finally, click on OK.
Restart your PC for the changes to take effect and Chrome should work fine.
3. Create a new user profile
Another potential solution for Chrome waiting for a cache error is to create a new user profile. This should launch Chrome with its default settings preferences, which might fix the error.
Follow the steps below to create a new user profile in Chrome.
Step 1: Click the current profile icon in the upper right corner. Under Other profiles, click the Add button.
2nd step: Then select the option “Continue without an account”.
Step 3: Now write a suitable name and choose a color scheme for your profile. Then click Done to continue.
This should restart Chrome with your new profile. Now go ahead and see if the problem is resolved. You can sign in with your Google account to retrieve your old favorites and set preferences if so.
4. Reset Google Chrome
You may need to reset Chrome to its default settings to resolve the issue. It is important to know that resetting Chrome will remove all extensions, cache, and settings preferences from Chrome.
To reset Chrome, type chrome: // settings / reset in the address bar at the top and press Enter. Under “Reset and clean”, click “Restore settings to their original defaults”.
In the confirmation pop-up window, click Reset settings to confirm.
5. Reinstall Chrome
If the problem persists even after resetting Chrome, you will need to uninstall and reinstall it. In this way, you can get rid of the old data associated with Chrome and start from scratch. Additionally, you will also update Chrome in the process. If you decide to go for this option, first make sure that all your important data is synced with your Google account.
Step 1: Press Windows key + I to launch the Settings app and use the left pane to go to the Apps tab. Now click on Apps and Features.
2nd step: Scroll down to find Google Chrome. Click on the three-dot menu and select the Uninstall option.
Now restart your PC and reinstall Google Chrome.
Also on Guiding Tech
The wait is over
Cache is a crucial part of any web browser. Without it, web browsers cannot achieve fast load times. In most cases, the problem occurs due to corrupted cache data or incorrectly configured settings. Rest assured, once you have gone through the solutions above, the error should be resolved.
Last updated on November 20, 2021
The above article may contain affiliate links that help support Guiding Tech. However, this does not affect our editorial integrity. The content remains impartial and authentic.