- #PROTOOLS 12 WINDOWS 10 INSTALL#
- #PROTOOLS 12 WINDOWS 10 UPDATE#
- #PROTOOLS 12 WINDOWS 10 DRIVER#
- #PROTOOLS 12 WINDOWS 10 WINDOWS 10#
#PROTOOLS 12 WINDOWS 10 INSTALL#
The Pro Tools 11 install would tell me "Avid requires the following software to be installed before proceeding" and lists "PACE License support" even though I have already had the latest version (v5.2.1) downloaded and functioning correctly.
#PROTOOLS 12 WINDOWS 10 DRIVER#
I found out that "InterLok Driver Setup Win64" was the culprit of the issue because I tried installing it on its own through the legacy download section of iLok's website, and encountered the same crashing error as when I would run the Pro Tools 11 install regularly. So I downloaded it again separately, restarted my computer, no issues.Īfter lots of digging, and checking the "legacy installers" section of iLok's download website, I figured out the problem was that Pro Tools 11 installation was attempting to force the install of the legacy "interlok driver" software (which is the legacy component of PACE License Support) for some reason, even though I already had the latest iLok license manager installed and functioning properly. But I remember I had previously installed the latest version of the iLok License Manager, which is the same thing as/includes the latest PACE License Support, without any issues. This told me that PACE License Support was the cause of the crashing. It asked me for a reboot and then the same crash sequence happened. After some experimenting I found the culprit: I began the installation of Pro Tools 11 only to where it installs PACE License Support, and didn't actually install Pro Tools. I tried installing Pro Tools 10 as well and got the same crashing.
#PROTOOLS 12 WINDOWS 10 WINDOWS 10#
From there I would have to select "startup repair" which would seem to act as a sort of system restore - when it successfully boots up again my computer would not have Pro Tools or the iLok License Manager/PACE installed anymore but everything else would be intact.Īt this point I was very scared that Pro Tools 11 wouldn't work on my PC, but my previous Windows 10 laptop ran it just fine so I was very confused. It would repeatedly crash on the "dots spinning in a circle" startup screen, turn into "attempting repairs," and then bring me to the boot recovery menu. Every time I would run the PT11 installer, when it asked for a reboot after the install completed, my computer would not boot back up. I couldn't install Pro Tools 11 on my brand new Windows 10 PC due to Pro Tools forcing me to install an outdated and unsupported PACE License Support. More information on the original alert can be found here.I want to share with you my nightmare experience attempting to install Pro Tools 11 on my new Windows 10 machine, and share the solution I found, so that anyone in the same boat as I was in can be saved hours of headache and hair-ripping. Having built a few systems with Windows 10 and Pro Tools I confess that I’ve not tried those particular combinations but otherwise I’ve found Pro Tools to work very well on Windows 10. What these problems are is anyone’s guess. With regular Pro Tools there appears to be no such limitations other than the usual feature of not being able to cope with anything but regular 2-powered buffer sizes. HD Native – avoid using these buffer settings:
There are some provisos if you are using Pro Tools HD Native or HDX. I stumbled across someone mentioning it on Facebook, otherwise there seems to be no other press release or announcement. It’s a bit weird because you’d think it was a big deal but all they did was release a little “ALERT” (in capitals so it must be important) on the System Requirements page. All we know is that someone somewhere in Avid has said “yep, it’ll be fine, let’s not make a big deal about it”.
Or maybe they’re aware that many people are actually using Pro Tools on Windows 10 and nothing bad has happened. Maybe we’ve been waiting for the support staff to finish their Windows 10 training.
#PROTOOLS 12 WINDOWS 10 UPDATE#
They haven’t released a software update that makes it compatible, it’s still the same Pro Tools 12.5 that wasn’t supported on Windows 10 just the day before.
0 kommentar(er)
