Won't cause BSOD to start protools, but most plugins won't work, with permission errors, the exact message being (Window title: "Initialization Error") "User privileges insufficient to start a low level driver." Installing the latest "License Support Win64.exe" from & "Avid Pro Tools.msi" from ProTools 10.3.10 installer Pro_Tools_10_3_10_Win_84130\Pro Tools\Pro Tools Installer\ISSetupPrerequisites\PACE License Support 2.2.1 In this case, PACE License version is 2.2.1, we can see it from the folder inside Pro Tools installer: Will install an old legacy iLok driver which comes bundled with ProTools, causing BSOD after asking to reboot Here is the install processes I attempted: In fact, even default ProTools plugins cause issues, so on my last attempt, I didn't even install any plugin other than the ones bundled with my Pro Tools 10 installer. I'm totally stuck, we need a genius move from a power user, or a fix either from either iLok or Microsoft.Īny hint or help is appreciated, I cannot make music anymore at the moment. If this is confirmed, then there must be a way to manually correct what's missing upon installing Legacy iLok directly from Build 2004. But in the end, it seems like there is no way to boot with the legacy driver at the moment.įrankpc says installing the driver BEFORE updating Windows works for them. I've tried installing the old driver, then the legacy driver, tried installing with Win 7 compatibility. You need to basically do these commands: c: cd Windows\System32\drivers ren Tpkd.sys tpkd.junk Note that if you have the BSOD issue and no restore point, you can also rename the file with command-line in Windows troubleshooting mode. Either it causes a BSOD pointing to Tpkd.sys or just fails to boot and restarts in troubleshooting mode. On Windows 10 Build 2004, installation legacy iLok driver cause a failed boot which forces to use a Windows restore point. Pro Tools 10 itself works with the new iLok driver, but most plugins (including Avid Virtual instruments and most essential plugins) only work with the legacy iLok driver (otherwise you got privilege errors on Pro Tools 10 startup)Ģ. InterLok Driver ("Old" or "Legacy driver")ġ. Doing so removed the existing older license.Įncountering a very similar issue issue with a fresh install of: And all I did was install the new iLok Manager. Amazing!! Prior to the license update, the W10 upgrade failed four or five times, which was a lot of hours. I then installed the update to W10 build 2004 and it was successful. UPDATE: While in W10 build 1909, I updated the PACE license to version 5. However it seems the 11R Editor would have been written at the same time it was removed from ProTools, so why wouldn't it have the newer license? ![]() ![]() As soon as the reboot occurs, Windows crashes, but I am able to remove the upgrade and return to build 1909.ĭoes it seem I should be able to install the 5.2.1 license and avoid the older license? Maybe do that while still in Windows 1909, then upgrade to Build 2004? Then look at the installed programs to ensure the 5.2.1 version is there and not the legacy one? Then the install of the Editor seems to go well and requests a reboot. If I upgrade to build 2004 without having the Editor and the legacy PACE/ iLok license installed, the upgrade works properly. But when I upgrade to Build 2004, Windows crashes and fortunately, I am able to recover back to build 1909 with nothing lost. If I install the Editor in W10 build 1909, it works fine. ![]() I am trying to install the 11R Editor in W10 build 2004.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |