Table of contents
TOC
Collapse the table of content
Expand the table of content

DIFx Guidelines

Last Updated: 8/24/2016

The Driver Install Frameworks (DIFx) tools were removed from the Windows 10 Version 1607 WDK. Instead, we recommend providing your driver as a standalone package that doesn't require an installer, ideally through Windows Update. To add your driver to Windows Update, the first step is to submit your driver package to the Sysdev Driver Portal.

If you choose to use DIFx anyway, you should be aware of a couple caveats:

  • If your driver package specifies only TargetOSVersion values of Windows 8.1 or later, you cannot use DIFxApp. TargetOSVersion is specified in the INF Manufacturer Section. DIFxApp exposes MSI custom actions such as MsiProcessDrivers, MsiInstallDrivers, and MsiUninstallDrivers. If your driver package specifies only TargetOSVersion values of Windows 8.1 or later, you cannot use these custom actions in your MSI.
  • Starting in Windows 8.1, applications that link to Difxapi.dll must contain an app manifest targeting the OS version on which the application is intended to run. This is due to DIFxAPI's dependency on GetVersionEx, an API that changed starting in Windows 8.1. For more on changes to GetVersionEx in Windows 8.1, see Targeting your application for Windows.
  • Use DIFx version 2.1, which is available in the Windows 7 WDK through the Windows 10 Version 1511 WDK. Although DIFx version 2.1 was available in earlier versions of the WDK, it was not properly compatible with Windows 7 and later versions of Windows.
© 2016 Microsoft