Fatal boot error caused by ILok driver

Audio Plugin Hosts and other audio software applications discussion
RELATED
PRODUCTS

Post

Hi!

I want to share a really bad experience I had recently with my PC, and i'm sure that many of you have seen this mentioned on other pages or even had it yourself. Is about the PACE license support, used by many softwares, being the most notorious Pro Tools and AIR Music Technology.

It's no secret that Microsoft has become extremely demanding about software compatibility with Windows 10, especially with drivers; In the world of technology, Microsoft's history is well known fighting with all kinds of licensing and copy protection systems, from constantly active game protection drivers taking resources (EA electronics as always), to buggy DLLs for features that no one needs or wants, and ending with the theme of this post: PACE or ILok license SUPPORT.

I will explain my situation: 2 days ago, I installed a plugin that needs ILok to be authorized, and right after installing everything worked well, without errors. One day passes and all good, Windows boots smoothly and the plugin works very well. This morning, I woke up and turned on the computer to start working on a song and it happened... Blue screen of death; The problem? this file "tpkd.sys", along with the code "PAGE ERROR ON NONPAGED AREA" (common in problems with the driver). Seeing this, I did the normal thing when a driver fails: Boot into safe mode and remove it, but even in that mode the blue screen still appears. I tried all the other ways because I had to start up to see what that damn file was. I had no choice but to google the file and what was it? The ILok system driver file...

Under this circumstance where it cannot be booted, the system cannot repair, and there is no way to run official fixers, the logical thing to do was to boot from the Windows installer and repair the computer, right? No, that's useless too. The worst part is that in almost every forum, including the Microsoft forum, people gave the same answers:
  • Reinstall Windows
  • Reinstall Windows
  • Start from Safe Mode and uninstall the driver
  • Reinstall Windows
  • Run ILok installer to fix the driver
  • Reinstall Windows
  • Recover from an image
  • Reinstall Windows
  • Reinstall Windows
  • Reinstall Windows
That was disappointing, because I'm not formatting my entire PC just for a single driver that doesn't work properly, and as some of you should experience, it's frustrating to even think about wasting days or weeks. So I asked my father for help and he gave me the tip he needed, and how he fixed 80% of the Windows driver failures: Delete each corrupted file one by one manually. And that's what I did, I took a Linux installation on a thumb drive and booted from there, opened my hard drive, searched for the "Tpkd.sys" file on System32 (The folder where windows has all the vital working files), deleted it, rebooted it and voila!... Windows started immediately without any error, and the hole process only took 5 minutes, just like that! no reinstallation, no wasting time, just going straight to the file and deleting it. Why isn't this mentioned as the first solution? I'd like to know that too.

Therefore, seeing that many people ask for help on how to solve this same problem, without any positive response from the specialists, I decided to make a complete detailed guide on how I did it, leaving links to all resources. This will work for ALL driver or program issues that lock your system to boot or work properly.

IMPORTANT NOTE, PLEASE READ:
  • If you do not have minimal knowledge about computers, do not attempt to do so yourself.
  • You will be interacting with vital file systems, so you will need to focus on what you touch or delete because a bad action can make the damage to your system worse.
  • Make sure that the problem you are having can be solved by deleting the driver, other than touching the Windows home folder.
  • Before doing anything, do the research about your issue the best you can, look for locations, fails, filename, extension, everything; Don't leave anything that could slow you down.


With nothing more to say, let's start with the tutorial:


Important information

For this process you will need a laptop or a computer from where you can download and create all necessary resources. The default location of all drivers in windows is "C:\Windows\System32\drivers", and is the same location of the ILok driver. This folder is the same for 32 and 64 bits systems.

Image


About Linux

NOTE: I know, many people is afraid of the difficulty and entanglement of Linux, and they have reasons; Because of that, in this post i'll be explaining ONLY the essential things.

To give a brief explanation, Linux is not a OS itself, is the core or what is called "Kernel" and acts like a universal engine that you can install on any car body. The distributions or "Distros", are systems built by companies and other persons using Linux as heart of the OS; This distros can are different of each other by many ways, added features, special functions, extra programs, but all of the distros share the same Linux core. Due to this there's a ton of distros available for every kind of needs and workload.

I've chosen the easiest and the best distro available: Linux Mint. The first step will be downloading the install image from the official website:

https://linuxmint.com/edition.php?id=281
Image

In the page there's a list with a lot of mirror links available, choose the World mirror or the closer to your location for better download speed.

Creating a Linux bootable USB drive:

After having the image downloaded, you need to create the USB drive from where you will boot Linux mint. For this you will have to download Rufus, a small program that creates bootable USB drives with all kind of images and file systems. The download link is available on their official website:

https://rufus.ie/
Image

Select the Portable edition and download it. After having the following file: rufus-3.12p.exe (the version can change with any future updates of Rufus), Execute it and will ask you if can it search updates online, press Yes and the main window with all the options will appear.

Image

Click on SELECT, and locate your Linux mint iso.

Image

After having the .iso loaded, click START and you will get a message asking you to allow the download of necessary libraries for the process; click Yes and immediately you will get another message asking you te select the mode of the image: select DD mode and then OK.

Image

Image

Accept the next message advising that the USB drive will be formatted and the process will start. After the process finished, extract the USB drive and insert it on the computer to be repaired.

Image

Image


Deleting driver manually

This process was made on a Virtual Machine created for testing; This processes are the same on all computers, the only things that can change are the keystrokes to select the boot device on startup, it depends of the manufacturer of the board and the model.

To boot to the linux USB, insert the thumb drive on the computer, start it and inmediatelly press the keystroke to enter the boot device selection:
  • Esc for HP
  • F12 for Acer
  • F8 or Esc for Asus
  • F12 for Dell
  • F12 or F10 for Lenovo
  • F11 for Msi
  • F10 for Asrock
After you've selected the USB drive as boot device, the Linux mint boot menu will appear; you don't need to touch anything, just let the boot countdown finish and linux will start automatically:

Image

With the system booted and loaded, go the the top-left corner and double-click on the "Computer" icon to open the main disk, from where you'll select your Windows drive; In my case is "VBOX HARDDISK", on your computer can be named "Local disk":

Image

Your directory should look like this:
Image

After getting into the Windows drive, go to "Windows -> System32 -> drivers", and locating the file you want to delete (In case you want to delete other driver, for this guide is "tpkd.sys") by typing the name with your keyboard, the search box will appear automatically on the bottom-right corner of the directory window

Image

With the driver located and selected, left-click the file and delete it:

Image

Now the only thing left is restarting, removing the USB drive and waiting for Windows to load:
Image
Image


FINAL RESULTS

Now Windows is booting and without errors or blue screens!!

Image
Image
Image


I hope this was useful to you on fixing your problem. If you have and doubt or question about this or any other problem, please contact me via private message.
Last edited by nucleox on Sat Nov 13, 2021 5:24 pm, edited 1 time in total.

Post

Thank you! I'm hoping that using an installation media will work, if I view the files from the command prompt via notepad? I don't have another computer to install linux mint nor do I have another USB drive because I need this one to gain admin privilege on certain computers to make music on them at school...

Post

I tested my method, and it worked! You can delete the tpkd.sys file by using windows 10 installation media, typing shift+F10 when in the install page, and typing "notepad" in the command prompt. Then you press file, open, and go to c drive, windows, system 32, and drivers then find that file, press del or right click and delete. Boom! Fixed. Thank you for this!

Post

Don't blame windows blame PACE, Pro-Tools and all the jerks who make and develop those products. They are A1 trash.

Post

Nobody's blaming Windows

Post

Ah, reminds me of good old Starforce days.

Post

The main problem with AIR iirc is that a lot of the older air installers auto installed an older version of PACE which is the thing crashing windows, not the new PACE driver. They have been slowly releasing new installers, but not all their stuff is ready (although I just checked and it looks like Transfuser, Vacuum pro, and Xpand have new installers now, which are the only three products of theirs I actually use)

Post

ShawnG wrote: Sat Apr 24, 2021 9:39 pm The main problem with AIR iirc is that a lot of the older air installers auto installed an older version of PACE which is the thing crashing windows, not the new PACE driver. They have been slowly releasing new installers, but not all their stuff is ready (although I just checked and it looks like Transfuser, Vacuum pro, and Xpand have new installers now, which are the only three products of theirs I actually use)
Yeah that happened to me. Stupidly, their installer doesn't even give you the option to not install iLok, meaning if you have a newer version already installed, it will get overwritten by the outdated version provided by Air. I think Sonivox does the same thing, they're the same company anyway (inMusic).

I suppose one workaround might be to uninstall iLok after installing the plugin, but before rebooting the system. Haven't tried that myself, though. Then you should be able to reboot and install the latest version of iLok (which works fine).
Take a single oscillator, producing a drone. Send it to the wave shaper, altering the tone.
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care

Post

Blue screen of death; along with the code "PAGE ERROR ON NONPAGED AREA"
Had this error too on Windows start up suddenly and it turned out the problem was the USB-Hub with the dongle didn't had enough power, i just grabbed an active hub which i had on my other computer and (without doing anything else on the system) the error was gone.
Image
Intel® Core™ i9-9900K•Cubase 11•Presonus Eris E8 XT•Focusrite Scarlett 18i20 & Octopre•NI Kontrol S61 MK2•Stein­berg CC121•Synthesizers: Arturia Casio Korg Roland Yamaha

Post

Thanks so much! I had just spent 7+ hours installing programs and reorganizing my system -- was not looking forward to a system restore or wipe.

For me I didn't go the Linux route - safe mode wasn't working either. So load up command prompt, find your drive (type 'dir' - if it isn't your Windows 10 drive type 'C:', dir, D:, dir, etc. until you find it). Then navigate via

cd windows
cd system32
cd drivers

(or cd windows/system32/drivers if so inclined)

and delete that stupid tpkd.sys file by entering

del tpkd.sys

type 'exit', restart, voila!

Typing this on my computer whereas I was reading this post on my phone. Screw the company that did this - I doubt the software was even worth this trouble.

Post

Hello everyone! sorry for not answering your questions before, my computer just died in the worst moment but anyways; About your questions on using CMD of windows setup, Yes, it's possible to do so and is the fastest way, but it's kind of a tricky thing for those with no advanced knowledge about computers, besides, doing the search on the drive is much faster, comfortable and failproof in Linux. Is a personal choice of course.

The other thing that can come out with using CMD is that if the .sys file for some reason is corrupted, infected with virus or maybe destiny hates you and the HDD has that exact sector damaged / blocked (Which happens very rarelly), the windows CMD will not be able to access the file due to the damaged NTFS record; Problem that doesn't affect linux, it can access and delete any file as long as the drive is on good health.

I've recieved via private messages a good amount of questions asking for problems which i didn't covered on this thread, so for that i'll move and update this thread to the Forum of Computer Setup and System Configuration, with new methods and workarounds for common issues, so, if you can put here your sugestions on what should i add and solve would be greatly appreciated.

Cheers! stay safe.

Post

I used to use Puppy Linux to fix windows a lot, super light weight.

Post

This happened to me, with softube installers .

I got a reply from iLok support which says......

"Hello,

The tpkd.sys driver is a very, very old legacy driver of ours. Support for this driver is no longer available, as it has not been actively developed for some time.

If this driver is being installed as part of a product's installation, please contact the software developer of that product to request an updated version that no longer uses our legacy driver.

If use of our legacy driver is required, you may not want to upgrade to the latest versions of Windows 10 which causes this behavior. You may also want to considering using a previous version of Windows that is not 10.

Finally, understand that the software publishers are the only ones capable of licensing their products. We at PACE merely build the infrastructure for the software publishers to distribute their products in the way that is consistent with their licensing terms."

---------------------------------------------------------------------------------------------------------------

To date, I have had no response to the sternly worded email I sent to softube.
If any Softube employee happens to be reading this, your company sucks, and I will never buy from softube again, and I offer the suggestion that softube sets up some kind of customer support department like any other responsible VST developer instead of only giving a damn about customers when trying to sell them things.

Post

The current Softube installers don't use such old ilok software....

Post

rasmusklump wrote: Wed Sep 01, 2021 2:09 pm The current Softube installers don't use such old ilok software....
They actually do. They also install some weird thing called a "helper". All softube helped me with was pointing me in the direction of a BSOD which cost me a few hundred quid in repairs. They couldn't even reply to an email. That's how much help they were !!

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”