This is the talk page for discussing improvements to the USB mass storage device class article. This is not a forum for general discussion of the article's subject. | |||
|
| ||
Archives:1 |
WikiProject Computing / Hardware | (Rated C-class, Mid-importance) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
To disable a USB Mass Storage Device. Press Save/Recall key. Press Explorer.and navigate to D:AgilentService. Installing the generic USB Mass Storage driver. Download Windows 98SE Generic USB Mass Storage Device Driver to the desktop. Open Device Manager (right click My Computer - Properties - Device Manager) and remove ALL drivers for USB flash drives. This includes any drivers of removable devices previously installed from the “Disk drives” tree.
Mac OS 8.5.1 Driver Question[edit]
Apple Computer's Mac OS 8.5.1 supports USB mass storage through an optional driver. Can anyone provide any more information regarding this driver? Nerobert (talk) 20:23, 17 August 2010 (UTC)
xbox 360, playstation 3, etc. mass storage[edit]
I don't know about the others, but the Xbox 360 only works with the fat32 file system, unlike the other operating systems.
Hot unplug[edit]
Does it matter if you unplug a USB mass storage device without 'Safely removing hardware' or the like? What happens if you unplug one during a file transfer? I've never noticed any problems, but these kinds of problems are subtle — Omegatron 03:30, 10 December 2006 (UTC)
It does not matter if you remove it without 'Safely removing hardware'. Also if you unplug one during a file transfer the file will become corrupted, although I am not sure if it corrupts the original file. I definitely do not recommend unpluging it during a file transfer. 68.255.97.28 11:10, 26 June 2007 (UTC)
- well, i unplug one after playing maple (i install it into my thumbdrive) and the next time i plug it in, the file is gone! the folder says it's empty, including my phone's backup! someone please help. Ragnaroknike 15:21, 28 July 2007 (UTC)
You definitely need to use 'Safely remove hardware'. The operating system mantains a cache, and if you remove the stick before telling windows to flush it (via safely remove hardware) you can corrupt the entire filesystem. —Preceding unsigned comment added by 200.203.113.191 (talk) 16:25, 6 July 2008 (UTC)
- Windows 2000/XP uses Write Behind caching on removable media for some odd reason. Pulling the usb cable or even pulling the card out of the reader before making it 'safe' is a very bad idea. It is in my experience Windows will write 'most' of the data immediately, but last bits won't be written in much as a few minutes sometimes. Safeing it will cause the write cache to immediately and completely flush. Windows 98 doesn't use Write Behind caching on removable media by default and is generally safe the pull the usb after you 'think' the data is written. 66.114.93.6 (talk) 12:42, 26 July 2008 (UTC)
To see a drive's caching policy in Windows XP,open Device Manager > right-click a drive and select Properties > click the Policies tab. -- Insterested (talk) 01:00, 10 January 2009 (UTC)
Incorrect scale?[edit]
Is the scale to the right of the first image correct, seems like a long device to me. Judging by the Quarter used in the previous versions of the image, the length should be just above 80mm instead of 100mm. Bergsten (talk) 12:40, 17 November 2007 (UTC)
Limits ? Technical details ?[edit]
What is the maximum supported device capacity ? Is the protocol based on SCSI (similar to ATAPI) ? Also other details would be welcome.--Xerces8 (talk) 10:21, 5 March 2008 (UTC)
![How To Install Usb Mass Storage Device Driver Windows Xp How To Install Usb Mass Storage Device Driver Windows Xp](/uploads/1/2/6/3/126380407/165705275.png)
Generic driver[edit]
What is a generic driver?. --Mac (talk) 08:41, 13 May 2008 (UTC)
No backport to Linux kernel 2.2[edit]
The 'Unix-like' section incorrectly states that 'a backport to [Linux] kernel 2.2 has also been made'. 'Neither USB-Storage nor High Speed USB are supported in the 2.2 line of kernels.' - According to www.linux-usb.org[1]. Although some general USB functionality was back-ported to Linux 2.2.18+ ; I believe that to be the source of confusion.Madman420 (talk) 02:45, 12 May 2009 (UTC)
- There is a usb-storage driver since 2.2.18: http://lxr.linux.no/#linux-old+v2.2.18/drivers/usb/usb-storage.c
- I've added it as a reference. --scgtrp (talk) 03:18, 2 February 2011 (UTC)
Error in article regarding AutoRun[edit]
Malware and inherent vulnerability
Since Windows's AutoRun feature works indiscriminately on any removable media, USB storage devices became
This is not true. Windows XP does not use AutoRun/AutoPlay on USB flash disks at all. And I believe Vista/7 also asks before starting anything.--Xerces8 (talk) 21:09, 16 January 2010 (UTC)
- It does not use AutoPlay, but it continues to use autorun. Some malicious programs change autorun.inf so that double-clicking the drive, or right-clicking and selecting open causes it to run a copy of itself on the drive, which then performs the expected action.--195.194.111.196 (talk) 13:43, 19 December 2011 (UTC)
Reliability[edit]
![How To Install Usb Mass Storage Device Driver Windows Xp How To Install Usb Mass Storage Device Driver Windows Xp](/uploads/1/2/6/3/126380407/976472749.png)
Having used various external USB drives on various PCs / operating systems I have *always* found them unreliable on large, long-running data transfers. By large / long-running I typically mean using something like rsync to synchronise changed data between disks, either both USB on the same computer, or both USB on different computers across ethernet or one USB external and one internal (IDE or SATA).
Without exception, various error messages and 'hangs' start to occur after a while and either the rsync fails on lots of files or else the transfer rate slows down enormously because of OS delays while waiting for time-outs or 'resetting' hardware.
I never experience such problems with two internal IDE drives.
The conclusion is that there is something unreliable about implementations of USB when used for large / long-running transfers. Whether it is inherent in the USB protocol, or ubiquitous across operating systems' implementations (Windows 2K / XP / 7; various Linux) the effect is the same - USB is not reliable for large / long-running data transfers.
Why is this protocol problem never addressed in USB reviews? Or discussed in articles about the protocol? Such failures with primary, internal disks would be intolerable. — Preceding unsigned comment added by 86.179.113.26 (talk) 07:57, 12 June 2011 (UTC)
Windows 98SE[edit]
A forum member at msfn.org using the handle Maximus Decim has packaged the USB Mass Storage drivers from Windows Me into an installer for Windows 98 Second Edition English version. Other forum members have made versions for other language versions of 98 SE. 66.232.94.33 (talk) 03:23, 6 February 2011 (UTC)
- Why is there a reference and external links to Linux drivers but it is a sin to add either type for Windows 98SE drivers? I want clarification of why one O/S is important but another is not?
- A link to the Maximum Decim Generic USB Mass Storage Device Drivers should be included in this article, because Microsoft no longer support the operating system, nor did they include generic support.
- • Sbmeirow • Talk • 17:46, 19 December 2011 (UTC)
Linux USB info[edit]
https://www.technovelty.org/linux/what-actually-happens-when-you-plug-in-a-usb-device.html— Preceding unsigned comment added by Sbmeirow (talk • contribs) 04:22, June 20, 2014
- That's a good article, went ahead and added it as an external link. — Dsimic (talk | contribs) 17:09, 22 June 2014 (UTC)
External links modified[edit]
Hello fellow Wikipedians,
I have just modified one external link on USB mass storage device class. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20120331082549/http://eserver.livejournal.com/27707.html to http://eserver.livejournal.com/27707.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
As of February 2018, 'External links modified' talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these 'External links modified' talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template
{{sourcecheck}}
(last update: 15 July 2018).- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.--InternetArchiveBot(Report bug) 20:07, 5 April 2017 (UTC)
External links modified (January 2018)[edit]
Hello fellow Wikipedians,
I have just modified 2 external links on USB mass storage device class. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20050923210216/http://lxr.linux.no/ to http://lxr.linux.no/
- Added archive https://web.archive.org/web/20120207000458/http://sourceforge.net/apps/trac/smartmontools/wiki/USB to http://sourceforge.net/apps/trac/smartmontools/wiki/USB
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
As of February 2018, 'External links modified' talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these 'External links modified' talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template
{{sourcecheck}}
(last update: 15 July 2018).- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.--InternetArchiveBot(Report bug) 00:10, 22 January 2018 (UTC)
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Talk:USB_mass_storage_device_class&oldid=821681402'
-->This topic lists the Microsoft-provided drivers for the supported USB device classes.
- Microsoft-provided drivers for USB-IF approved device classes.
- For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
- For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).
If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.
If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.
USB Device classes
USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.
Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.
For general information about USB-IF approved device classes, see the USB Technology website.
For the current list of USB class specifications and class codes, visit the USB DWG website.
Device setup classes
Windows categorizes devices by device setup classes, which indicate the functionality of the device.
Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.
Two important device setup classes for USB devices are as follows:
- USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.
- USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.
The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.
Microsoft-provided USB device class drivers
USB-IF class code | Device setup class | Microsoft-provided driver and INF | Windows support | Description |
---|---|---|---|---|
Audio (01h) | Media {4d36e96c-e325-11ce-bfc1-08002be10318} | Usbaudio.sys Wdma_usb.inf | Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides support for the USB audio device class by means of the Usbaudio.sys driver. For more information, see 'USBAudio Class System Driver' in Kernel-Mode WDM Audio Components. For more information about Windows audio support, see the Audio Device Technologies for Windows website. |
Communications and CDC Control (02h) | ||||
Ports {4D36E978-E325-11CE-BFC1-08002BE10318} | Usbser.sys Usbser.inf | Windows 10 for desktop editions Windows 10 Mobile | In Windows 10, a new INF, Usbser.inf, has been added that loads Usbser.sys automatically as the function driver. For more information, see USB serial driver (Usbser.sys) | |
Modem {4D36E96D-E325-11CE-BFC1-08002BE10318} Note Supports Subclass 02h (ACM) | Usbser.sys Custom INF that references mdmcpq.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | In Windows 8.1 and earlier versions, Usbser.sys is not automatically loaded. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) and includes [Install] and [Needs] sections. Starting with Windows Vista, you can enable CDC and Wireless Mobile CDC (WMCDC) support by setting a registry value, as described in Support for the Wireless Mobile Communication Device Class. When CDC support is enabled, the USB Common Class Generic Parent Driver enumerates interface collections that correspond to CDC and WMCDC Control Models, and assigns physical device objects (PDO) to these collections. | |
Net {4d36e972-e325-11ce-bfc1-08002be10318} Note Supports Subclass 0Eh (MBIM) | wmbclass.sys Netwmbclass.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 | Starting in Windows 8, Microsoft provides the wmbclass.sys driver, for mobile broadband devices. See, MB Interface Model. | |
HID (Human Interface Device) (03h) | HIDClass {745a17a0-74d3-11d0-b6fe-00a0c90f57da} | Hidclass.sys Hidusb.sys Input.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the HID class driver (Hidclass.sys) and the miniclass driver (Hidusb.sys) to operate devices that comply with the USB HID Standard. For more information, see HID Architecture and Minidrivers and the HID class driver. For further information about Windows support for input hardware, see the Input and HID - Architecture and Driver Support website. |
Physical (05h) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
Image (06h) | Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} | Usbscan.sys Sti.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbscan.sys driver that manages USB digital cameras and scanners for Windows XP and later operating systems. This driver implements the USB component of the Windows Imaging Architecture (WIA). For more information about WIA, see Windows Image Acquisition Drivers and the Windows Imaging Component website. For a description of the role that Usbscan.sys plays in the WIA, see WIA Core Components. |
Printer (07h) | USB Note Usbprint.sys enumerates printer devices under the device set up class: Printer {4d36e979-e325-11ce-bfc1-08002be10318}. | Usbprint.sys Usbprint.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbprint.sys class driver that manages USB printers. For information about implementation of the printer class in Windows, see the Printing - Architecture and Driver Support website. |
Mass Storage (08h) | ||||
USB | Usbstor.sys | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbstor.sys port driver to manage USB mass storage devices with Microsoft's native storage class drivers. For an example device stack that is managed by this driver, see Device Object Example for a USB Mass Storage Device. For information about Windows storage support, see the Storage Technologies website. | |
SCSIAdapter {4d36e97b-e325-11ce-bfc1-08002be10318} | SubClass (06) and Protocol (62) Uaspstor.sys Uaspstor.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 | Uaspstor.sys is the class driver for SuperSpeed USB devices that support bulk stream endpoints. For more information see: | |
Hub (09h) | USB {36fc9e60-c465-11cf-8056-444553540000} | |||
Usbhub.sys Usb.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbhub.sys driver for managing USB hubs. For more information about the relationship between the hub class driver and the USB stack, see USB host-side drivers in Windows. | ||
Usbhub3.sys Usbhub3.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 | Microsoft provides the Usbhub3.sys driver for managing SuperSpeed (USB 3.0) USB hubs. The driver is loaded when a SuperSpeed hub is attached to an xHCI controller. See USB host-side drivers in Windows. | ||
CDC-Data (0Ah) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
Smart Card (0Bh) | SmartCardReader {50dd5230-ba8a-11d1-bf5d-0000f805f530} | |||
Usbccid.sys (Obsolete) | Windows 10 for desktop editions Windows 7 Windows Server 2008 Windows Vista | Microsoft provides the Usbccid.sys mini-class driver to manage USB smart card readers. For more information about smart card drivers in Windows, see Smart Card Design Guide. Note that for Windows Server 2003, Windows XP, and Windows 2000, special instructions are required for loading this driver because it might have been released later than the operating system. Note Usbccid.sys driver has been replaced by UMDF driver, WUDFUsbccidDriver.dll. | ||
WUDFUsbccidDriver.dll WUDFUsbccidDriver.inf | Windows 8.1 Windows 8 | WUDFUsbccidDriver.dll is a user-mode driver for USB CCID Smart Card Reader devices. | ||
Content Security (0Dh) | - | - | - | Recommended driver: USB Generic Parent Driver (Usbccgp.sys). Some content security functionality is implemented in Usbccgp.sys. See Content Security Features in Usbccgp.sys. |
Video (0Eh) | Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} | Usbvideo.sys Usbvideo.inf | Windows 10 for desktop editions Windows Vista | Microsoft provides USB video class support by means of the Usbvideo.sys driver. For more information, see 'USB Video Class Driver' under AVStream Minidrivers. Note that for Windows XP, special instructions are required for loading this driver because it might have been released later than the operating system. |
Personal Healthcare (0Fh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
Audio/Video Devices (10h) | - | - | - | - |
Diagnostic Device (DCh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
Wireless Controller (E0h) Note Supports Subclass 01h and Protocol 01h | Bluetooth {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} | Bthusb.sys Bth.inf | Windows 10 for desktop editions Windows 10 Mobile Windows 8.1 Windows 8 Windows 7 Windows Vista | Microsoft provides the Bthusb.sys miniport driver to manage USB Bluetooth radios. For more information, see Bluetooth Design Guide. |
Miscellaneous (EFh) | Net {4d36e972-e325-11ce-bfc1-08002be10318} Note Supports SubClass 04h and Protocol 01h | Rndismp.sys Rndismp.inf | Windows 10 for desktop editions Windows 8.1 Windows 8 Windows 7 Windows Vista | Prior to Windows Vista, support for CDC is limited to the RNDIS-specific implementation of the Abstract Control Model (ACM) with a vendor-unique protocol (bInterfaceProtocol) value of 0xFF. The RNDIS facility centers the management of all 802-style network cards in a single class driver, Rndismp.sys. For a detailed discussion of remote NDIS, see Overview of Remote NDIS. The mapping of remote NDIS to USB is implemented in the Usb8023.sys driver. For further information about networking support in Windows, see the Networking and Wireless Technologies website. |
Application Specific (FEh) | - | - | - | Recommended driver: WinUSB (Winusb.sys) |
Vendor Specific (FFh) | - | - | Windows 10 for desktop editions Windows 10 Mobile | Recommended driver: WinUSB (Winusb.sys) |