PD Explorer is a free tool that enables you to explore Private Disk encrypted images even in the cases when Private Disk is not installed on the computer, even if you don't have administrative privileges.
You can view the contents of the encrypted disk, write or remove files from it - as you can normally do with an archive such as a ZIP file.
It is extremely simple in use, making it easy to add new files to the encrypted vault, delete or update existing files.
PD Explorer is compatible with NTFS images of any size, there are no file size restrictions, nor are there limitations about the maximum number of files that can be processed.
PD Explorer is a available for free, you can download it right now.
Most of us think that we're stuck with the letters assigned to the partitions by Windows - and that cannot be changed. C: will always be C: and D: will always be D:, etc.
If you are a Private Disk Light user, you may run into a problem - the disk cannot be mounted, because the letter it was supposed to be mapped to is already in use. Since Private Disk Light doesn't allow you to change the disk letter of the encrypted disk - you cannot access your data. There are several solutions to this problem.
Make sure the letters are available
Use the standard Disk Management tool (Start\Run\diskmgmt.msc) to modify the drive letter of an existing partition. You will see that letters can be changed at will, unless you're trying to change the letter of the system disk (in this case you will be trying to cut off the branch upon which you are standing).
Note that if you use NTFS, the partition can be mapped to a folder on another NTFS drive, not necessarily to a letter. Also, some partitions may not have a letter or a folder to which they are mapped - of course, the obvious disadvantage is that you won't be able to access them.
Install Private Disk (the non Light version)
With Private Disk, you get a lot of other security features, as well as many other handy features - among them is the possibility to edit the settings of an image and change its disk letter.
This approach is the opposite of the one. In the previous case we make available the desired letter, while in this one we "desire another letter".
You don't have to actually buy the program, you can make the changes while still in the trial mode (which is fully functional), and then go back to Private Disk Light. If you decide to stick to the full version, don't forget that you can get it for a discount.
Private Disk Explorer
PD Explorer is a new tool that is perfect for this job, if what you need is to simply extract the files from an encrypted image. Note that PD Explorer works with NTFS images, so it is not applicable if you have FAT32 or another file system.
This encrypted image browsing tool is not yet officially released, but you can get a copy from our forum.
Use another computer
Private Disk and Private Disk Light are both portable programs - they can run from removable disks without installation enabling you to encrypt a USB flash disk or a CD; all you need is another computer on which the disk letters you need are not in use.
It has been reported that in certain circumstances the system will shutdown instead of rebooting itself when the user restarts it while Private Disk is running and an encrypted disk is mounted.
This was a problem difficult to trace; while it repeats itself 10/10 times on a "problematic" machine, on "non-problematic" ones everything is working correctly and it is impossible to simulate the problem.
This is what makes it of reason to make an educated guess that this is caused by a third-party component present on the system, which somehow alters the standard behaviour of Windows. The tough part is that even when you think you have disabled all the non-standard programs, there is a myriad of low-level components that one can't see with the naked eye.
I am on Private Disk v 2.09. I close my files and every time I try to disconnect a drive letter I get the message:
There are files currently opened on disk Z:\
I feel that my data is not closing correctly. My question is how do I find out what file(s) are still open and how do I close them?
Quite often a volume can be used by a service, or another process that is running in the background - which makes it difficult to detect. In such cases, the best approach is to use a tool that monitors all the file activity that goes on in the system, and examine the list of processes that interfere with files located on the specific volume.
One such tool is Process Monitor; among many things, it can show which programs are working with data on a specific volume.
All you have to do is close these programs, and try to dismount the volume again.
If you see an unknown program accessing the volume, and you don't know how to close it (or you are not sure whether "killing the process" will have any serious consequences or not), look up the name of the program in a search engine and that will give you enough details to make a correct decision.
Earlier I explained how blue screens of death can be countered, today I will describe an alternative approach, which achieves the same result using different means.
Normally, the blue screen of death contains a driver name, and some addresses; if you're lucky, removing that driver will do the trick. But what if there is no driver name on the BSoD? And what if you don't have all the skills to play with crashdumps and debuggers?
In this case, Autoruns comes to the rescue. This is a graphical tool that allows you to disable/enable drivers in a very easy way.
The steps above will be repeated until the system is able to boot correctly.
When that happens, remember what were the last changes you applied, and try to enable some drivers back - until you figure out which one of them was causing the issue.
The advantage of this method is that you can keep unchecking drivers without knowing what they do, because undoing any change is as easy as checking an item back (this is one of the coolest things about Autoruns).
What makes a driver suspicious?
When temporarily disabling a driver, you are not yet sure whether the driver in question is the culprit, so an educated guess is your best option. Start by unchecking:
In the example above, I highlighted Private Disk's drivers, you can see the description and the vendor name - this illustrates how one can easily spot the modules related to an application.
Note: if you have a driver from 'Micr0soft' or "MlCROSOFT" (i.e. something that mimics the name of a well-known vendor), it is most likely a piece of malware, so you should not only disable it, but also figure out how it got in your system in the first place.
How to find the blue screening driver faster?
Usually one's technical knowledge provides sufficient data for a good guesstimate, but what if you have no clue where to start, and there are a lot of suspect items? In this case, try the binary search:
The trick is in narrowing down the problem to as few items as possible. At each step the list of suspects is cut in two, so eventually you are left with one single item.
How to tune my Windows performance with Autoruns?
If you switch to the other tabs, you'll see a lot of other stuff that loads automatically when the system boots (drivers, services, applications in the registry, various shell extensions, etc). You can go ahead and uncheck the items that look suspicious - this will cut boot times, and make the system faster once it is loaded (since less stuff is loaded into RAM).
Beware of the fact that if you uncheck the wrong stuff, certain functionality will be lost, and the system may become partially unusable. Therefore be careful with the changes you apply:
Sometimes the standard behaviour of the Windows OS annoys the end user - this story is about NumLock and the fact that Windows sets it to an "off" state.
The easy way to make sure NumLock is automatically turned on when you logon is to
Next time you log on with your user - the state of NumLock will be set to the state it had when you logged off.
Now, that does work, but there is still another problem - when a user is not yet logged on, NumLock is off. The explanation is simple - since nobody is logged on yet, Windows does not know which user profile to use (this is the beauty of a multi-user OS).
To deal with this, follow these simple instructions:
An alternative is to create a .REG file with this contents, then merge it into the registry
Windows Registry Editor Version 5.00
2g 3g 64-bit «address book» authentication beta biometry «blue screen» bsod business driver email encryption «file system» form-filling «google contacts» gsm howto internet keeper keylogger logon mobile mobility password «password carrier» portability privacy «private disk» recovery release «reverse engineering» security seven sim «sim card» «sim manager» «sim reader» «smart card» software sync tips token troubleshooting usb usim vista windows wiping xp