Opened 9 years ago
Closed 7 months ago
#14263 closed defect (fixed)
Unable to start Windows 10 64 build 10162 (preview) guest under i686 Linux host: The digital signature for this file couldn't be verified
Reported by: | Artem S. Tashkinov | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
I have troubles trying to run the preview of Windows 10 64 build 10162 (Windows10_InsiderPreview_x64_EN-US_10162.iso) under Linux (i686 PAE) using VirtualBox 5.0.
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.
This is a cross post from here: https://forums.virtualbox.org/viewtopic.php?f=2&t=68840
Attachments (4)
Change History (23)
by , 9 years ago
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Same issue as birdie - Host: Windows 8.1 x64 Guest: en_windows_10_enterprise_insider_preview_10074_vhd_x64_6677120.vhd
comment:3 by , 9 years ago
Microsoft since has turned down all the ISOs, but they can be trivially found via torrents or I can upload the image to Google Docs for your pleasure. The final ISOs will be released soon.
follow-up: 5 comment:4 by , 9 years ago
Exactly the same issue. Work around is to rename c:\windows\system32\drivers\VBoxGuest.sys to something else - I mounted the VDI within a Linux VM to do this. Once into Windows, the signature is reported as 'OK' by 'File => Properties => Digital signature'
comment:5 by , 9 years ago
Replying to NikNakk:
Exactly the same issue. Work around is to rename c:\windows\system32\drivers\VBoxGuest.sys to something else - I mounted the VDI within a Linux VM to do this. Once into Windows, the signature is reported as 'OK' by 'File => Properties => Digital signature'
The initial bug report is about not being able to install Windows 10 64 under VirtualBox. Your problem seems to be totally different (you cannot run it after installation due to "bad" VirtualBox drivers).
comment:6 by , 9 years ago
The final build of Windows 10 64 (en_windows_10_pro_10240_x64_dvd.iso) cannot be installed as well with the same error message.
comment:7 by , 9 years ago
VirtualBox 5.0 running on a 64bit of Windows have no problems installing Windows 10 64.
follow-up: 9 comment:8 by , 9 years ago
So it's most likely the same problem as #14262. Does disbling nested paging work around the problem?
comment:9 by , 9 years ago
by , 9 years ago
Attachment: | VBoxLog.tar.bz2 added |
---|
VirtualBox log files: bad vs good with basically the same settings except Nested Pages
comment:10 by , 9 years ago
I've noticed that Nested Pages enable the following CPU instructions (they are otherwise disabled):
PCLMUL - PCLMULQDQ support (for AES-GCM) POPCNT - POPCNT instruction AES - AES instructions XSAVE - XSAVE instruction AVX - AVX support
And without these instructions the guest works. It might be possible that "Nested Pages" itself is not the culprit but the implementation of these functions is.
comment:11 by , 9 years ago
Meanwhile Windows 7 64 BSOD's on installation (with Nested Pages enabled).
Without Nested Pages 64 bit OSes are unusable (run absolutely slowly).
comment:12 by , 9 years ago
Test build 101882 fixes this problem. Hopefully 5.0.1 will be released with this fix.
Thanks!
comment:14 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:15 by , 9 years ago
I have the same problem after upgrading Guest Additions from 5.0.0 to 5.0.2 version
comment:16 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:17 by , 9 years ago
colorprint, very unlikely that the Guest Additions have something to do with such kind of error. Please attach a VBox.log file of a VM session where you experienced this problem.
comment:19 by , 7 months ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I have tried disabling audio/network/usb (by converting mouse to PS/2) and also I attached the ISO to an IDE adapter - yet nothing helps.