The installer always defaults to my system disk (C without giving me the chance to change it whenever I install a release from team VR, and occasionally R2R as well. Even though I have set my D: drive as the default installation location for Windows, these installers still insist on installing to C:, which is now a problem because I am out of space.

Does anyone have a solution or a way to get around this problem?

 

Its so annoying but the only way round it for me is to symlink lesser used software to d drive, delete to free up space then install VR (which you can then symlink too)

 

reformat windows and get a bigger hard drive

 

Yeap use R2R , TCD , Flare and Moca . Never use anything from VR , always revisions after revisions after revisions .... , always problems , uninstall issues and personally i dont like their internet page and the country they are from .

 

You can't change the behaviour of the installers yourself and VR is a bit lazy hwen it comes to installers.
But just move the installation directory to the desired drive an place a hardlink to the position where VR has installed it originally.
Problem solved.


P.S.: If you are not used to make hardlinks with windows command prompt, there is a utility that makes it easy. Link shell extension (LSE):
https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
You just click right "Set Link Source" on the directory you moved (e.g. "D:\Audiomodern"), and then paste it to the directory where you moved it from (most of the time "C:\Program files"). A link is made reading "C:\Program files\Audiomodern"
This makes the OS thinks think, everything is on the C: drive as before, while it is actually on the D: drive (or any other you like, even network places).

Get used to hardlinks and it will save you hours and hours.

 

Last edited: Aug 28, 2023

You can't save space on a drive by using hardlink(s). Hard link cannot link to a file that is on a different partition, volume or drive.

 

Totally true. Unfortunately, they have no love for beautiful setups.

As a workaround, you could e.g. 1) run the setup in a sandbox and pull the files out of there. OR b) In many cases, it is also sufficient to simply run the installation and move the installation directory elsewhere. Afterwards you simply set a new link to the EXE. Has the advantage that registry entries - if any - would be correct.