|« Amazon negative feedback removal tips||How to generate a system report »|
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:
On choosing the entries:
What the modules mean:
This post has 27 feedbacks awaiting moderation...
2g 3g 64-bit authentication beta biometry «blue screen» brute-force bsod business driver email encryption «file system» flash form-filling gsm howto internet keeper keylogger logon microsim mobile password «password carrier» portability privacy «private disk» recovery release security seven sim «sim card» «sim manager» «sim reader» «smart card» sms software tips token troubleshooting usb usim vista voyager windows wiping xp