Lazybit

If you're someone who checks the system logs every now and then, to make sure things are running smooth - you may have noticed some errors related to Private Disk:

The PRVDISKAMD64 service failed to start due to the following error: The system cannot find the file specified.

The program works fine, despite these log entries.  The error is not critical and it has no impact on the program's functionality. But why is it there? And what does it mean?

Private Disk comes with several flavours of drivers - 32-bit and 64-bit. Upon installation, both driver types are registered, but only one of them is successfully loaded by the system.

The other type, which is not compatible with the platform, fails to load - hence the log entry is generated.

In other words, you can simply ignore these notifications.

This behaviour will be changed in the next release, so the system won't bother loading modules that are not designed for it. Until then, here is a simple solution:

1. download Autoruns from Sysinternals
2. run the program and switch to the Drivers tab
3. find the drivers the pubisher of which is Dekart
4. uncheck the versions that do not correspond to your system
5. the new settings will come into effect after a restart

On choosing the entries:

• if you have a 32-bit (x86) system, disable the ones ending with "amd64"
• for 64-bit platforms, disable the other ones (as in the example below)

What the modules mean:

• pdfilter - Disk Firewall, the application-layer access filter;
• prvdisk - virtual disk driver (the thing that makes the encrypted drive show up in My computer as a regular disk);
• prjndl - the disk encryption driver that implements AES-256 in CBC mode, our NIST-certified implementation of it.