So yesterday I decided to install S1 5.2.0 just to find out that vstservice.dll make it crash on every startup. If I move away the dll from its folder S1 runs normally but without vst support and, as soon as I move the dll in its folder, S1 begin to crash again.
I read that a possible solution could be to rename %USERPROFILE%\AppData\Roaming\PreSonus\Studio One 5 and then let S1 rebuild it but it didn't worked for me.
Is there someone else experienced the same problem? Fixes or workarounds?
I'm on Windows 10 Pro (20H2) and there are no 3rd party plugins.

 

Does it crash when it's scanning the plugins at startup? Or when you're working with it already.
Just in case, check that VST support is enabled in advanced settings. although it shouldn't crash anyway.

 

Last edited: Apr 17, 2021

Yep it crash when it's scanning the plugins at startup but, as I wrote, it's a fresh install and there are no 3rd party plugins to scan.

 

The plugin scanner (that most likely uses that dll) is known to give some problems, but I don't remember when.
Do you use some Firewall?

 

Just Window Defender Firewall but S1 is free to go in the wild...

 

I tried to switch to a previous version (5.1.0) and it seem to work, I wonder if replacing vstservice.dll from 5.10 to 5.2.0 will work...
EDIT: It seem to work, definitely something is wrong with vstservice.dll from 5.2.0
EDIT 2: I was wrong, It doesn't work. With dll from 5.1.0 S1 doesn't crash anymore but there's no way to set the vst path in the option panel.

 

Last edited: Apr 21, 2021

1. Uninstall Studio One (backup your Sounds)
2. Delete all Studio One Files
3. Use the CCleaner Tool /Registry Cleaner
4. Restart your PC and install new

Delete this one:
C:\Users\YourName\AppData\Roaming\PreSonus
C:\ProgramData\PreSonus
C:\Program Files\PreSonus

Spoiler: Warning proceed at your own risk:

Warning proceed at your own risk:
Assuming it is crashing on VST plugins.

In that same directory (settings folder) under X64 or X86 depending on if you are 64 or 32 bit, you will find services.setting file.
With S1 off open it in a text editor and change:

<Section path="{254061B1-7E4E-4D4F-9F79-768BD4B66F6C}">
<Attributes friendlyName="VST 3 Plug-In Support" enabled="1"/>
</Section>
and
<Section path="{967BFE7C-01EE-44F0-A03A-59BBAD1D23BE}">
<Attributes friendlyName="VST 2.4 Plug-In Support" enabled="1"/>
</Section>

Set a service the enable="1" to "0" to turn it off for debugging.
Then S1 will open with no plugins.
Once opened you then you want to edit the same file and turn 3 or 2.4 vst back on to isolate the failing service.

Also check all your location path once open.

You can do the same thing with other services if it it is something else.

It looks like you've added Studio One's application plugins folder (which isn'ta VST plugin folder) to the Studio One VST Plug-ins locations (Options > Locations > VST Plugins).
Easiest solution is to rename %USERPROFILE%\AppData\Roaming\PreSonus\Studio One 3\ (when Studio One is closed) and let Studio One rebuild a new settings folder on the next start.

 

Last edited: May 4, 2021

Anyone got a solution for this one?..

 

I had the same issue after trying S1 5.2 on a freshly installed windows and if I remember correctly installing on top of version 5.0.1 (installing in the exact same location) solved my problem (make sure you remove the programdata and appdata in the first step). Please let me know if it works for you, because I might not remember some neccessary details about how I got it to work.

 

I had the exact same problem, the solution was to let S1 (main exe) connect to the internet when the scanner was scanning. I think that was with an earlier S1, tho, so I dunno if it will help?

Spoiler

Windoze defender is notoriously bad at (or good at =) blocking things, so it's likely to have seen a change in an exe and decided to block it? ¯\_(ツ)_/¯

 

Actually i got a solution! There's a new torrent of S1 5.2 on RuTracker. It's the "NOINSTALL" one and it works like a magic for me on a fresh install!

 

Last edited by a moderator: May 25, 2021

oh you have to block s1 w/the firewall man

 

I think (well, it did for me) the scanner crashes if you block the s1 exe with firewall et al. You can turn it on afterwards, if you need to? I didn't realise but I think I had hosts block presonus, so that's prolly a good workaround? Bit annoying, tbh.

 

Having all the same problems that you all are having. Tried deleting vstservice.dll, ect.

Tried the 5.2 Noinstall torrent, same issue with vstservice.dll,

Tried the 5.1 Noinstall torrent, works! For now. It is fully working, can scan and add vsts.

Hope this helps