Cannot Create Soundtoys Version Root Folder At Soundtoys 5 Hot May 2026

Windows 10/11 includes a feature called Controlled Folder Access that blocks apps from writing to protected folders. It frequently interferes with audio software installers.

How to disable it:

Note: You do not need to disable your entire firewall. Only this specific feature causes the "cannot create root folder" error.

The error "cannot create SoundToys version root folder at SoundToys 5 hot" is almost never a flaw in SoundToys itself. It is a Windows permission safeguard that is overprotective. By following the steps above—specifically running as administrator, manually setting folder permissions, and disabling Controlled Folder Access—you will resolve this error in under five minutes.

SoundToys 5 is one of the most creative effect suites ever made. Do not let a permission hiccup stand between you and your mix. Take control of your system, apply the fix, and get back to making music. Windows 10/11 includes a feature called Controlled Folder

Quick Recap:

Now go install that hotfix and enjoy EchoBoy, Decapitator, and the rest. Happy producing.

Sources: SoundToys官方支持文档, Microsoft Technet (UAC & Controlled Folder Access), Gearspace community troubleshooting threads.

If the folder permissions are corrupted, a clean install is often the fastest fix. Note: You do not need to disable your entire firewall

This solves the problem for 70% of users.

Step-by-step:

Why this works: Running as admin bypasses the default write restrictions to Program Files. The installer can now freely create the "SoundToys version root folder."

Do not simply double-click the installer. Right-click is your friend. The error "cannot create SoundToys version root folder

Pro Tip: Even if you are the admin, Windows sometimes runs installers in user mode. Forcing admin rights gives the installer permission to create the root folder.

If a file named Soundtoys (no extension) or a corrupted folder exists at that path:

In some versions of the installer, the specific folder path simply does not exist, and the installer fails to create it on the fly. You can manually create the path to bypass this check.

This method manually creates the folder that the installer is failing to create, but places it in the correct user-accessible location and links it so the plugin can find it.