USB storage device no longer functions after upgrade from Windows 2000 to Windows Server 2003 (330050)



The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, 64-Bit Enterprise Edition
  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Small Business Server 2003, Premium Edition
  • Microsoft Windows Small Business Server 2003, Standard Edition

This article was previously published under Q330050

SYMPTOMS

After you upgrade from Windows 2000 Server to Windows Server 2003, a USB storage device that is connected to your computer may no longer function. Additionally, a duplicate USB storage device may appear in Device Manager and in the Removable Storage snap-in.

CAUSE

This problem occurs because Windows Server 2003 creates an instance ID string for the USB storage device that does not match the instance ID string that Windows 2000 created for the USB storage device.

In Windows Server 2003, if the USB storage device has a USB serial number string, the Usbstor.sys file creates a unique instance ID string for the USB storage device. The instance ID string that Windows Server 2003 creates is different than the instance ID string that Windows 2000 created. As a result, Plug and Play adds the USB storage device to the computer as a new device and uses the new address assignment to communicate with the USB storage device. Because of this, the address assignment from Windows 2000 no longer matches any device that is connected to the computer, and the Windows 2000 copy of the USB storage device appears disabled in the Removable Storage Manager snap-in.

WORKAROUND

To work around this problem, log on to the computer as a member of the Administrators group, and then use the Removable Storage snap-in to delete the disabled copy of the USB storage device.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MajorLast Reviewed:11/12/2004
Keywords:kbbug kbpending KB330050