Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results


More Info on Driver Writing and Debugging

The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.

Check out The OSR Learning Library at:

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

Windows 8.1: WinUSB.sys for service 'WinUsb' is not present.

HagenHagen Member Posts: 49

we have an application that communicates via WinUSB with its device. WinUSB is installed via custom .inf.
Two Windows 8.1 users report an issue where WinUSB can't be installed. The install log reads:
AddService=WinUsb,0x000001fa,WinUsb_ServiceInstall (winusb.inf line 31)
!!! dvi: Add Service: Binary
'C:\Windows\system32\DRIVERS\WinUSB.sys' for service 'WinUsb' is not

Other than that there are several thousand installation without the issue. The inf reads:
Signature= "$WINDOWS NT$"
Class= MEDIA
ClassGUID= {4d36e96c-e325-11ce-bfc1-08002be10318}
Provider= %VENDOR%
DriverPackageDisplayName= %VENDOR% %DEVICE%
PnpLockDown= 1

%VENDOR%= devices, NT$ARCH$

%DEVICE%= DeviceInstall, USB\VID_xxxx&PID_xxxx&MI_xx

Include= winusb.inf

Include= winusb.inf
Needs= WINUSB.NT.Services
AddService= WinUsb, 0x000001fa, WinUsb_ServiceInstall

AddReg= DeviceInstall.AddReg

HKR,, DeviceInterfaceGUIDs, 0x10000, "{fbd8de61-48b4-4072-9a00-2bb4ac85aabf}"

DisplayName= %DEVICE%
ServiceType= 1
StartType= 3
ErrorControl= 1
ServiceBinary= %12%\WinUSB.sys

DEVICE="My Device"

Any hint where to look or idea what could have went wrong, or even just a workaround for the user is highly appreciated!


  • Pavel_APavel_A Member Posts: 2,781
    edited May 27

    %VENDOR%= devices, NT$ARCH$

    The inf really has these lines? Hmm.

  • HagenHagen Member Posts: 49

    Well, it can be assumed that it had these lines before getting architecture-customized. Of course after customization, stampinf, etc. it reads (for x86_64):
    Signature= "$WINDOWS NT$"
    Class= MEDIA
    ClassGUID= {4d36e96c-e325-11ce-bfc1-08002be10318}
    Provider= %VENDOR%
    DriverPackageDisplayName= %VENDOR% %DEVICE%
    PnpLockDown= 1

    %VENDOR%= devices, NTamd64


  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,970

    The install log reads:
    AddService=WinUsb,0x000001fa,WinUsb_ServiceInstall (winusb.inf line 31)

    You didn't literally call your inf file "winusb.inf", did you? Did you not notice there is already a "winusb.inf"? Your winusb drivers are supposed to use Needs and Include to bring in the standard winusb.inf.

    You're sure both of those users were on Windows 8.1? In Windows 7, WinUSB did not ship with the operating system, so your driver package would have to use the co-installers. It should be included in Windows 8.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • HagenHagen Member Posts: 49

    Thanks, Tim,
    winusb.inf - good point! But doesn't it end up as oemxx.inf anyways. I will see if this improves anything.
    And yes, its 8.1 thats why I am posting here.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Developing Minifilters 24 May 2021 Live, Online
Writing WDF Drivers 14 June 2021 Live, Online
Internals & Software Drivers 27 September 2021 Live, Online
Kernel Debugging 15 November 2021 Live, Online