Windows 10 USBSER fails to load with our hardware. All previous windows versions work fine????? <URGENT> RRS feed

  • Question

  • <<<<URGENT PROBLEM using USBSER.SYS in Windows 10>>>>

    We have a hardware product which is communicated to via windows by USBSER.sys SERENUM.sys.
    We use a basic INF file to load the drivers.
    This configuration has worked from VISTA through to WINDOWS 8.

    This NOW FAILES with driver load error of CODE 10 in WINDOWS 10!

    We have no method of changing the Firmware USB coding to accomadate changes in Windows 10 USBSER.

    Is there a method we can "Use the USBSER.sys and SERENUM.sys" driver files from an earlier version of windows IN WINDOWS 10???

    This is of the most URGENCY since when Windows 10 is released, currently we have NO METHOD and our customers will find no ability to communicate with our product.

    Our product is a Harley Davidson ECU.

    Any and all help guidance appreciated!!


    If direct contact desired...
    email me at...
    Saturday, July 11, 2015 2:50 PM

All replies

  • Which build of Win10?

    Have you looked in the event log?

    You should enable trace logging. The docs on tracing are here

    I would recommend you start tracing these providers:

    Microsoft-Windows-Kernel-PnP             {9C205A39-1250-487D-ABD7-E831C6290539}
    Microsoft-Windows-USB-USBHUB             {7426A56B-E2D5-4B30-BDEF-B31815C1A74A}
    Microsoft-Windows-USB-USBHUB3            {AC52AD17-CC01-4F85-8DF5-4DCE4333C99B}
    Microsoft-Windows-USB-USBPORT            {C88A4EF5-D048-4013-9408-E04B7DB2814A}
    Microsoft-Windows-USB-USBXHCI            {30E1D284-5D88-459C-83FD-6345B39B19EC}
    Microsoft-Windows-Serial-ClassExtension  {47BC9477-A8BA-452E-B951-4F2ED3593CF9}
    Microsoft-Windows-Serial-ClassExtension-V2 {EEE173EF-7ED2-45DE-9877-01C70A852FBD}


    Azius Developer Training Windows device driver, internals, security, & forensics training and consulting. Blog at

    Saturday, July 11, 2015 8:17 PM
  • Can you please capture logs and e-mail them to me : vivekg(@)

    From an administrator cmd prompt: 

    logman create trace -n USBSER_WPP -o %SystemRoot%\Tracing\USBSER_WPP.etl -nb 128 640 -bs 128

    logman update trace -n USBSER_WPP -p {6b4acd39-60f9-48a2-a5e1-c7168dffed0a} 0x7FFFFFFF 0xFF

    logman start -n USBSER_WPP


    <<< Repro the issue here by plugging the device>>>>


    logman stop -n USBSER_WPP

    logman delete -n USBSER_WPP

    move /Y %SystemRoot%\Tracing\USBSER_WPP_000001.etl %SystemRoot%\Tracing\USBSER_WPP.etl


    Saturday, July 11, 2015 11:47 PM