by VistaFirewallControl » Tue Dec 21, 2010 11:36 am
The problem is common.
When a new device arrives Windows assigns new (so called) volume path to the device (i.e /device/TrueCryptVolumeX) each time. The volume path is volatile, so the next time device arrives the path would be /device/TrueCryptVolumeY. Then the mount manager trying to identify the device is able to assign the same drive letter (e.g X: ) to the device most probably and the user does not notice any mount related changes finally.
However W7FC (and the underlying security core) application permissions are set on Volume path basis. So W7FC must determine new device as “removable” first and if the arrived device is marked appropriately, W7FC just reassigns the same X:\...\xbmc.exe to the new volume path.
Without "removable" sign W7FC can not perform the trick. Reassigning all the W7FC listed applications on every new device arrival is too time consumptive unfortunately.