none
Windows Insider Preview Windows Driver Kit (WDK) build 16190 is now available for Visual Studio 2017 RRS feed

  • General discussion

  • The Windows Insider Preview Windows Driver Kit (WDK) build 16190 is now available for Visual Studio 2017. Here are the known issues which will be addressed in subsequent releases:

    • This is a two-step installation process (instructions at the link below).
    • Install warning regarding 'no developer environment’. – This is benign and can be ignored.
    • Install warning regarding ‘unable to build modern apps’. This is benign and can be ignored.
    • Launching 'Driver -> Test -> Configure Devices' does not work.
    • Launching 'Driver -> Static 'Driver Verifier'  does not work.
    • Compiling an instantiated "Printer Driver v4" template fails.
    • Compiling an instantiated "Printer XPS Render Filter" template fails.

    This is a preview release and is not allowed for production use. This release will also support VS2015, however that support will be removed in subsequent releases.

    For more information and to download, please visit:

    https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewWDK

    Friday, May 12, 2017 8:57 PM

All replies

  • Thank you for expediting this Erin. Not having SDV is a problem, though. Do you have an ETA on that?

     -Brian


    Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog

    Friday, May 12, 2017 9:14 PM
    Moderator
  • Launching SDV from the menu will be supported in the next WDK WIP release. 

    k


    Friday, May 12, 2017 11:06 PM
  • After installing (and running the second step to install the VS2017 extension), I get several errors every time I try to launch VS2017. It also gives an error and fails to create a new project from any of the driver templates.

    The errors are along the lines of:
    "The 'DriverCommonPackage' package did not load correctly."
    "The 'DriverTargetConfigPackage' package did not load correctly."
    ...

    The first error refers to an ActivityLog.xml file that has this error description:
    CreateInstance failed for package [DriverCommonPackage]Source: 'mscorlib' Description: Could not load file or assembly 'DriverCommonPackage, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
System.IO.FileLoadException: Could not load file or assembly 'DriverCommonPackage, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
File name: 'DriverCommonPackage, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
   at System.Reflection.Assembly.LoadFrom(String assemblyFile, Evidence securityEvidence)
   at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
   at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)

System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer

    Sunday, June 25, 2017 5:36 PM
  • s_p_oneil,

    I bet it is a signing issue.  Try our new WDK we just released.  Same URL.

    Jakob

    Thursday, June 29, 2017 7:32 PM