If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically.With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf. For more information, see USB communications device class. If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor.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. Driver can auto-download via Windows Update (Windows 7, 8, 8.If you trying to install a USB device class driver included in Windows, you do not need to download the driver. Windows Vista, 7, 8, 8.1 Certified WHQL Driver Compatible with Windows 2000SP4 & Server2003 Installer version & Build date: 1.12.0 () (For PL2303 HXA, XA, HXD, EA, RA, SA, TA, TB versions) This is the Prolific website read on the driver I installed:ĭownload File: PL2303_Prolific_DriverInstaller_v1.12.0.zip July for the ones from the download page) and so Windows prefers it over them. The problem is probably that the non-working driver is the newest (September 2021 vs. I had only one other entry, a "ser2pl.inf" version " 3.8.40.0".ĭisconnect the device, and "pnputil /delete-driver oemXY.inf" with the INF file you located in the previous step.Ĭonnect the device again, and it should work, at least, it does for me. Then "pnputil /enum-drivers", and in the output look for Prolific drivers other than the ones from the previous step. It will add the two driver packages to the driver store and tell you what oemXY.inf files it has assigned to them. What I did is this:įirst install the downloaded driver by unpacking the zip file and "pnputil /add-driver *.inf /subdirs /install" (the /install is probably not necessary) from the extracted "Win11_DCHU" directory. Getting it installed is a bit tricky, it seems. There is a working driver at, a bit down the page listed as "DCHU (for PC Vendors)".
0 kommentar(er)
