2018.4 + Windows 7: Won't even let me install :(

[DontLetMeDrown]

2018.3 installs, and I was able to use it for a day, but after a couple days, it would no longer launch, so I went back to 2018.1. Today I had some time to install 2018.4, bit it refuses to install and gives the error message: The operating system is not adeaute for running Avid Pro Tools.

"Not supported", I can handle, but to not let us install at all, is that really necessary? I'm only 1/4 of the way through my subscription, so this is bad news. Another tidbit- Windows 10 is not compatible with my Aurora 16 + AES16e setup. Caused tons of problems with settings changing automatically which caused my 32-channel system to switch to a 16-channel system so half of the channels wouldn't pass audio. Works perfect on Win 7, so I guess my system is EOL. Very disappointing.

[TNM]

Originally Posted by DontLetMeDrown

2018.3 installs, and I was able to use it for a day, but after a couple days, it would no longer launch, so I went back to 2018.1. Today I had some time to install 2018.4, bit it refuses to install and gives the error message: The operating system is not adeaute for running Avid Pro Tools.

"Not supported", I can handle, but to not let us install at all, is that really necessary? I'm only 1/4 of the way through my subscription, so this is bad news. Another tidbit- Windows 10 is not compatible with my Aurora 16 + AES16e setup. Caused tons of problems with settings changing automatically which caused my 32-channel system to switch to a 16-channel system so half of the channels wouldn't pass audio. Works perfect on Win 7, so I guess my system is EOL. Very disappointing.

would you consider win 8? Avid still support it and it should run all your gear and it's a bit of an underrated, solid OS.

[Wizzoboy]

I got round this problem by not doing a clean install. Usually I remove the previous version but this time installed 2018.4 over 2018.3. Now it runs with no problems. It will be a case of updating the OS in the near future though.

[64GTOBOY]

^^^+1
I have 18.4 running on three windows 7 machines with no issues. They are all Intel processors. Don't know if that makes a difference

[DontLetMeDrown]

Interesting. I’ve never tried to install a new version that way. 64GTOBOY, I’m guessing you installed yours the same way? I will give that a shot. The Win8 suggestion is good as well. Will research that. Thanks everyone!

[DontLetMeDrown]

Ok, now I'm getting angry. I'm now having the same problem with 2018.1 where it will not launch. I was just using the damn thing last night. What on earth is causing Pro Tools to not launch at all? Might have to hit up support this morning.

[Wizzoboy]

Well, the compatability notes for 2018.1 and up do show that Win 7 is not supported.

[64GTOBOY]

If you have access to 12.x you can update from there. I am semi -sure I updated all mine using app manager. I download the install files just to have backups, which I have been doing since 12.1, but i don't usually update the way you are "supposed" to (uninstall, etc). I generally start with the smallest laptop and when it updates correctly i do the bigger laptop , then the desktop last. Advise you to"Trasher" pref.s first. I'd be willing to bet that at this point you have a lot of extraneous s&%t in caches that are causing issues. As for the whole "not supported" that really just means that avid is not going to bother testing on win7 anymore, but lets face it 18.1 is really just 12.93 under the hood. And win10 may have changed it's UI from 7 but the underlying code, well it ain't that different.

[Shan]

Originally Posted by DontLetMeDrown

... Today I had some time to install 2018.4, bit it refuses to install and gives the error message: The operating system is not adeaute for running Avid Pro Tools...

Install 2018.3 first and then install 2018.4 overtop of it. Don't do a clean install by uninstalling 2018.3 first. Hope that helps.

Shane

[DontLetMeDrown]

Thanks for the tips guys. I'm in the middle of a few projects right now and haven't tried to mess with it again. Digi support also suggested trashing prefs & databases which got my 2018.1 launching again. Will try the 2018.3->2018.4 install when I'm more caught up.