![]() ![]() ![]() I've explained you are wrong, asked you to reread the thread and you seem to have not done that carefully. These are not third party plugins, they are internal (and largely hidden) inside Pro Tools, they validate as loading and that validation fail is not caused by other plugins, which won't even have loaded at the point this failure happens. That is nothing to do with what is being talked about here.ĭo you understand what these systems plugins are? That they live somewhere very different. In the past you found a faulty third party plugin by doing the correct standard troubleshooting for that problem. It was as simple a solution as I could muster. Took me about 30 minutes to get everything sorted. Guess I could have just moved 3rd party plugs out, but could not tell which were which in some cases. Narrowed it down to a third party plug that caused the issue. After moving them out, I started moving a few back at a time, initiated PT until it failed to load. And if things are not resolved fast you might save time and just jump to doing a clean Windows install. My gut feel is this is very likely to be Windows messed up. (edit run cacls on the file and folders). If you cannot do that: What permissions does you used ID have? (edit just run whoami /all)Īnd either way: What are the file and directory permissions for the plugin folders, files and Unused folder. And that's not really going to help anyhow since it's not going to get you back any of these usable systems plugins). What is the history of this computer? Did Pro Tools ever run on it? Did you build it and install software on it or did somebody do that for you? Etc.Ĭan you manually move those plugin files from the File Explorer or CMD shell? (EDIT: Oops and of course it turns out a typical setup user (including one in the Admin group) on Windows does not have permission to move the those systems plugins to the Unused folder, so that suggestion is of no use - and I suspect that the developers may have messed this up and possiblet Pro Tools itself can't move those files, which may explain the failure message when Pro Tools tries to do that. No surgery was done to Windows? This was a standard install of Windows? Is not a clone/restoration? It’s a standard Windows NTFS file system? Pro Tools executable is installed in the default location on the C: drive? Has anybody seen anything similar and remember how to fix it? I'm at a loss. My only option is to click "OK" after which it exits. Even if I select to move them (which I shouldn't) I can't because it says Access is denied.Īfter getting passed this, I get this message: Pro Tools has encountered an unrecognized component and must now exit. These are core aax plugins that are required for protools to run. I'm guessing that Pro Tools does not have permissions to read many of the necessary files to open correctly.Įxhibit A) When I open Pro Tools, it tells me these plugins are not valid 64 bit plugins. I've tried all the basic troubleshooting: Reboot computer, trash prefs, uninstall and reinstall protools, turn off windows defender, run as administrator. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |