This DataTraveler requires two consecutive drive letters AFTER the last physical disk that appears before the 'gap' in drive letter assignments (see figure below).
This does NOT pertain to network shares because they are specific to user profiles and not the system hardware profile itself, and thus appear available to the OS.
This means that Windows may assign the DataTraveler 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 help desk department for information on changing drive letter assignments in Windows Disk Management (administrator privileges required.)
In this example, the DataTraveler uses drive F:, which is the first available drive letter after drive E:
(the last physical disk before the drive letter gap).
Since letter G:
is a network share and not part of the hardware profile, the DataTraveler may attempt to use it as its second drive letter, causing a conflict.
If there are no network shares on your system and the DataTraveler 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 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.
FAQ: KDT-011411-PRV-02