Composite device inf file

The hardware IDs for audio interface collections do not contain interface class-specific information. The format of compatible IDs for audio interface collections contains embedded information about the interface class, interface subclass, and the protocol.

One data class interface and optional audio class interfaces that the union functional descriptor UFD references. If the operating system does not find a match for one of the hardware IDs in a vendor-supplied INF file, the system automatically loads the native NDIS miniport driver to manage the interface collection.

The UFD can reference an audio class interface collection that is enumerated independently of the TCM interface collection. MCPC interface collections have the following properties. Video class interface collections receive special handling on CDC devices. If the collection uses one of the protocols that the WMCDC specification describes, the protocol value that is embedded in the compatible IDs is 0x2 through 0x06, or 0xFE.

The UFD might reference an audio interface collection that is enumerated independently of the ACM interface collection. Interface collections must comply with the special descriptor and endpoint requirements that are specified in section 6.

If the operating system does not find a match for one of the hardware IDs in a vendor-supplied INF file, the system automatically loads the native telephony application programming interface TAPI modem filter driver to manage the modem function and sets the appropriate TAPI registry settings, unless the protocol code is 0xFE. If the protocol code is 0xFE, the vendor must supply a device or class co-installer to correctly populate the TAPI registry settings.

The registry settings that are associated with the instance of the USB generic parent driver that manages the WHCM interface collection determine whether the USB generic parent driver creates a physical device object PDO for the interface collection or not.

The union functional descriptor UFD identifies interfaces that are associated with a logical handset. If a USB composite device has an interface association descriptor IAD in its firmware, Windows enumerates interface collections as though each collection were a single device and assigns a single physical device object PDO to each interface collection and associates hardware and compatible identifiers IDs with the PDO.

You cannot use IADs recursively to bind functions of functions. In particular, if a device has IAD descriptors in its firmware, the generic parent driver will not group interfaces by audio device class, as described in Enumeration of Interface Collections on USB Composite Devices. For audio devices, the Windows operating system can enumerate groups of interfaces interface collections that are associated with a function and assign a single physical device object PDO to each group, even when the device does not have an interface association descriptor IAD.

The operating system groups the interfaces of composite audio devices into interface collections, if the interfaces meet the following conditions:. If an interface does not meet all of these three conditions, Windows will attempt to enumerate it separately instead of grouping it with the other audio class interfaces.

The operating system does not group audio class interfaces in a special way if an interface association descriptor IAD is present in device firmware. This section describes hardware and compatible identifiers IDs associated with the PDO that is created by the operating system for an interface collection whose interfaces belong to the audio device class. In these compatible IDs, c 2 , s 2 , and p 2 contain values that are taken, respectively, from the bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol fields of the first USB interface descriptor in each interface collection.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. In USB terminology, these devices are called composite devices. Microsoft Windows and Windows 98 operating systems include a generic parent facility in the USB bus driver Usbhub. Using the features of the generic parent driver, device vendors can make selective use of Microsoft-supplied driver support for some interfaces.

The interfaces of some composite device operate independently. For example, a composite USB keyboard with power buttons might have one interface for the keyboard and another interface for the power buttons. The USB generic parent driver enumerates each of these interfaces as a separate device. The operating system loads the Microsoft-supplied keyboard driver to manage the keyboard interface, and the Microsoft-supplied power keys driver to manage the power keys interface. If the composite device has an interface that is not supported by native Windows drivers, the vendor of the device should provide a driver for the interfaces and an INF file.

Step 1: Go ahead and open Services. Once you have found it, go ahead and right-click on it. Step 3: Next is choose Properties. This can be found under the General tab. From there, go ahead and have the Startup set to Automatic.

Step 4: Then, go ahead and hit on the Start button for you to be able to activate your Apple Mobile Device Service again. After that, go ahead and restart your PC. The first thing that you need to do is to ensure that you have the iTunes program and the Apple Mobile Device Support be stored on your computer. And after that, go ahead and follow the steps below. And then right-click on it and then choose Update Driver then go to Browse my computer so that the driver software can be located and then select this folder:.

Then after that, go ahead and click on the Next button. After doing all of the steps above, your Apple USB driver will then be updated on your computer. Once you do, check if your iOS device can now be detected by your computer. Some iOS users are having trouble connecting their device to their computer. And because of this kind of situation, what they want to do is to have the Apple Mobile Device Support and the Apple Mobile Device Service should be installed separately.

Well, the fact is that, the Apple Mobile Device Support or the Apple Mobile Device Service is known to be one of the components of the iTunes program and that they cannot be separately installed. So for you to be able to have the Apple Mobile Device Service reinstalled on your computer, go ahead and take out iTunes and its component that is related to it and then have your iTunes reinstalled from Apple Store or the Microsoft Store.

And as you can see, doing the Apple Mobile device USB Driver download is a very important thing to do since your iOS device is not able to recognize by your computer and your iTunes program as well. If you do not have the driver for your Apple device, then you will not be able to transfer any of your data from your iPhone, iPad, or iPod device.

So with that, if your Apple Driver is missing, all you need to do is to follow the methods that we have shown you above. That way, you will be able to have your iOS device be detected by your iTunes program and as well as your computer.