Hi!
I'm getting this window error when opening a project:



AFAIK, this is related to a plugin built using SynthEdit. Which, from the list of plugins used on the project, could be BIONIC SUPA DELAY - ED 1_1.

But the thing is that I have really no clue of what to do about this situation. Should I do something about it or leave it alone? (Although something tells me the second option is not right).

 

System Requirements --> www.interruptor.ch/vst_donationware.shtml

32 bit Plugins:
C:\Program Files (x86)\VSTPlugins

 

Last edited: Sep 13, 2025 at 3:01 PM

I guessed that pretty much that was going to be the answer...
Not that I'm using that plugin anymore, but after a long few years travelling and not having enough time to invest on production, I have retaken my projects and this is used in an old, old project. I've checked if the sound is still the same and it seems that error showing up it's not affecting the original sound programmed. Won't be using that plugin anymore but I still have to finish some of them using that old vst. Nowadays I prefer Imperial Delay or Tekturon.

As always, thanks again for the answer!

P.S.: Forgot to mention I'm using Bitwig, which has its own bridge for old 32-bit gear. Seems to work efficiently.

 

Hi @clipper, if you have old projects, simply install an older version, i.e., the DAW you used to create your project. If you make a living from music and are currently working on a project, you shouldn't do any updates at all until your project is finished.

Older versions of Bitwig Studio https://bitwig-studio.en.uptodown.com/windows/versions

For example, I have two DAWs installed: an ancient 32-bit Studio One and a current 64-bit version.
You just have to create a separate folder for the old DAW, for example, "Stdido 32-bit," and install it there.

 

BIONIC SUPA DELAY - ED 1_1 works in my newest VSThost bei Heim and in the latest REAPER 64bit software without any hickups. not 2 weeks ago I have used it in a project.

 

The " Bionic Supa Delay - ED 1_1.dll " C:\Program Files (x86)\VSTPlugins works in Studio One (32 Bit Version) on " Windows 11.

Installation from the Manual_

• Copy the dll file from the download archive to your VST folder
• Restart your host software (DAW)
• Load the plug-in

Note: In case of problems please read the following. Upon starting the plug-in for the first time a number of files are automatically extracted to your VST folder. On Windows versions from VISTA onwards by default plug-ins are not allowed to write files to your 4 BIONIC SUPA DELAY - User Manual hard drive.

This will typically cause an error message from your DAW reporting missing files. You can fix this issue by changing the write permissions for your VST folder as follows:

• Use Windows Explorer to browse to your VST Plugins folder.
• Right-click the folder – 'Properties'
• Choose 'Security' tab.
• Click 'Edit' button (You may need to click a UAC prompt).
• Select user name "Users".
• Tick options Allow 'Write' and 'Modify'.
• To finish Select 'OK' to close the two dialog boxes.

 

Last edited: Sep 13, 2025 at 3:06 PM

The truth is that idea was vaguely in my head, although I wasn't very sure that the problem was related to the DAW version I'm using, or if it was related to Windows 11, which is the laptop OS I'm moving to. But since the plugin is working on the project I'm using it, I won't bother much more. I've finished that project this morning and I'm happy with the result. I'll just keep away of that plugin from now on, though it is a pity, since it has such a peculiar fx when you do some knobs changes all of a sudden. But I'm pretty sure there's other new surprises to find out with other plugins in the future.

Respect to the suggestion of changing the security properties for writing/modifying, I did, for both, 32bit and 64bit folders, reloaded Bitwig and the project but the same error keeps showing up. Anyway, thanks again for all your help! Tomorrow, I'll be asking something else, if you fancy to shed some light, hahahaha!!! (Just joking!).

Keep well!

 

vcredist_2005 both x86/x64 and NET Framework 3.5 are needed to run most sub 2010 plugins, i accidentaly figured it out while trying some old xoxos plugin, also some older vcredist work better with old plugins so it does not hurt to try a few.

Sometimes you can even pull out dll-s and the manifest file and throw it in the .exe folder for exsample Bitwig.exe root and it will load it before it looks system32 or winsxs folders!

Gl

 

Please install:

Visual C++ Redistributable Runtimes All-in-One Jul 2025
www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one

 

Yeah, I got them all installed because one of the days I got well fed up of checking if I had already installed or not the one the vst I was installing needed. So I installed them all, wether they were needed or not.






And NET Framework 3.5 is in the system as well: