VirtualBox can't start any VM because of certificate expiration
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
So today I started my Windows Server 2008 R2 virtual machine and got an error saying this:
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
And I did take a look on the VBoxHardening.log file. I noticed several lines about crypt32.dll. But I didn't found any information about this problem on Windows 10, and I tried to reinstall VirtualBox three times. Then I checked my crypt32.dll file and it's certificate was expired.
I changed the date on computer to 05.08.2018 and it worked. But it's temporary solution as changing the date breaks many other certificates.
I'm running Windows 10 Pro (build 1809).
Here is the error in VBoxHardening.log:
1268.143c: Fatal error:
1268.143c: Error loading 'crypt32.dll': 1790 [C:WINDOWSsystem32crypt32.dll]
52c.2528: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 658 ms, the end);
2f14.1988: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1156 ms, the end);
windows-10 virtualbox certificate
asked Feb 5 at 15:21
dengr1065dengr1065
266
|
show 7 more comments
So today I started my Windows Server 2008 R2 virtual machine and got an error saying this:
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
And I did take a look on the VBoxHardening.log file. I noticed several lines about crypt32.dll. But I didn't found any information about this problem on Windows 10, and I tried to reinstall VirtualBox three times. Then I checked my crypt32.dll file and it's certificate was expired.
I changed the date on computer to 05.08.2018 and it worked. But it's temporary solution as changing the date breaks many other certificates.
I'm running Windows 10 Pro (build 1809).
Here is the error in VBoxHardening.log:
1268.143c: Fatal error:
1268.143c: Error loading 'crypt32.dll': 1790 [C:WINDOWSsystem32crypt32.dll]
52c.2528: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 658 ms, the end);
2f14.1988: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1156 ms, the end);
windows-10 virtualbox certificate
asked Feb 5 at 15:21
dengr1065dengr1065
266
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
1
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48
|
show 7 more comments
So today I started my Windows Server 2008 R2 virtual machine and got an error saying this:
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
And I did take a look on the VBoxHardening.log file. I noticed several lines about crypt32.dll. But I didn't found any information about this problem on Windows 10, and I tried to reinstall VirtualBox three times. Then I checked my crypt32.dll file and it's certificate was expired.
I changed the date on computer to 05.08.2018 and it worked. But it's temporary solution as changing the date breaks many other certificates.
I'm running Windows 10 Pro (build 1809).
Here is the error in VBoxHardening.log:
1268.143c: Fatal error:
1268.143c: Error loading 'crypt32.dll': 1790 [C:WINDOWSsystem32crypt32.dll]
52c.2528: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 658 ms, the end);
2f14.1988: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1156 ms, the end);
windows-10 virtualbox certificate
asked Feb 5 at 15:21
dengr1065dengr1065
266
So today I started my Windows Server 2008 R2 virtual machine and got an error saying this:
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
And I did take a look on the VBoxHardening.log file. I noticed several lines about crypt32.dll. But I didn't found any information about this problem on Windows 10, and I tried to reinstall VirtualBox three times. Then I checked my crypt32.dll file and it's certificate was expired.
I changed the date on computer to 05.08.2018 and it worked. But it's temporary solution as changing the date breaks many other certificates.
I'm running Windows 10 Pro (build 1809).
Here is the error in VBoxHardening.log:
1268.143c: Fatal error:
1268.143c: Error loading 'crypt32.dll': 1790 [C:WINDOWSsystem32crypt32.dll]
52c.2528: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 658 ms, the end);
2f14.1988: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1156 ms, the end);
windows-10 virtualbox certificate
windows-10 virtualbox certificate
asked Feb 5 at 15:21
dengr1065dengr1065
266
asked Feb 5 at 15:21
dengr1065dengr1065
266
edited Feb 5 at 15:42
dengr1065
asked Feb 5 at 15:21
dengr1065dengr1065
266
asked Feb 5 at 15:21
dengr1065dengr1065
266
asked Feb 5 at 15:21
dengr1065dengr1065
266
266
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
1
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48
|
show 7 more comments
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
1
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
1
1
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48
|
show 7 more comments
1 Answer
1
active
oldest
votes
I forgot that I have an Windows 10 ISO. So here's what I did.
First, I mounted the ISO by double-clicking on it.
Then, I opened sourcesinstall.wim file using 7-zip.
I navigated to 1Windowssystem32 and copied the crypt32.dll file.
Checked digital signature and it was valid.
Then I did reboot to recovery mode with command line, made a backup and replaced the file using these commands:
c:
cd WINDOWSsystem32
mv crypt32.dll crypt32.dll.bak
mv C:Users<username>Desktopcrypt32.dll crypt32.dll
I closed the Command Line window and did reboot to normal mode.
answered Feb 5 at 16:40
dengr1065dengr1065
266
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%2f1402296%2fvirtualbox-cant-start-any-vm-because-of-certificate-expiration%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
I forgot that I have an Windows 10 ISO. So here's what I did.
First, I mounted the ISO by double-clicking on it.
Then, I opened sourcesinstall.wim file using 7-zip.
I navigated to 1Windowssystem32 and copied the crypt32.dll file.
Checked digital signature and it was valid.
Then I did reboot to recovery mode with command line, made a backup and replaced the file using these commands:
c:
cd WINDOWSsystem32
mv crypt32.dll crypt32.dll.bak
mv C:Users<username>Desktopcrypt32.dll crypt32.dll
I closed the Command Line window and did reboot to normal mode.
answered Feb 5 at 16:40
dengr1065dengr1065
266
add a comment |
I forgot that I have an Windows 10 ISO. So here's what I did.
First, I mounted the ISO by double-clicking on it.
Then, I opened sourcesinstall.wim file using 7-zip.
I navigated to 1Windowssystem32 and copied the crypt32.dll file.
Checked digital signature and it was valid.
Then I did reboot to recovery mode with command line, made a backup and replaced the file using these commands:
c:
cd WINDOWSsystem32
mv crypt32.dll crypt32.dll.bak
mv C:Users<username>Desktopcrypt32.dll crypt32.dll
I closed the Command Line window and did reboot to normal mode.
answered Feb 5 at 16:40
dengr1065dengr1065
266
add a comment |
I forgot that I have an Windows 10 ISO. So here's what I did.
First, I mounted the ISO by double-clicking on it.
Then, I opened sourcesinstall.wim file using 7-zip.
I navigated to 1Windowssystem32 and copied the crypt32.dll file.
Checked digital signature and it was valid.
Then I did reboot to recovery mode with command line, made a backup and replaced the file using these commands:
c:
cd WINDOWSsystem32
mv crypt32.dll crypt32.dll.bak
mv C:Users<username>Desktopcrypt32.dll crypt32.dll
I closed the Command Line window and did reboot to normal mode.
answered Feb 5 at 16:40
dengr1065dengr1065
266
I forgot that I have an Windows 10 ISO. So here's what I did.
First, I mounted the ISO by double-clicking on it.
Then, I opened sourcesinstall.wim file using 7-zip.
I navigated to 1Windowssystem32 and copied the crypt32.dll file.
Checked digital signature and it was valid.
Then I did reboot to recovery mode with command line, made a backup and replaced the file using these commands:
c:
cd WINDOWSsystem32
mv crypt32.dll crypt32.dll.bak
mv C:Users<username>Desktopcrypt32.dll crypt32.dll
I closed the Command Line window and did reboot to normal mode.
answered Feb 5 at 16:40
dengr1065dengr1065
266
answered Feb 5 at 16:40
dengr1065dengr1065
266
answered Feb 5 at 16:40
dengr1065dengr1065
266
answered Feb 5 at 16:40
dengr1065dengr1065
266
266
add a comment |
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%2f1402296%2fvirtualbox-cant-start-any-vm-because-of-certificate-expiration%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
What version of VirtualBox?
– Kinnectus
Feb 5 at 15:25
@Kinnectus last, 6.0.4
– dengr1065
Feb 5 at 15:26
Also I don't think there's something to do with VirtualBox. crypt32.dll's certificate is expired.
– dengr1065
Feb 5 at 15:28
Can you post the VBoxHardening.log lines where the file is rejected?
– Kinnectus
Feb 5 at 15:39
1
@Kinnectus already did it, nothing changed (I rebooted after scan)
– dengr1065
Feb 5 at 15:48