Drive Letter Conflict: Windows Operating Systems - Kingston Technology IronKey Vault Privacy 50 Bedienungsanleitung

Help and Troubleshooting

Drive Letter Conflict: Windows Operating Systems

•
As mentioned in the 'System Requirements'
section of this manual (on page 3), the
VP50 requires two consecutive drive letters
AFTER the last physical disk that appears before
the 'gap' in drive letter assignments (see Figure
9.10.) 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
VP50 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.) As
mentioned in the 'System Requirements'
section of this manual (on page 3), the
VP50 requires two consecutive drive letters
AFTER the last physical disk that appears before
the 'gap' in drive letter assignments (see Figure
9.10.) 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.
In this example (Figure 9.10), the VP50 uses drive F:, which is the first available drive letter after drive E: (the last
physical disk before the drive letter gap.) Because letter G: is a network share and not part of the hardware profile,
the VP50 may attempt to use it as its second drive letter, causing a conflict.
If there are no network shares on your system and the VP50 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 Drive Letter Management, or DLM, has improved significantly in Windows 8.1,10 and 11 so you
may not come across this issue, but if you are unable to resolve the conflict, please contact Kingston's Technical
Support Department or visit Kingston.com/support for further assistance.
Figure 9.10 - Drive Letter example
31