Windows 10 Driver(without hardware device) with Error 39, 0xc0000603, Certificate Revoked
Well, the driver was signed by EV Signing Certificate and Microsoft Windows Hardware Compatibility Publisher(WHLKWHQL)
With Secure Boot on Win 10 machine, I got the error code 39(Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked.)
Here is the full setup log.
The EV Signing Certificate's SN is not in its CRL Distribution Point list.
So, why dose device manager told me my driver's certificate for this file has been revoked?
BTW on Windows 10 and later, its recommend using HLK not HCK.
, thx for the help of @user71659. Now everything works well.
drivers certificate digital-signature code-signing
add a comment |
Well, the driver was signed by EV Signing Certificate and Microsoft Windows Hardware Compatibility Publisher(WHLKWHQL)
With Secure Boot on Win 10 machine, I got the error code 39(Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked.)
Here is the full setup log.
The EV Signing Certificate's SN is not in its CRL Distribution Point list.
So, why dose device manager told me my driver's certificate for this file has been revoked?
BTW on Windows 10 and later, its recommend using HLK not HCK.
, thx for the help of @user71659. Now everything works well.
drivers certificate digital-signature code-signing
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38
add a comment |
Well, the driver was signed by EV Signing Certificate and Microsoft Windows Hardware Compatibility Publisher(WHLKWHQL)
With Secure Boot on Win 10 machine, I got the error code 39(Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked.)
Here is the full setup log.
The EV Signing Certificate's SN is not in its CRL Distribution Point list.
So, why dose device manager told me my driver's certificate for this file has been revoked?
BTW on Windows 10 and later, its recommend using HLK not HCK.
, thx for the help of @user71659. Now everything works well.
drivers certificate digital-signature code-signing
Well, the driver was signed by EV Signing Certificate and Microsoft Windows Hardware Compatibility Publisher(WHLKWHQL)
With Secure Boot on Win 10 machine, I got the error code 39(Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked.)
Here is the full setup log.
The EV Signing Certificate's SN is not in its CRL Distribution Point list.
So, why dose device manager told me my driver's certificate for this file has been revoked?
BTW on Windows 10 and later, its recommend using HLK not HCK.
, thx for the help of @user71659. Now everything works well.
drivers certificate digital-signature code-signing
drivers certificate digital-signature code-signing
edited Jan 23 at 7:45
Ahmed Ashour
1,3401715
1,3401715
asked Jan 21 at 2:11
Jack MartinJack Martin
84
84
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38
add a comment |
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38
add a comment |
1 Answer
1
active
oldest
votes
According to the screenshot in the comments, your driver was submitted for WHQL test signing. The problem is likely that your system you are installing on is not properly configured for test signed drivers.
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396436%2fwindows-10-driverwithout-hardware-device-with-error-39-0xc0000603-certificat%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to the screenshot in the comments, your driver was submitted for WHQL test signing. The problem is likely that your system you are installing on is not properly configured for test signed drivers.
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
add a comment |
According to the screenshot in the comments, your driver was submitted for WHQL test signing. The problem is likely that your system you are installing on is not properly configured for test signed drivers.
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
add a comment |
According to the screenshot in the comments, your driver was submitted for WHQL test signing. The problem is likely that your system you are installing on is not properly configured for test signed drivers.
According to the screenshot in the comments, your driver was submitted for WHQL test signing. The problem is likely that your system you are installing on is not properly configured for test signed drivers.
answered Jan 21 at 2:43
user71659user71659
1263
1263
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
add a comment |
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
how can I make a reales one? I followed these steps. If its a test version, there is no other checkbox(options) when I saw on the site when I make a submission.
– Jack Martin
Jan 21 at 3:45
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
now on win 10 test machine, I installed the 'test version' driver for a new Test Report from HLK Studio, and with that report for a new Submission to see what going on.
– Jack Martin
Jan 21 at 3:49
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396436%2fwindows-10-driverwithout-hardware-device-with-error-39-0xc0000603-certificat%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why are you censoring the name of the driver? If we know the name of the driver, we could find out what's going on behind it. Likely the driver or manufacturer has had some sort of security compromise or is malicious.
– user71659
Jan 21 at 2:18
@user71659 will the name of driver cause this issue? It's a test driver written by me. It's not a official name, and I have update the log with driver name.
– Jack Martin
Jan 21 at 2:28
@user71659 if you need something else, just let me know. And THX!!!!!
– Jack Martin
Jan 21 at 2:28
So you wrote the driver yourself and sent it to Microsoft for WHQL testing and signing?
– user71659
Jan 21 at 2:33
@user71659 Yes, screen sortcut
– Jack Martin
Jan 21 at 2:38