Pro Tools 10 Access Violation after installing Pro Tools 12

[dalves]

I apologize if this has been posted somewhere else in the forum, or if I am missing some needed information...

I am running a Windows 7 64bit Machine. I have been using Pro Tools 10.3.10 for the better part of a year with no problems. I recently learned that I could install Pro Tools 12 on the same computer as Pro Tools 10 as I bought that software bundle. Through some trial and error, I was able to get Pro Tools 12.5.2 installed on the same machine and it seems to work fine. However, now when I try to launch Pro Tools 10, it won't fully launch. It gets to the AAX version of "Eleven" and tells me I don't have a license for it. I close that out and then it starts loading other plugins. When it gets to AIR Enhancer, I get an "Access violation, unable to read location 0x000000008". I guess I've been lucky as I haven't had to do much wrenching on Pro Tools in the many years I've used it, so I wasn't sure where to go from here. I can say, that I had a problem with access violations in Pro Tools 10 when I recently bought an East West library, and Pace updated my iLok driver. I installed an older version of the Pace driver and the access violations were gone. I don't remember seeing Pace updating the iLok drivers when I installed Pro Tools 12, but am wondering if that may be the cause. I was just curious if others have seen this problem and if there may be a known cause. Any help would be appreciated.

[jeam25]

Hi friend !

Fisrt remove all the plugins from the PT 10 plugins folder .

Launch PT without ANY plugin and exit .

Add by groups the plugins , launch and exit PT after each group add until you successfully load them all in .

Remeber to have PT the running as admistrator setting .

Report back

[dalves]

Hi, I removed all of the plugins from PT 10 and ran it. It opened fine. Just out of curiosity, I copied and pasted the entire plugin folder back in it's original location, and ran PT 10. It loaded all the plugins correctly without any errors and has worked fine since. Not sure what the problem was or why the copy and paste fixed it, but it's been running great ever since. thanks again for the help.

[jeam25]

Good ! Glad it works !

Sent from my SM-G930P using Tapatalk