Server Status Due to the high demand service might be impaired temporarily. We are sorry for the inconveniences.
: A pop-up asks for one-time admin permission to create the required directories. Path Selector
Ensure you are running the Soundtoys 5 installer with administrative privileges. Right-click the installer and select "Run as administrator" to bypass potential folder creation restrictions.
Soundtoys V5 Preset location, presets not saving and hardlinks
support moving the preset root folder via symbolic or hard links. If you’ve tried to save space by "aliasing" the folder to another drive, it can cause this exact creation error. Default Root Folder Locations The plugin expects to find its "root" here: SoundToys - Problem creating User folder cannot create soundtoys version root folder at soundtoys 5
This happens because the installer or the plugin itself lacks the "authority" to create the necessary directories for presets and settings. How to Fix the Issue
Jack tried to select a different folder, but every time he clicked "OK," the same error message popped up. He tried restarting the installer, but that didn't work either. He even tried running the installer as an administrator, but still, nothing seemed to work.
If you try to delete the folders in Step 2 and get a "Permission Denied" error or a password prompt that doesn't work: : A pop-up asks for one-time admin permission
The installer may be trying to overwrite a corrupted or user-permission-blocked folder.
If your C: drive has permission issues, install to a secondary drive.
: Some security software may block the plugin from creating new folders; try adding your DAW to your antivirus safe list Avoid Symbolic Links Soundtoys V5 Preset location, presets not saving and
Soundtoys V5 Preset location, presets not saving and hardlinks
Select TEMP , click , and reset the variable value to: %USERPROFILE%\AppData\Local\Temp
Some users in Reaper found a practical workaround for crashes during rendering, which may be triggered by the same folder creation error. Instead of fixing the root cause, they create a dedicated rendering project: save a copy of your main project with , render from that copy, and keep your original project untouched. This can bypass the issue.
