Vienna Symphonic Library Forum
Forum Statistics

180,734 users have contributed to 42,140 threads and 254,357 posts.

In the past 24 hours, we have 4 new thread(s), 14 new post(s) and 56 new user(s).

  • [SOLVED] VI crashing Pro Tools in Admin mode

    Hi all. I have a windows 10 x64 machine with Pro Tools 11 Pro HD, all SSD drives and 32gb of ram, AMD 3700x 8 core processor. 

    So I have this issue that Vienna instruments crashes pro tools, it's the ONLY plugin that does this. 

    Everything else (I have a lot of them) all work fine.

    Disabling admin mode fixes it but I can't do that, I need it on because it breaks other things to turn it offs. 

    I am using the latest version of VEP 6 and VI and also updated e-licenser to the latest version. Pro tools is also as far updated PT11.

    I don't what caused this, it used to work fine but windows forces me to update along with the other programs so I need a fix asap. 

    On starting Pro Tools it shows an error and asks to "retry" indefinitely, it causes the app to hang or crash. 

    Application 'Vienna Symphonic Library' has caused the following error: 

    Process with the ID NOT found.

    Options: 

     - Click <Ok> to abort.

    Clicking OK doesn't work. It is stuck in a loop forever until I restart the computer. 


  • last edited
    last edited

    Hi notedmusic,

    A clean uninstall & reinstall might help here (for each VSL plugin in question). Please follow these steps:

    1) Uninstalling VE Pro via the Windows Uninstaller

    2) Deleting any leftovers here: C:\Program Files\Vienna Ensemble Pro

    3) Deleting the preference "*ini" file here: %appdata% > VSL

    4) Deleting any leftovers here: %appdata% > VSL > Vienna Ensemble Pro

    5) Then reinstalling VE Pro 7 with the latest installer from MyVSL.

    Best,
    Paul


    Paul Kopf Product Manager VSL
  • Okay so after a lot of trial and error I was able to resolve the issue for now. Here’s the steps- Right click on all Vienna *.exes in program films and x32 folders and set to Admin mode. This seems to have fixed the issue at least for now.