Ramdisk Junction Possible Bug

[data2318]

I use the function feature to point Google Chrome's cache folder "C:\Users\xxxxx\AppData\Local\Google\Chrome\User Data\Default\Cache" to Ramdisk, sometimes if Google Chrome gets updated the junction will no longer be there, it was overwritten...
I think a good program in 2016 is supposed to check for the validity of the junction itself every-time computer restarts, automatically make a new symbolic if it's broken, otherwise it is pointless.

[Support]

The junction point is a feature provided by NTFS file system. Primo Ramdisk just gives a simple way to create/delete a junction point. There are also many tools like mklink.exe that can operate junction points. So when a user deletes a junction point by another tool, Primo Ramdisk cannot know if this junction point was deleted intentionally or unintentionally and it is not reasonable to automatically restore the junction point in Primo Ramdisk. Besides, many users don't like a program running in the background to monitor the status of junction points.
But thank you for the feedback! We'll think about this problem.

[InquiringMind]

... sometimes if Google Chrome gets updated the junction will no longer be there, it was overwritten...

This suggests that the problem lies with Chrome's updates overwriting the junction with a new folder rather than with Primo Ramdisk.

You may be able to avoid this by altering NTFS permissions on the link (setting Delete to Deny) to stop future updates from removing it, but this is probably an issue you should raise with Google themselves.

Chrome also has a command-line option for changing its cache folder so you may be able to use this to use a Ramdisk folder directly. See How To Change Google Chrome’s Cache Location And Size for details.