The following plug-ins failed to load because they are not valid 64 bit AAX plug-ins

[Wilfriedd]

Originally Posted by sleepingtiger

I'm on Windows and I've experienced this problem and it's annoying. In my case it happened mostly with Izotope plugins. It's been a while but if I remember correctly this was my solution:

1. Create a folder on the desktop and relocate the problem plugins temporarily to that folder.

2. Reopen Pro Tools to be sure the error is gone. Close Pro Tools.

3. Replace the plugins back to the plugin folder and reopen Pro Tools again.

In my case this would usually fix it though I seem to remember having to repeat the process occasionally. Regardless, I've always been able to get up and running again with this method eventually.

Good luck with it!

Thank you , but i doubt it will solve this .


In fact , when i open pro tools , i get this message with all these plugins involved. Pro tools asks me if i want to move them in UNUSED PLUGINS.
i choose "NO" because i always want Pro Tools to scan them .


If i do what you say , obviously the error will stop . (Because the first time , i chose to move them in unused folders and the error stopped) .


Moving them out and bringing them back will not solve that. But i'm trying that now and i'll let you know . Thank you for your reply !

[Wilfriedd]

Originally Posted by sleepingtiger

I'm on Windows and I've experienced this problem and it's annoying. In my case it happened mostly with Izotope plugins. It's been a while but if I remember correctly this was my solution:

1. Create a folder on the desktop and relocate the problem plugins temporarily to that folder.

2. Reopen Pro Tools to be sure the error is gone. Close Pro Tools.

3. Replace the plugins back to the plugin folder and reopen Pro Tools again.

In my case this would usually fix it though I seem to remember having to repeat the process occasionally. Regardless, I've always been able to get up and running again with this method eventually.

Good luck with it!

I did your trick , it didn't work ! Thanks anyway !

[sleepingtiger]

Originally Posted by Wilfriedd

Thank you , but i doubt it will solve this .


In fact , when i open pro tools , i get this message with all these plugins involved. Pro tools asks me if i want to move them in UNUSED PLUGINS.
i choose "NO" because i always want Pro Tools to scan them .


If i do what you say , obviously the error will stop . (Because the first time , i chose to move them in unused folders and the error stopped) .


Moving them out and bringing them back will not solve that. But i'm trying that now and i'll let you know . Thank you for your reply !

Yes, this is what happens when I've experienced the problem. Pro Tools always asks about moving plugins to the UNUSED folder when it can't scan them. Your description sounds exactly like what I've experienced. Too bad my fix doesn't work for you. I hope you find something that does!

[Darryl Ramm]

I would contact the plugin vendors. My suspicion is it's a code signing/security/licensing flakey issue somewhere between Avid, iLok/Pace and the plug-in vendors. I suspect some plugin vendors support might be more responsive.

[albee1952]

Originally Posted by Wilfriedd

I don't really get what you say .


I upgraded from Pro tools 10 to 2020 by uninstalling pro Tools 10 and downloading via AVID LINK .


Windows 10 has nothing to do , since it's working well with all others programs , and i already did a clean install before installing all of these .


For my plugins , i chose AAX and VST3 since i'm using FL STUDIO too .

Uninstalling PT10 leaves behind a ton of stuff that didn't get uninstalled. It also probably left a bunch of issues in the Registry(unless you cleaned that out). Just trying to offer suggestions to help get you back to a working system

[JFreak]

Originally Posted by Wilfriedd

Windows 10 has nothing to do, since it's working well with all others programs

Unfortunately that is not a valid point regarding PT. You need to follow compatibility requirements religiously, starting with the W10 build required

[WKG]

I've run into this before.

Usually opening Protools and letting it scan a few times weeds it out. Even with up to date plugins I find that Protools will sometimes throw an error on the initial update scan but then accepts it on subsequent runs.

[Wilfriedd]

Originally Posted by WKG

I've run into this before.

Usually opening Protools and letting it scan a few times weeds it out. Even with up to date plugins I find that Protools will sometimes throw an error on the initial update scan but then accepts it on subsequent runs.

Hummmm . i'm trying to do that. I run it , then reboot my computer multiple times . I've done it more than 20 times since yesterday
nothin happened ....


Well i'm done ....