Acid Pro 11 plante "update VST plugins"

Strictly-East wrote on 12/8/2025, 10:24 AM

No response from support, unable to work since last week

I haven't used Acid Pro 11 for several weeks. It was working perfectly before, but now it crashes when I start it up..
I've tried everything: uninstalling/reinstalling Acid, uninstalling/reinstalling Visual C++.
Reset the settings,
moving the VSTs to avoid scanning, nothing works.
Finally, I decided to reinstall version 10, and now it works.
Is there a way to recover my functional version 11, or do I have to wait for an update or the release of version 12?

 

Comments

SP. wrote on 12/8/2025, 10:32 AM

@Strictly-East Try resetting the program settings. Hold CTRL and SHIFT, then start Acid while still holding both keys. A window will appear and ask you if you want to reset the program settings. Confirm that and maybe it will work again.

Strictly-East wrote on 12/8/2025, 10:45 AM

Already done, I also deleted all cache data.

SP. wrote on 12/8/2025, 2:45 PM

@Strictly-East Assuming this is caused by some VST, did you install a new VST between the last time Acid worked and now? Have you removed some entries from the VST paths in the program settings just to make sure Acid only scans certain folders with VST Plugins you know work fine?

Alternatively, if you open the program folder of Acid, you'll find audio_plugin_scan_server exe files. These programs scan the VST plugins. You can try to replace them with the older ones from Acid 10 (don't forget to make a backup of the files first!), or newer ones from Sound Forge Pro 18 (simply install the free trial and copy the files from there). The newest version of the audio_plugin_scan_server exe files can be found in Music Maker 2026 (you can also install the free trial), but I don't know if they are compatible with Acid. I think the Sound Forge Pro 18 files should work fine.

Strictly-East wrote on 12/12/2025, 10:07 AM

No new VSTs installed, I emptied all the VST folders.
I copied the audio_plugin_scan_server files from SoundForge 18 without success, then those from Acid Pro 10 (which work perfectly), but version 11 still crashes.
I'll have to go back to Acid Pro 10, which is rather annoying when you have a license for version 11.

SP. wrote on 12/12/2025, 10:16 AM

@Strictly-East Please copy and paste the crash reports from the Windows Reliability Monitor. Maybe this problem is driver related.

Press the Windows key and R on your computer keyboard. This opens the Run window. Type perfmon /rel and press Enter. This will open the Windows Reliability Monitor. Red cross icons symbolize crashes. Click on such an icon and then double click on the crash entry to open a detailed report. Copy and paste it here.

Strictly-East wrote on 12/12/2025, 10:29 AM

Source
ACID Pro 11.0

Résumé :
Ne répond plus et a été fermé

Date
12/12/2025 11:22

Statut
Rapport envoyé

Description
Un problème a empêché ce programme d'interagir avec Windows.
Chemin d'accès de l'application défaillante : C:\Program Files\ACID\ACID Pro 11.0\acidpro.exe

Signature du problème
Nom d'événement du problème : AppHangB1
Application Name: acidpro.exe
Application Version: 11.0.2.21
Application Timestamp: 639995d6
Hang Signature: c3b0
Hang Type: 134217728
Version du système: 10.0.26200.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Additional Hang Signature 1: c3b0cdfa9b73a3d6ecd6cbfad9a461a9
Signature de blocage supplémentaire 2 : 83a6
Signature de blocage supplémentaire 3 : 83a65bcd9309e7a388e57ce7420698b9
Signature de blocage supplémentaire 4 : c3b0
Signature de blocage supplémentaire 5 : c3b0cdfa9b73a3d6ecd6cbfad9a461a9
Signature de blocage supplémentaire 6 : 83a6
Signature supplémentaire Hang 7 : 83a65bcd9309e7a388e57ce7420698b9

Informations complémentaires sur le problème
ID de compartiment : 006735262849dc57aa05226e0d424934 (1874942675933874484)
 

SP. wrote on 12/12/2025, 11:43 AM

@Strictly-East Thanks! Here the same problem occurred (AppHangB1) and it was caused by the audio driver.

https://www.magix.info/us/forum/acid-11-quits-responding--1341184/

There are also some other tips like running sfc and DISM via the command prompt to repair Windows.

In case your problem is caused by the old Magix Low Latency ASIO driver, you can uninstall it the following way:

- press the Windows key + R on your computer keyboard, and type REGEDIT in the Open field:

- then navigate to: HKEY_LOCAL_MACHINE > SOFTWARE > ASIO > Magix Low Latency 2016:

- now, simply right click the Magix Low Latency 2016 folder, and delete it.

- then restart your computer. Please select the Restart option and not the Shut down option.