Filter
Top Products
Drive Letter Conflict
[Back to top]
The DTVP-M requires two consecutive drive letters AFTER the last physical disk that appears before
the ‘gap’ in drive letter assignments. This does NOT pertain to network shares because they are
specific to user-profiles and not the system hardware profile itself, thus appearing available to the OS.
What this means is, Windows may assign the DTVP-M a drive letter that’s already in use by a network
share or Universal Naming Convention (UNC) path, causing a drive letter conflict. If this happens,
please consult your administrator or helpdesk department on changing drive letter assignments in
Windows Disk Management (administrator privileges required.)
Figure 1.12 – Drive Letter Assignment
If there are no network shares on your system and the DTVP-M still won’t load, it is possible that a card
reader, removable disk, or other previously-installed device is holding on to a drive-letter assignment
and still causing a conflict.
Please note that native Drive Letter Management has improved significantly in Windows XP SP3, Vista,
and 7, so you may not come across this issue, but if you are unable to resolve the conflict, please
contact Kingston’s Technical Support Department for further assistance.
[Back to top]
DTVP-M Help DataTraveler
®
Vault – Privacy Managed Page 6 of 6