[wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?

  • From: "Vincent Burel \(VB-Audio\)" <vincent.burel@xxxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Thu, 8 Oct 2015 15:34:42 +0200

No, it does not work anymore on WIN10 release, this is what I’ve experimented
last days when building a new driver version,

This is also explained there:

http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx



Regards

Vincent Burel



De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
De la part de Tom Eckert
Envoyé : jeudi 8 octobre 2015 15:22
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Audio Driver Code Signing for WIN10 ?



If you have a code signing certificate that was issued before the Win10 release
date, you can continue to use it with the old driver signing method until it
expires.

Tom Eckert

On 10/8/2015 3:02 AM, Vincent Burel (VB-Audio) wrote:

Hello,



As far as I see; WIN10 does not allow Installation of driver signed after its
Release Date.

In other words, doing a driver package today for WIN10 is not possible anymore
without using the Microsoft Signing Services.

(please confirm or if there is a workaround? )



Consequently we need to register on Microsoft DashBoard
(https://sysdev.microsoft.com/) and sign different agreements…



So I have basically 2 questions:

What is the exact list of Agreements that must be signed to be able to make
code-signing on an audio driver ?

What is the technical and financial risk ? (some agreement are about technical
constraint , some other talk about paying Microsoft for testing services).



Regards

Vincent Burel



Other related posts: