
The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. To load the driver, you need to write an INF that references the modem INF ( mdmcpq.inf) by using the Include directive.

In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device. Unlike desktop editions, it is not possible to load a driver through an external driver package. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Microsoft encourages you to use in-box drivers whenever possible.

For information about INF sections, see Overview of INF Files. For examples, look through the INF files included with sample drivers and find devices similar to your device.

The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows. You do not need to write your own INF to reference the driver. If your device belongs to the communications and CDC control device class, Usbser.sys is loaded automatically. Starting in Windows 10, Usbser.inf was added to the %Systemroot%\INF directory, which loads Usbser.sys as the functional device object (FDO) in the device stack. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows. If they are not installed automatically, contact the device manufacturer. If you trying to install a USB device class driver included in Windows, you do not need to download the driver.
