• Drivers Ms Auto Mobile Phones & Portable Devices 2017
• Drivers Ms Auto Mobile Phones & Portable Devices

W ith the Microsoft “Your Phone” screen mirroring app live on the Windows Store, Dell has now laid out its cards as well.The “Dell Mobile Connect app,” earlier only available for Dell. Drivers are constantly reminded not to use their phones while behind the wheel, but a new study reminds us just how dangerous it is. The National Safety Council's annual injury and fatality report.

-->

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

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 Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

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)

Related topics

Bereji­klian calls for crackdown on phone use while driving

A hi-tech camera which can detect people using their mobile phones while driving was trialled in Melbourne. Picture: Mark Stewart.Source:News Corp Australia

DISTRACTION is one of the leading causes of fatal road crashes in Australia but new hi-tech cameras that detect drivers using their mobile phones without them even knowing could soon change everything.

A New South Wales Police spokesman told news.com.au that officers currently “use a variety of methods to detect drivers using their phones while driving”.

“Line-of-site, by trained officers is the primary method of detection, however, long-ranged cameras have been used with success, and helmet cameras in motorcycle police continue to be used,” the spokesman said.

But that technology could soon be replaced by stationary cameras that automatically issue an infringement notice without the driver even realising they’ve been sprung.

NSW Police Highway Patrol boss, Assistant Commissioner Mick Corboy, told the Nine News there were “emerging technologies coming out”.

“So the way we are going to defeat this is by video evidence, by photographic evidence and we are looking at everything possible around the world at the moment and we think we’ll get something in place fairly quickly,” Mr Corboy said.

His comments came after NSW Minister for Roads Melinda Pavey put out a call on Tuesday for potential providers to present “practical, technology-based solutions to address the problem” of mobile phone use in cars.

“Developing this technology would be a world-first and is one of the priorities of our Road Safety Plan 2021 that we announced,” Mrs Pavey said.

A hi-tech camera which can detect people using their mobile phones while driving was trialled in Melbourne. Picture: Mark Stewart.Source:News Corp Australia

As part of the Road Safety Plan 2021, the NSW Government outlined its plans to implement legislative changes to allow camera technology to enforce mobile phone use offences.

Mrs Pavey said the Road Transport Legislation Amendment (Road Safety) Bill 2018 was introduced into the NSW Legislative Assembly on March 6, 2018. NSW is the first jurisdiction to introduce such legislation in Australia.

Last year, NSW Police handed out about 42,000 fines to drivers caught on their mobile phones, with the distraction increasingly emerging as a factor in fatal crashes over the past decade.

In February this year, serial texter Jakob Thornton, was allegedly engrossed in his phone when he ploughed into a roadside breath test in southwest Sydney, seriously injuring two officers.

Senior Constable Jonathon Wright had his foot and part of his lower leg amputated and Senior Constable Matthew Foley suffered a broken leg.

NATIONAL SNAPSHOT

Alex McCredie demonstrates how the hi-tech cameras that can detect drivers using mobile phones work. Picture: Mark Stewart.Source:News Corp Australia

According to National Road Safety Partnership Program (NRSPP) Manager Jerome Carslake, the most common causes of road fatalities and car accidents occasioning serious harm are fatigue, speed, distraction (including mobile phones), and alcohol or drugs.

During the 12 months ending in February 2018, there were 1249 road deaths across Australia. That was a 0.2 per cent decrease compared to the total for the 12-month period ending February 2017.

In 2016, 1300 lives were lost on roads nationwide, which was an increase of nearly 8 per cent on the previous year (1205).

Mr Corboy said in a statement earlier this month that too many people made “poor decisions” while driving. “Every fatal crash is a tragedy for not only those involved, but for the families they leave behind,” he said.

“The most frustrating part about it is that most crashes are preventable if people slow down and take responsibility on our roads.”

In NSW, motorists caught using a mobile phone while driving can be slapped with a $330 fine and a loss of four demerit points, regardless of whether they’re repeat offenders or not.

The Australian Capital Territory has some of the toughest laws in the country, with a fine of $528 and loss of four demerit points for a driver caught texting or using social media behind the wheel.

Like the ACT, Western Australia also has a separate specific offence for motorists caught texting while driving. “WA Police Force is constantly looking for new ways to target offences frequently linked to serious and fatal crashes on our roads, including inattention through mobile phone use,” a WA Police spokesman told news.com.au.

“The penalty for using a mobile phone while driving is $400 and three demerit points.”

This driver was booked by Acting Sargeant Paul Stanford for using a mobile phone while driving in Brisbane City and copped a $378 fine. Picture: Jamie Hanson.Source:News Corp Australia

Acting Sargeant Paul Stanford talks to a motorist in Brisbane City. Picture: Jamie Hanson.Source:News Corp Australia

In Queensland, motorists can be fined $378 and have three demerit points recorded against their traffic history if they are caught holding a mobile phone for any reason while driving — that includes when they’re stopped at traffic lights or in congested traffic.

Learner and P1 drivers are prohibited from using hands free, wireless headsets or a mobile phone’s loudspeaker function. “At this time the QPS does not have technology to detect drivers using mobile phones,” a QLD Police spokesman told news.com.au.

Double demerit points apply for second or subsequent mobile phone offences committed within one year after an earlier offence.

HI-TECH CAMERAS TRIALLED

A hi-tech camera which can detect people using their mobile phones while driving was trialled in Melbourne last year. Picture: Mark Stewart.Source:News Corp Australia

Drivers Ms Auto Mobile Phones & Portable Devices 2017

A red-light style camera capable of photographing drivers illegally using their mobile phones was trialled in Melbourne, Victoria last year. The technology — touted as a world first — detected 272 culprits during a five-hour test across just one lane of the Eastern Freeway, the Herald Sun reported.

The trial revealed that 7.1 per cent of the drivers observed infringed phone use laws. And 65.8 per cent of those offences related to motorists actively using their phone by holding it or touching it in a cradle. Authorities said in December last year that they were always looking at ways to improve road safety but had no current plans to introduce the technology.

SOUTH AUSTRALIA

A driver who was booked for using his mobile phone while driving in Brisbane. Picture: Jamie Hanson.Source:News Corp Australia

A South Australia Police spokesman told news.com.au the state “doesn’t have any technologies to assist in the detection of driving while using mobile phones”.

As of November 11, 2017, the fine for using a mobile phone while driving was $327 plus a $60 government levy — totalling $387 coupled with three demerit points. Drivers are permitted to touch their phones only if they are making or receiving a call on a device mounted to the vehicle.

Drivers Ms Auto Mobile Phones & Portable Devices

“To avoid doubt, nothing ... authorises a person to use a mobile phone by pressing a key on the phone, or by otherwise manipulating the body or screen of the phone, if the phone is not secured in a mounting affixed to the vehicle,” the legislation reads.

The SA Police spokesman said it was “not unlawful to pull over to the side of the road to a place where it is legal to stop and make or receive a telephone call”.

“There is no requirement to turn off the engine,” he said. “Although the rule that relates to mobile telephones does not say that the vehicle must be in an area where it is legal to park, other Australian Road Rules apply.

“To put that into context, it is not legal to park at a set of traffic lights, therefore it is unlawful to use a hand held phone while stationary at those lights.”

[email protected] @Megan_Palin