Can't open the new Acid Pro 10 on my Windows

Mark-Abramov wrote on 3/5/2020, 8:53 AM

Extra Information
   File:                C:\Users\M...k\AppData\Local\MAGIX\ACID Pro\10.0\dx_grovel_x64.log
   File:                C:\Users\M...k\AppData\Local\MAGIX\ACID Pro\10.0\vst_grovel.log

Problem Description
   Application Name:    ACID Pro 10.0
   Application Version: Version 10.0.0 (Build 14)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.657_none_e6c5b579130e3898\COMCTL32.dll
   Fault Address:       0x00007FFE31593DA9
   Fault Offset:        0x00000000000A3DA9

Fault Process Details
   Process Path:        C:\Program Files\ACID\ACID Pro 10.0\acidpro.exe
   Process Version:     Version 10.0.0 (Build 14)
   Process Description: ACID Pro 10.0

Can you help me to solve it?

Comments

MarcoStorm wrote on 3/6/2020, 12:06 AM

Dear @Mark-Abramov,

was it yor first start of ACID Pro 10 or could you use it before the crash? Does the crash happen while the splash screen is still open or when ACID is trying to load the recent project?

Best regards,

Marco

Mark-Abramov wrote on 3/8/2020, 9:30 AM

Yes it was from the first star.
after it I twice reinstall the program, but was same problem.


Dear @Mark-Abramov,

was it yor first start of ACID Pro 10 or could you use it before the crash? Does the crash happen while the splash screen is still open or when ACID is trying to load the recent project?

Best regards,

Marco

 

Frank_Fader wrote on 3/9/2020, 4:20 AM

Maybe the problem is caused by a bad vst plugin during startup scan. To prevent any vst scanning on startup, you need to rename your vst2 plugin folder and/or move your vst plugins to a another (temporary) folder.

Then check if this resolves the issue. If it works, put the plugins back into their original place step by step to find out which plugin causes the crash. (If it doesn't help, you should put your vst plugins back to their original place again, too, of course).

Please also contact the support, if you haven't done yet.