No matter what program I try and install if it uses PACE I get the blue screen after install when I reboot my machine.

I'm using Windows 10 (fully uptodate with correct updates and system drivers)

Has anyone else encountered this and found a way to make it work?

 

Im assuming you're trying to install unofficial software (lifetime trial) did you had official software installed that uses pace? before? second did you disable av, disconnect from the web while you try to install the software

 

I've dealt with this on ALL new Windows 10 systems I have built in the last 6 months. A Windows update from a few months ago causes the whole OS to crash if an old version of Ilok licnese manager is installed. I have posted steps below to fix this:

Since you wont be able to get into the Windows OS once you boot up your computer (you'll get a crash/blue screen) you'll need to remove the offending ilok driver from the Windows system folder. Below are the 4 methods for fixing the problem. Once you've determined which will work best for you, follow the procedure at the bottom of the post to fix your windows installation.

Here are the 3 methods:

1. you can Install a linux distro to a usb thumb drive. I recomend using the linux distro "WindowsFX" as it is basically is a windows 10 style clone that you can run from the flash drive. This will make it easier for windows users who are not familiar with linux to gain access to the files on the bricked windows OS drive. Here is the site to download WindowsFX: https://linuxfx.org/

After downloading the WindowsFx distro, Google "how to install linux distro using rufus" this will give you instructions on how to get it on the thumb drive. After successfully creating the WindowsFx usb you can use the proccedure at the bottom of this post to fix your windows installation.

2. You can take the hard drive you installed the Windows OS on, and connect it to another computer as a secondary drive, either directly with Sata cables, or buy an external enclosure and connect a drive to a working computer. Once the drive is connected to the working computer, you can uses the instructions below.

3. You can use a system restore point to before you installed the offending program. If you can successfullyuse a restore point, skip to the "IMPORTANT INFO" section below.

4. You can reinstall windows and start from scratch, avoiding the problem in the future. This is method will delete any programs you have installed on the drive, so this method is NOT recommended if you have important data, or want to save your system as it currently is. If you choose this method you can skip to the "IMPORTANT INFO" section below.


Ok here are the steps to fix the problem and restore windows to working order:

1. Once you have access to the bricked windows drive using either method 1 or 2 above. You will need to navigate to the following folder on the drive: *name of drive*\Windows\System 32

2. There will be a file in the system 32 folder named "TPkd.sys", delete this file. This is the legacy ilok driver that is causing the BSOD.

3. Once that file is deleted you should be able to boot into windows again, without the Blue Screen of Death.


IMPORTANT INFO:

This problem is a bug caused by a Windows 10 update that causes system incompatablity with OLD ilok drivers. If you install a legacy ilok driver, its installs TPkd.sys into the System 32 folder, and when you restart the computer the computer Windows tries to load TPkd.sys and you'll get a BSOD.

In order to ensure this doesnt happen again, be sure that when you install older applications that also try to install "pace drivers" or "ilok license manager", DO NOT accept the pace or ilok installation. Instead cancel that portion of the installation and install the software ONLY. If required to install the pace license manager, make you do NOT restart your computer before navigating to the system32 folder and deleting the TPkd.sys file. This does NOT apply to newer programs or updates from ilok over the last year or so.


-Peace

 

Last edited: Jul 22, 2021

Thanks for the replys, much appreciate it.

I do not think I have PACE on my system before although I do have legit Cubase Pro 11 and that uses eLicenser.

I was able to access the repair windows screen and then did a system restore so no issues with using my machine now.

It is just that I have tried to install two programs (sister site) that use PACE and had the same blue screen issue with both....

 

@belinea2010 Can you name the software you tried to install? ex: softube EQ v12345

 

Read my post above, especially the section: "IMPORTANT INFO"

It will expain what the problem is, and how you can successfully install the programs WITHOUT crashing your system.

 

THANK YOU - it all works perfectly.

The main one was AU's PTs 12.5 seems to run perfectly so far.

the other was a Sonivox VSTi also seems to be working fine.

Thanks again everyone

 

Again and again I say it and again and again nobody hears it.
Since more than two years I disabled any kind of updates (Win 10 pro).
My computer work with countless VST's (legit or cracked) flawless.
I install and uninstall any kind of shit without any problems.
Stop the update-paranoia and enjoy your computer without surprise-troubles.

 

The above section is in a color that is almost impossible to see on my screen ...

Thanks for the info - I have saved it for reference just in case i forget and get a TPkd.sys in my system32

 

Thats weird, I fixed the text issue. Your welcome.

 

I agree. Stop windows updates if you want to run a stable machine, only update if you have a need to, and understand the implications of the update.

 

When I say updated I meant essential system drivers.

My machine is a custom build fully optimised DAW

 

https://www.sordum.org/9470/windows-update-blocker-v1-6/

 

I had this issue also with a legit pace software bundle. Did the remove the TPkd.sys trick and never installed that shit again.
I had freaking dongles and software protection.
Anyone who thinks this doesn't slow down your PC is dumb. Because it's and extra process and task you computer has to do.
Yes it might be a millisecond or two but how many times is it checking one twice, or over and over.

 

You mean rather "unoptimized"?

 

*sigh

The tolls waving thier todgers around have to infest any thread because thier own lives are so empty and dull...

Run along little dweebs and go back to playing with your self in your dark corner.

 

I had the same problem a few months ago, startkid84 is correct. I have an eleven rack from Avid, and the preset editor to use on windows 10 in sync with the unit needs an ilok/pace drivers. It installs the old ones by default and then boom, blue screen loop. Windows 10 and new updates aren't the culprit, Avid is. They're guilty for not fixing and updating their software, and for stopping support on perfectly, still usable hardware.

But, as startkid84 said, whatever you're installing, when it gets to the point it asks you to install the ilok/pace drivers, cancel it, or, if it doesn't let you cancel, let it install, but don't reboot! Uninstall the ilok right away and install the new version downloaded from Avid's website.