- Host-based – Host-based drivers use the computer's (host's) resources to process print commands when the computer is connected to the printer via USB cable. It is a custom driver created for host-based printers to provide basic print or print/scan software features. Enables more advanced software functionality than the drivers included InOS or Windows Update.
- Access any files, from drivers to manuals, that you may need for your Kyocera product. Can't find what you're looking for? Our support teams are as efficient and reliable as our document solutions.
- Download the Windows Driver Kit (WDK) and install it. Create a driver package folder on the machine that the USB device is connected to.
Vendors can provide an INF file to install a WBDI driver.
Build a basic v4 printer driver by using the driver development wizard in Microsoft Visual Studio 2019 to select the minimum set of features to create a functional printer driver. The instructions in this topic will focus on the steps required for building a driver, and will not explain the many printer driver options available in the wizard.
The following is a list of guidelines for biometric device installation. The code examples in this topic are taken from the WudfBioUsbSample.inx file of the WudfBioUsbSample:
WBDI drivers should specify a class of 'Biometric.' Set ClassGuid equal to the value that corresponds to GUID_DEVCLASS_BIOMETRIC in Devguid.h:
In your .HW section, provide AddReg directives to specify three sections that contain entries to be added to the registry:
Provide the named sections referred to in the .HW section. The [Biometric_Device_AddReg] section sets values for the biometric device, including the exclusive flag and system wake/device idle. To be recognized by Windows Biometric Framework, UMDF-based WBDI drivers must set the 'Exclusive' value to 1. The first two lines of the [Biometric_Device_AddReg] section specify access control list (ACL) rights so that the device can only be opened by an administrator or the local system account. When you specify these ACL rights, third-party applications cannot open the device and capture fingerprint data when the WinBio service is not running. For example:
A WBDI driver that exposes functionality to a legacy (non-WBDI) biometric stack should set the Exclusive value to zero. If this value is set to zero, the Windows Biometric Framework does not attempt to control the device and the device is not exposed through WBF.
Vendors can have a single driver binary that can work with legacy stacks and WBF, but the two cannot operate simultaneously. WBF will only operate if the device can be opened with exclusive access.
The second named section contains registry values for the plug-in adapters. The sample uses the Microsoft-provided sensor adapter and storage adapter. This section also enables Windows log-in support by setting the SystemSensor value:
Finally, the third section sets the following registry values for the database service. The identifying GUID must be unique for each vendor database of a certain format. For instance, in this code example from the sample, change 6E9D4C5A-55B4-4c52-90B7-DDDC75CA4D50 to your own unique GUID in your INF file.
To differentiate WBDI and legacy drivers, vendors must set a Feature Score for the driver in the INX file. Feature Score is not set in the WudfBioUsbSample sample. For more information about setting a Feature Score, see Ranking a Biometric Driver on Windows Update.
For information about INX files and how they differ from INF files, see Using INX Files to Create INF Files.
Printer Driver Windows 10
In order to replace a WBDI driver with a legacy driver, use the following procedure:
Custom Engineering Spa Printers Driver Download For Windows
Close all currently active WBF applications.
Uninstall the WBDI driver.
Stop the WBF service, restart it, and then stop it again.
Install the legacy driver.
The driver samples in this directory provide a starting point for writing a custom print driver for your device.
| Sample | Description |
|---|---|
| Print Auto Configuration | Demonstrates how to implement Unidrv-based and PScript5-based drivers to leverage the inbox support for auto-configuration. The sample works only when used with the standard TCP/IP port monitor or the Network-Connected Device (NCD) port monitor. |
| Common Property Sheet UI | An application that causes the Common Property Sheet User Interface (CPSUI) to call the Windows print spooler to create property sheet pages for the system's default printer. |
| OEM Printer Customization Plug-in Samples | The OEMDLL samples are an illustration of OEM customization plug-ins. The BITMAP, OEMPS, OEMUI, OEMUNI, OEMPREAN, CUSTHLP, SyncSet, ThemeUI, PSUIRep, and Watermark samples do not affect the printer output. They are only examples of how to build OEM Customization DLLs of various types. |
| OpenXPS Documents | Contains a set of documents that were generated from a variety of sources, including those generated from the Windows Presentation Foundation in the .NET Framework and from the Microsoft XPS Document Writer (MXDW). They have been included to provide you with a few documents that exercise a variety of features of the XML Paper Specification. |
| XPS Documents | Contains a set of documents that were generated from a variety of sources, including those generated from the Windows Presentation Foundation in the .NET Framework and from the Microsoft XPS Document Writer (MXDW). They have been included to provide you with a few documents that exercise a variety of features of the XML Paper Specification. |
| Print Pipeline Simple Filter | Shows how to use the print pipeline's filter interfaces. |
| Printer Extension | Demonstrates how to use .NET to build a customized, desktop UI for a v4 print driver. This .NET application uses PrintTicket, PrintCapabilities and Bidi in order to communicate with the print system and is suitable for inclusion in a v4 print driver. |
| Print Driver Constraints | Demonstrates how to implement advanced constraint handling, and also PrintTicket/PrintCapabilities handling using JavaScript. |
| USB Host-Based Print Driver | Demonstrates how to support host-based devices that use the v4 print driver model, and are connected via USB. |
| Print USB Monitor and BiDi | Demonstrates how to support bidirectional (Bidi) communication over the USB bus, using JavaScript and XML. This sample supports bidirectional status while not printing, and unsolicited status from the printer while printing. |
| WSDMon Bidi Extension | Demonstrates how to use an XML extension file to support bidirectional (Bidi) communication with a WSD connected printer. |
| XPSDrv Driver and Filter | This sample is intended to provide a starting point for developing XPSDrv printer drivers and to illustrate the facility and potential of an XPSDrv print driver. This goal is accomplished by implementing a number of real-world features within a set of XPS print pipeline filters that are configured through a configuration plug-in that supports custom UI content and PrintTicket handling. |
| XPS Rasterization Filter Service | An XPSDrv filter that rasterizes fixed pages in an XPS document. Hardware vendors can modify this sample to build an XPSDrv filter that produces bitmap images for their printers or other display devices. |