| 425 | == Test-signing issues == |
| 426 | |
| 427 | You may encounter the follwoing error when building with EWDK from the command-line with buildtap.py with --hlk switch, which has test-signing enabled: |
| 428 | |
| 429 | {{{ |
| 430 | SIGNTASK : SignTool error : No certificates were found that met all the given criteria. |
| 431 | }}} |
| 432 | |
| 433 | This happens even though a properly named (e.g. "WDKTest samuli") certificate is present under ''cert:\!CurrentUser\My''. This problem was probably caused doing a "Hlk" build from inside Visual Studio 2019 Community, which created the WDKTest certificate automatically, but in a way that EWDK was unable to use it. |
| 434 | |
| 435 | This problem can be resolved by simply removing the old certificate. For example: |
| 436 | |
| 437 | {{{ |
| 438 | PS> Remove-Item Cert:\CurrentUser\My\91047502F73D5410C106E05CEC8A990219810FBE |
| 439 | }}} |
| 440 | |
| 441 | Then just run buildtap.py with --hlk to create a new test-signing certificate. |
| 442 | |
| 443 | You will also need to export the new certificate from the certificate store. For example: |
| 444 | |
| 445 | {{{ |
| 446 | PS> Get-Childitem Cert:\Currentuser\My\F1E725722C5BB56757B6D261D958425869213089|Export-Certificate -Filepath C:\users\samuli\opt\wdktest-samuli.cer |
| 447 | }}} |
| 448 | |
| 449 | Then import that certificate to the certificate store on HLK clients. The puppet-hlk_tap6_openvpn module handles that part automatically with Powershell DSC. |
| 450 | |