InstallDriver error code 31 after SysDev signing
Posted: Sat Feb 24, 2018 5:46 pm
Past 3 months I've been having a larger number of clients reporting driver not being installed under their windows 10, it seems microsoft is slowly rolling their previous call to not trusting in the EV certificate and requiring you to go through their dashboard to get an extra signature from them
To make sure it was not something on my end, on the machines that the driver under my certificate no longer loads, will also not load PrintMonitor sample driver, disabling secureboot let's them both work as stated before by microsoft
So I went through the process on the sysdev dashboard, it requires a .cab with the driver and the .inf, and you need to submit one architecture at a time
Things went pretty straight forward(I use globalsign's EV certificate), I used the .inf provided in the last version from december 22,2017 and modified the strings and only used the 64 bits .cat due having to submit one architecture at a time
It went on successfully and I got the signed driver that now has 3 signatures (sha1, sha256 and the microsoft's sha256), so far so good
But somehow the InstallDriver method fails now, reporting error code 31, if I try the exact same driver before submiting to the sysdev dashboard(with the dual signature) it installs successfully
I first suspected it was the signature requested in the dashboard(different versions of windows 10 RS2 RS3 etc) but I specifically selected the x64 versions, I repeated the process unchecking almost all boxes to see if it could be related, same error 31 result
Then I thought that the triple signature could be related, so I tried one more time now only signing sha256, still same result
Any ideas?
To make sure it was not something on my end, on the machines that the driver under my certificate no longer loads, will also not load PrintMonitor sample driver, disabling secureboot let's them both work as stated before by microsoft
So I went through the process on the sysdev dashboard, it requires a .cab with the driver and the .inf, and you need to submit one architecture at a time
Things went pretty straight forward(I use globalsign's EV certificate), I used the .inf provided in the last version from december 22,2017 and modified the strings and only used the 64 bits .cat due having to submit one architecture at a time
It went on successfully and I got the signed driver that now has 3 signatures (sha1, sha256 and the microsoft's sha256), so far so good
But somehow the InstallDriver method fails now, reporting error code 31, if I try the exact same driver before submiting to the sysdev dashboard(with the dual signature) it installs successfully
I first suspected it was the signature requested in the dashboard(different versions of windows 10 RS2 RS3 etc) but I specifically selected the x64 versions, I repeated the process unchecking almost all boxes to see if it could be related, same error 31 result
Then I thought that the triple signature could be related, so I tried one more time now only signing sha256, still same result
Any ideas?