legacy PACE License Support crashes Windows 10, couldn't install Pro Tools 11 (RESOLV

[UltimateByte]

Allright, got some news. I found exactly why it is that Tpkd.sys doesn't work with newer builds of Windows.

Seeking through the Windows Event Viewer, I found this error:
"The PACE License Services service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly."

Then I found out that: "Microsoft has removed the Interactive Services Detection Service on Windows 10 Version 1803."
https://kb.firedaemon.com/support/so...-and-session-0

More details about supported versions here:
http://batcmd.com/windows/10/services/ui0detect/

But it appears that upon upgrading from previous builds, that service still exists, which explains why my previous install from late 2017 that I upgrader to build 1909 or 1903 still worked with the driver.

Other users, if you're willing to, you could verify that by checking if you find "Interactive Services Detection" in your services list, and by checking your Windows version/build number.

So there must be a way, or a hack to get it back.
Microsoft support was very kind and attentionate until I asked for that... Now I've got two support people leaving the chat right away when exposing that. I guess it's a sensitive subject.

I'll try to hack a way to add it back.
This link says:
"Make sure that the UI0Detect.exe file exists in the %WinDir%\system32 folder. If this file is missing you can try to restore it from your Windows 10 installation media."

Then run: sc config UI0Detect start= demand

So I'm restoring this file right away and will try that. I'll be reporting back and spread this file and procedure widely if it works.

Edit: This file doesn't exist on my previous Windows install. Gotta boot off of my old legacy Windows install, to check out the event log from it.

[UltimateByte]

After digging more, remembered I had an iLok account...

I've then been able to open a support ticket:
"Hello. Pro Tools 10 default plugins requires older iLok drivers to work (latest shows "User privileges insufficient to start a low level driver.") .
After installing legacy driver, running a fresh Win 10 Install, upon booting, computer blue screens incriminating Tpkd.sys because it requires "Interactive Services Detection Service" which was removed since Win 10 Version 1803.
I've been able to sort the booting issue, but the driver doesn't work, starting with loading BF-76.aaxplugin then other plugins fail as well. Can you please fix the driver or provide a workaround to make it work? Thank you"

PS: I'm still unable to get Tpkd.sys to load and work properly.
I've tried importing the exact same old iLok license manager (including the program service and everything) from my previous Win10: Does not work. Also I cannot find a way to retrieve the "Interactive Services Detection Service". My guess is it stays in Windows somehow if it's in use upon upgrade. Would need to start from build 1709 to keep it, if I'm right. No way I'm doing this. Prefer ditching pro tools and keep a secondary Windows 7 handy on a drive if I ever need it.

[kevindubois]

Wow UltimateByte, you rock for doing all that digging! That's a really interesting find about the "Interactive Services Detection" service being removed in the latest versions of Win10, and how the legacy PACE License Support needs that service in order to run. Very cool to get to the bottom of exactly WHY the issue is happening on PT10 and older.

Unfortunately this seems like a very difficult fix, that would require either deep hacking, or a manual patch from either Microsoft, PACE, or Avid. Unfortunately this doesn't seem like a high priority issue for any of them....

[OleMoe]

Originally Posted by kevindubois

So after ripping my hair out for hours a few nights ago, I finally reached a solution! When PT11 prompted the install of PACE License Support (as it always did, even though I had the newest version already installed), I clicked install, as I was always forced to do in order to continue. But, when Windows 10's action center popped up, asking if I trust the developer and wanted to install the software, I hit DON'T INSTALL. The PT11 install software did not error out and continued on as normal, allowing me to install PT11! I've tested Pro Tools and everything runs as it should.

I just wanted to let you know that you can fully bypass the installation step where it tries to install the legacy pace drivers. You simply open the installer folder, enter the PT folder and run the "Avid Pro Tools.exe" only. This starts the installation of Pro Tools 11 directly.

And to the ones trying to install PT10 on the latest Windows 10 build I can just say sorry. You will need to be a hell of a hacker to hack all the licenses to get the Air Creative collection to work, and I don't even think it's possible at this point.

I've been at this for a week now, and at the point where I almost sendt half my coputer back to the store for replacement when I found my issue. After some trying and failing with PT10 (as I just liked it better and had more compatible plugins) I was so happy that I read this post and found that PT11 will actually work still. Luckilly some of my plugins also have 64-bit licence.

So thanks to the thread starter!

[RJH_]

Hi All,

Thanks to everyone who contributed to this post.

I would just like to briefly share my experience and how I fixed the issue which may or may not be achievable for everyone.

Firstly must I say the fix was found in one of the posts here and it relates to the newer version of Windows 10.

I have an old Mbox 2 and had an old PC from work which I was using to load pro tools First.

Came across the same issue as some here whereby Pro rools would moan about user privileges nor sufficient to load a low level driver.

On installing the ilok drivers from the Old Installers folder, same thing happened to me, BSOD in windows 10 and was related to the TPkg.sys file that has been mentioned here.

I had also been using a laptop with the hardware and had no past issues until I built this PC. I though it was the age of the PC then found this post.

The fix was to download an older version of windows 10 and reimage the whole computer using this. I noticed my laptop was on an older build which ties in to what others have been saying about Interactive desktop being disabled on new builds causing issues.

After that I installed the ilok drivers straight after the re image and then they worked fine. I then upgraded through normal windows update and now all is working fine.

for reference I used Windows 10 1703 build which is the Creators Update.

I had the luxury of being able to reimage and it fixed my issue.

Hope this helps someone who is having similar issues and thanks to the commenters for the help with this

Rob

[kevindubois]

Wow!! That's amazing! I'm so glad somebody figured out a workaround for this, thank you for sharing! For anyone else stuck in this situation, hopefully this works for you, and I'm glad we were able to help out the community in some way!