Reset your default Windows library paths back to your physical disk ( C:\ ). 3. Clear "Phantom" Folders and Broken Symbolic Links
Under , ensure that everyone and your user account are set to Read & Write .
Ultimately, while this error requires a bit of technical effort to resolve, the creative power and sonic versatility of Soundtoys 5 are well worth the initial setup, putting you back in control of your productions. Reset your default Windows library paths back to
Click , restart your computer, and run the Soundtoys installer again. 2. Manually Create the Public Preset Root Directory
: Ensure the folder C:\Users\Public\Documents\Soundtoys\Soundtoys 5 is a physical folder on your primary drive. If it is a link, delete it and let the installer create a standard directory. 2. Reset the Windows Temp Folder Ultimately, while this error requires a bit of
Soundtoys uses your local temporary directory during initialization. If this path has been customized or corrupted, it breaks the installation routine. Press Windows Key + R to open the Run dialog box. Type sysdm.cpl and hit enter to open . Go to the Advanced tab and click on Environment Variables . Locate the TEMP and TMP user variables.
If you have used tools to move your "Documents" or "Public" folders to another drive using symbolic links, Soundtoys may fail to save presets or create its root folder. Manually Create the Public Preset Root Directory :
If the system's "Temp" folder has been moved to a different drive, it can disrupt the installation path.
Manually delete the Documents/Soundtoys folder.
Sometimes, an older version of the SoundToys 5 Link.exe is already running in the background—perhaps from a previous failed installation or an automatic update attempt. This running process can lock the target directory, preventing a new installer from accessing it.
Conclusion The “cannot create Soundtoys version root folder at Soundtoys 5 link” error usually stems from permissions, an invalid link target, or security software blocking folder creation. Systematically verifying the target path, correcting permissions, ensuring links point to accessible volumes, and running installers with elevated privileges resolves most cases. If these steps fail, a thorough clean reinstall and contacting Soundtoys support with diagnostic logs will get you back to producing sound quickly.