10 The digital signature for this file couldn't be verified

[birdie]

I have troubles trying to install the preview of Windows 10 64, build 10162 (Windows10_InsiderPreview_x64_EN-US_10162.iso) under Linux (i686 PAE) using VirtualBox 5.0. The release version is also affected.

When I try to boot my Windows 10 64 guest I see this error message:


Recovery

Your PC/Device needs to be repaired

The digital signature for this file couldn't be verified.

Error code: 0xc0000428

My ISO file is correct (verified using SHA1 hash: 31346458255afeac1afeed5c4c61f15d57708b9b)

My host is: Linux 4.1.0 i686 PAE, 16GB of RAM
My guest is: Windows 10 64

People with a totally different HW configuration also have this problem. I have created a bug report here.

[birdie]

The retail version of Windows 10 64 cannot be installed with the same error message.

[loukingjr]

The retail version of Windows 10 64 cannot be installed with the same error message.

There is no retail version yet. And about this…

People with a totally different HW configuration also have this problem. I have created a bug report here.

One person doesn't constitute "people".

[birdie]

Build 10240 is the retail version of Windows 10 as confirmed by numerous sources.

And just like I thought VirtualBox 64 running on a 64bit of Windows have no problems installing Windows 10 64.

[Mighty Joe]

It looks like a number of people having this problem (I can't post links because I just joined)
I'm getting the same "Error code: 0xc0000428" on an OS X host and the Windows 10 x86 10074 build after installing Guest Additions and rebooting. If I don't install Guest Additions, Windows 10 works fine through multiple reboots. Can you run Windows 10 without Guest Additions?

*Edit to add: I tried today's "final release" of Windows 10 and it works fine with Guest Additions. *shrug*

[loukingjr]

I don't know what to say. I've been running Windows 10 on two OSX hosts, One Linux and one Windows host updated to the current 10240 build and I have the guest additions installed. You can run it without guest additions, you just won't have the niceties they give you.

[birdie]

God, I cannot install it! I don't care about freaking Guest Additions.

That's the first message I receive when I try to power on a new virtual machine with a Windows 10 ISO in it.

[birdie]

This is a VirtualBox 5.0 regression: https://www.virtualbox.org/ticket/14262

The solution is to disable "Nested Pages".

[JeWu]

This is a VirtualBox 5.0 regression: virtualbox/ticket/14262
The solution is to disable "Nested Pages".

Well, "Nested Pages" off doesn't do the trick for me.

Instead, almost 2 years down the line, I got just the same error, installing Win10 Enterprise. I don't seem to get it installed in VBox 5.1 under Linux Mint Cinnamon 18.1. Related posts:
- german: forums on linuxmint, topic# 243294
- english: viewtopic.php?f=2&t=82593

[socratis]

@JeWu

1. This is a duplicate post.
2. This is a duplicate post in a dead thread.
3. This is a duplicate post in a dead thread that has nothing to do with the thread.

[JeWu]

#1 is partly correct, but I thought, if somebody was looking around and poked into this old thread, it wouldn't hurt to have a link to a current thread with the same topic.

And #3 is not correct, Sir.
Just look at my posted Error screens.

[socratis]

if somebody was looking around and poked into this old thread, it wouldn't hurt to have a link to a current thread with the same topic.

Yes, it does hurt. Otherwise I can find a gazillion posts with "USB device is busy with a previous request" and start posting on all of them. Not cool. And that's why it's against forums rules. This time I'm not going to delete your post, I'm not going to lock this dead thread and I'm going to explain to you some of the rules. This time only...

I really don't want to lock the thread, in the rare case that someone with the retail Windows version comes by.

And #3 is not correct, Sir.

Yes it is. You do NOT have the retail version. A "BSOD" is a "BSOD", that doesn't mean it's the same cause.

Please do not continue the discussion here...

[Martin]

...and for others stumbling on this thread: The problem now was just a corrupted ISO file so please check for something like this first.