What's New for WDF Drivers Getting Started with UMDF Using WDF to Develop a Driver Writing a Simple WDF Driver Sample Toaster Driver Programming Tour Developing Drivers with the Windows Driver Foundation: Reference Book Supporting PnP and Power Management in Your Driver Creating a Framework Device Object Power Management for I/O Queues Handling Requests to Stop a Device PnP and Power Management Scenarios PnP and Power Management Callback Sequences Driver Access to Hardware Creating WDF HID Minidrivers Handling Client Impersonation in UMDF Drivers Host Process Timeouts in UMDF Supporting Kernel-Mode Clients in UMDF Drivers Handling DMA Operations in KMDF Drivers Supporting WMI in KMDF Drivers Accessing WDM Interfaces in KMDF Drivers Building, Installing, and Testing Porting a Driver from WDM to WDF Additional Topics for KMDF Drivers UMDF 1.x Design Guide Developing Drivers with the Windows Driver Foundation: Reference BookThe Developing Drivers with Windows Driver Foundation book is also available to help you learn the concepts and fundamentals of Windows Driver Frameworks (WDF).
This book introduces Windows drivers and basic kernel-mode programming, and then describes the WDF architecture and programming model. It provides a practical, sample-oriented guide to using the frameworks to develop Windows drivers.Orwick, Penny and Guy Smith. Developing Drivers with Windows Driver Foundation. Redmond, WA: Microsoft Press, 2007.Where can I find the book?You can purchase the book from O'Reilly using the following links:Electronic or printed formatPreview or read entire content with a Safari subscriptionI’ve been reading quite a bit for the last couple of months and I compiled my list of the 5 Windows development books that I want to complete: 1) Windows Internals (finished): The classic book by Mark Russinovich and David Solomon is now in its 5th edition. I’ve read the 4th one and I think that it’s a must-read for every windows developer. 2) Developing Drivers with the Windows Driver Foundation (finished): I just finished the book and I think that its the best book currently available to windows driver developers, especially for beginners.
I’ll write a review shortly, however I think that it’s definately the most complete and at the same time easier to read book on windows drivers. 3) Advanced Windows Debugging (not started): After John Robbins decided not to write a debugging book for Win32 programming, I was wondering which book would take its place. I’ve read lots of good reviews about this book and I have it in my bookcase, so I’m eager to read it. Just with a first glance it seems to be exactly what I was searching for. 4) Windows via C/C++ (not started): This is the latest version for “Programming Applications for Microsoft Windows”. It covers application development in Windows. I’ve taken a class by Jeffrey Richer and I know that he’s definately both a good developer and a good teacher, so I’m waiting to read it. 5) Programming the Windows Driver Model (half-read): This is the most tough-to-read and most advanced book in windows driver development. It covers many aspects of windows in depth, however I don’t feel that I’m ready to read it yet.
I’ve tried a couple of times in the past and I failed miserably. I think that really understanding this book means that your level is definately above intermediate. Of course, there are other books, like Subverting the Windows Kernel, however these are my top choices. I’d love to hear your comments, as well as your top choices.This topic summarizes the new features and improvements for Windows Driver Frameworks (WDF) drivers in Windows 10.Windows 10, version 1607 includes Kernel-Mode Driver Framework (KMDF) version 1.19 and User-Mode Driver Framework (UMDF) version 2.19.You can use these framework versions to build drivers for:For version history, see KMDF Version History and UMDF Version History. Except where noted, UMDF references on this page describe version 2 functionality that is not available in UMDF version 1.The WDF source code is now available as open source on GitHub. This is the same source code from which the WDF runtime library that ships in Windows 10 is built. You can debug your driver more effectively when you can follow the interactions between the driver and WDF.
/Microsoft/Windows-Driver-Frameworks.The private symbol files for WDF on Windows 10 are now available through the Microsoft Symbol Server.The Windows Driver Kit (WDK) 10 samples are also now published to GitHub. /Microsoft/Windows-Driver-Samples.When you use WinDbg to debug a WDF driver on Windows 10, WinDbg automatically retrieves the framework source code from Microsoft's public GitHub repository. You can use this feature to step through the WDF source code while debugging, and to learn about framework internals without downloading the source code to a local machine. For more information, see New support for source-level debugging of WDF code in Windows 10, Debugging with WDF Source, and Video: Debugging your driver with WDF source code.All WDF driver samples and Visual Studio driver templates are Universal Windows driver compliant.All KMDF and UMDF 2 functionality is Universal Windows driver compliant.Note that UMDF 1 drivers run only on Windows 10 for desktop editions and earlier versions of desktop Windows.
Want to benefit from the universal capabilities of UMDF 2? To learn how to port your old UMDF 1 driver, see Porting a Driver from UMDF 1 to UMDF 2.All KMDF and UMDF 2 drivers can use the new always on, always available Inflight Trace Recorder (IFR). When a driver provides a custom trace, the driver IFR log contains the trace messages. Note that the new driver IFR log is separate from the framework IFR log that WDF creates for each driver.It's easy to turn on the IFR. See Inflight Trace Recorder (IFR) for logging traces and Using Inflight Trace Recorder in KMDF and UMDF Drivers.The IFR maintains a circular buffer of WPP traces in non-pageable memory. If a driver crashes, the logs are frequently included in the crash dump file.If you turn on the IFR in your driver binary, the IFR is present and running during the lifetime of your driver. You don't need to start an explicit trace collection session.IFR logs are included in minidump files except when the responsible driver is undetermined or if the crash was a host timeout.
If you have a debugger connected, you can access both the driver and framework IFR logs by issuing !wdfkd.wdflogdump.If you do not have a debugger connected, you can still access both logs. To learn how, see Video: Accessing driver IFR logs without a debugger.When debugging a UMDF driver, you can merge framework logs with driver logs by issuing: !wdfkd.wdflogdump-mUMDF logs (WudfTrace.etl) and dumps are now located in %ProgramData%\Microsoft\WDF instead of %systemDrive%\LogFiles\Wudf.New debugger command: !wdfkd.wdfumtriage provides a kernel-centric view of all UMDF devices on the system.You can run !analyze to investigate UMDF verifier failures or UMDF unhandled exceptions. This works for live kernel debugging as well as debugging user crash dump files from %ProgramData%\Microsoft\WDF.In KMDF and UMDF 2, you can monitor power reference usage in the debugger. For info, see Debugging Power Reference Leaks in WDF.You can use !wdfkd.wdfcrashdump to display error information about UMDF 2 drivers.
For more information, see !wdfkd.wdfcrashdump.You can use the Windows Performance Toolkit (WPT) to view performance data for a given KMDF or UMDF 2 driver. When tracing is enabled, the framework generates ETW events for I/O, PnP, and Power callback paths. You can then view graphs in the Windows Performance Analyzer (WPA) that show I/O throughput rates, CPU utilization, and callback performance. The WPT is included in the Windows Assessment and Deployment Kit (ADK).For more information, see New Performance Tools for WDF Drivers in Windows 10 and Using the Windows Performance Toolkit (WPT) with WDF.UMDF now fully supports HID filters (enumerated by HIDClass) and minidrivers. Simply port your existing KMDF driver or write a new UMDF 2 filter; the functionality is automatically enabled.UMDF HID minidrivers that are enumerated by ACPI can perform selective suspend. For more information, see Creating WDF HID Minidrivers.UMDF drivers can now be installed in the HID stack for low latency input devices such as touch and mouse.