Article ID: 836662
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
A Microsoft Windows 2000-based computer may incorrectly assign duplicate drive letters to a single universal serial bus (USB) floppy drive when you attach the USB floppy drive to the computer and then restart the computer. Windows Explorer may display duplicate drive letter icons for a single USB floppy drive, and one of the drive letters may not be valid for the USB floppy drive.
CAUSE
This problem occurs because of a synchronization issue between the Windows 2000 kernel and the MountMgr.sys driver. When you attach a USB floppy drive to a Windows 2000-based computer, Windows 2000 uses the following procedure to assign drive letters to the USB floppy device:
- When the computer starts, Windows 2000 enumerates the USB floppy disk drive.
- During system initialization, the Windows 2000 kernel calls the IoAssignDriveLetters function to grant drive letters to all present storage devices, such as hard disks, CD-ROM drives, and floppy drives.
- To assign the drive letters to the devices, the IoAssignDriveLetters function calls the HalpNextDriveLetter function to assign a drive letter to the USB floppy drive.
- The HalpNextDriveLetter function tries to call the HalpSetMountLetter function for the USB floppy drive and issues a IOCTL_MOUNTMGR_CREATE_POINT command to assign a drive letter.
- The MountMgr.sys driver uses the IOCTL_MOUNTMGR_CREATE_POINT command to create the mount point for the USB floppy device, but the driver cannot assign a drive letter because, when the MountMgr.sys driver tries to call the IoGetDeviceObjectPointer function for the USB floppy drive, the procedure fails. The failure occurs because the USB floppy drive still has the DO_PENDING_START flag set. The DO_PENDING_START flag means that the USB floppy device has not yet responded.
- Because the HalpNextDriveLetter function cannot assign a drive letter with the IOCTL_MOUNTMGR_CREATE_POINT command, the HalpNextDriveLetter function calls the IoCreateSymbolicLink function and creates a symbolic link for the drive letter that has no corresponding registry entry. This letter is the first drive letter that is assigned to the USB floppy drive.
- After the symbolic link has been created, the MountMgrMountedDeviceArrival function is called to notify the MountMgr.sys driver that the USB floppy drive has arrived.
- The MountMgr.sys driver is unaware of the symbolic link that is created by the HalpNextDriveLetter function, and therefore the MountMgr.sys driver assigns the next available drive letter. This letter is the second drive letter that is assigned to the USB floppy drive.
After you apply this hotfix, the MountMgrMountedDeviceArrival function checks for an existing USB floppy drive that has the same symbolic link as the one that is arriving. If a symbolic link exists for the USB floppy drive, but no corresponding registry entry exists for the drive letter, the previously assigned symbolic link is removed, and the MountMgrMountedDeviceArrival function assigns the drive letter correctly.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 10-Feb-2004 19:47 5.0.2195.6897 30,160 Mountmgr.sys
WORKAROUND
To work around this problem, follow these steps:
- Make a full system backup of the computer and system state.
- Log on as administrator.
- Click Start, click Run, type regedt32.exe, and then click OK.
- Locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices - Click MountedDevices, and then click Permissions on the Security menu.
- Verify that the Administrators group has Full Control permissions.
Note If the permissions are modified, make sure that they are returned to their original settings. - Quit Regedt32.exe.
- Click Start, click Run, type regedit.exe, and then click OK.
- Locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices - Find the drive letters that overlap. For example, if "B:" overlaps, find "\DosDevices\B:", right-click "\DosDevices\B", and then click Delete.
Note You must use Regedit.exe instead of Regedt32.exe to delete this registry key. - Quit Regedit.exe.
- Click Start, click Run, type regedt32.exe, and then click OK.
- Locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices - Change the permissions back to the previous settings for the administrators group.
- Install the hotfix that is listed earlier.
- Restart the computer.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB836662
