Cannot Create Soundtoys Version Root Folder At - Soundtoys 5 Link

SoundToys provides an official uninstaller tool that removes all traces of previous installations. This is the nuclear option but highly effective.

Corrupted disk sectors can prevent folder creation.

Open Command Prompt as Administrator:

chkdsk C: /f

Say Y to schedule on reboot → restart → let it run.

This solves the issue 80% of the time.

Why this works: Running as admin gives the installer unrestricted access to create folders in ProgramData and register system components.

Follow these in order. Most users stop at Step 1.

Despite you being the admin of your computer, many Windows applications do not run with full system privileges by default. The SoundToys installer needs to write to the ProgramData folder (a protected system directory). If the installer isn't "Run as Administrator," Windows may block the folder creation.

Background software (shell extensions, security tools) can interfere. SoundToys provides an official uninstaller tool that removes

SoundToys’ installer writes several files in rapid succession. Some overzealous antivirus programs (including Windows Defender’s “Controlled Folder Access”) see this as suspicious ransomware-like behavior and block the folder creation.

Encountering the message “cannot create Soundtoys version root folder at Soundtoys 5 link” is a frustrating interruption for any music producer trying to install, update, or run Soundtoys 5. This issue typically points to a permissions, path, or file-system conflict that prevents the installer or application from creating the required directory structure. Understanding the likely causes, diagnostic steps, and fixes helps restore your workflow quickly and reduces the chance of recurrence.

Causes and context

Diagnosis — step-by-step

  • Inspect links/aliases: If a symbolic link, alias, or junction is involved, verify it resolves to an accessible, mounted location and not to a read-only or remote drive.
  • Check disk health/format: Ensure the target volume is mounted, has free space, and is formatted with a suitable filesystem (NTFS on Windows, APFS/HFS+ on macOS).
  • Temporarily disable antivirus/security software: Briefly turn off or whitelist the Soundtoys installer/application and retry, then re-enable protections afterward.
  • Run installer or DAW with elevated privileges:
  • Look for leftover files/old versions: Remove remnants of prior Soundtoys installations (backup first). On Windows, check Program Files and registry entries; on macOS, check /Library/Audio/Plug-Ins and ~/Library/Preferences.
  • Consult logs: Installer logs, DAW plugin-scanner logs, or system logs may show precise filesystem errors (access denied, path not found, I/O error).
  • Try an alternative location: If permitted by the installer, choose a different install path on the primary drive (e.g., inside your user’s Documents folder) to isolate whether it’s a path/permission problem.

    • Fixes — prioritized actionable steps

  • Free up or reformat drives: Move installation to an NTFS/APFS volume. Avoid FAT32 or exFAT for plugin libraries that require permission features.
  • Whitelist Soundtoys in security software: Add installer/app to exclusions, or temporarily disable shields while installing.
  • Clean reinstall: Uninstall Soundtoys, delete leftover folders and preference files, restart the machine, then reinstall the latest Soundtoys 5 installer from the official source.
  • Update host/DAW: Ensure your DAW and its plugin-scanner are up to date; sometimes newer versions handle plugin folders and permissions better.
  • Contact Soundtoys support with logs: If the issue persists, collect installer/console logs and a brief description of attempted fixes and send to Soundtoys support for targeted help.

    • Preventive recommendations

    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.