Browser cache location reverts from RAM disk back to HDD

The Cache Relocator setting for my Google Chrome is prone to reverting to HDD rather than staying on the RAM disk after a reboot. How can I make this setting stay semi-permanent?

I use Primo RAM disk with image enabled, and after a reboot the RAM disk still exists.

It looks like occasionally the new versions of Chrome/Edge delete the symbolic link and re-create a regular cache directory. It is unclear why they do that; maybe because their cache format changes from version to version.

One way to deal with this would be to run the Cache Relocator periodically, to check if the redirection is in place.

Alternatively, you can edit the shortcut that you use for opening Chrome/Edge and add the --disk-cache-dir parameter. For example, your shortcut can look like this:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir=R:\Cache

where R:\Cache is the browser cache folder on the RAM disk.

This should always use the specified location.

It looks like there is now a similar problem with Firefox.

SoftPerfect Cache Relocator is a great little program, however it is not relocating but duplicating Firefox cache. Basically there is cache in the old location on Disk C, and in the intended RAM drive location.

Maybe Firefox has changed its settings in the latest versions, but it is clearly not allowing the cache to simply completely relocate to a RAM drive.

Cache Relocator works by creating a symbolic link that makes Firefox use a different location for its cache. It is possible that you mistake the symlink for a real cache folder. Its icon can look identical to that of a folder, and it will be in the original cache location on your C drive. But there is no reason for the cache data to be "duplicated". It is possible it reverted to the hard drive, but there shouldn't be two copies of it. Here is a more detailed guide on symbolic links.

However, if Firefox now detects that its cache is a symbolic link and decides to delete it, there is unfortunately nothing we can do about it.

Hello,
I use edge 03/2025 and i saw that original C:\ cache folder was redirected to the new location (new cache created). Symlink is ok, but there is still the original cache that is working. So it seems to be 2 caches working now.

Hi @calvin4242,

I use Edge as well and there are two things that I did in order to make the cache work properly. The first is similar to what Ann mentions in this thread about Chrome browser. You need to change your shortcut to read (where x: is your RAM disk):

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --user-data-dir="x:\User Data"

But you also need to add a registry entry which tells the app to use the cache upon launch. For the .reg file:

[HKEY_CLASSES_ROOT\MSEdgeHTM\shell\open\command]
@="\"C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe\" --user-data-dir=\"x:\\User Data\" --single-argument %1"

This prevents the browser from reverting to the default cache location upon launch. Unfortunately this needs to be executed after every browser version update as this registry entry will be removed. These steps also assume you have used cacherelocator.exe to SymLink your Edge browser first.

Hope this helps!