Hyper-V VM won't boot from Cd, error: “unsigned image's hash is not allowed”Can't start Hyper-V VM -...
Deal the cards to the players
Why did the Cray-1 have 8 parity bits per word?
How to fix my table, centering of columns
Correct physics behind the colors on CD (compact disc)?
Would the melodic leap of the opening phrase of Mozart's K545 be considered dissonant?
Draw bounding region by list of points
PTIJ: Mordechai mourning
If there are any 3nion, 5nion, 7nion, 9nion, 10nion, etc.
How do we objectively assess if a dialogue sounds unnatural or cringy?
Find maximum of the output from reduce
Practical reasons to have both a large police force and bounty hunting network?
Should we avoid writing fiction about historical events without extensive research?
Is there a math equivalent to the conditional ternary operator?
Are small insurances worth it
PTIJ: Is all laundering forbidden during the 9 days?
“I had a flat in the centre of town, but I didn’t like living there, so …”
Make me a metasequence
Did Amazon pay $0 in taxes last year?
Are there other characters in the Star Wars universe who had damaged bodies and needed to wear an outfit like Darth Vader?
Levi-Civita symbol: 3D matrix
is 'sed' thread safe
Why do phishing e-mails use faked e-mail addresses instead of the real one?
Can an earth elemental drown/bury its opponent underground using earth glide?
Relationship between the symmetry number of a molecule as used in rotational spectroscopy and point group
Hyper-V VM won't boot from Cd, error: “unsigned image's hash is not allowed”
Can't start Hyper-V VM - error hypervisor is not runningBooting to a black screen without cursor in Windows 10Attempted to dual boot Windows 10 and Fedora, now completely locked out of booting to WindowsHyper-V Could Not Connect to MobyLinuxVM of Docker & Docker Won't RunWindows 10 on Dual Boot System with Debian 9 won't shutdown properlyError when trying to activate Hyper-V feature, assembly not foundVHD from WIM won't bootUnable to boot; 0xc000000f errorNo partition active; Reboot and select proper boot deviceAfter booting windows 10 from usb getting bsod: KERNEL SECURITY CHECK FAILURE
I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".
Finding information about this error on the internet is proving to be difficult.
windows-10 hyper-v bootable-media
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
add a comment |
I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".
Finding information about this error on the internet is proving to be difficult.
windows-10 hyper-v bootable-media
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
add a comment |
I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".
Finding information about this error on the internet is proving to be difficult.
windows-10 hyper-v bootable-media
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".
Finding information about this error on the internet is proving to be difficult.
windows-10 hyper-v bootable-media
windows-10 hyper-v bootable-media
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
asked Jan 14 '16 at 8:19
ThomasThomas
2,4073813
2,4073813
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.
To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.
Update:
As mentioned by Itai Bar-Haim in the comments, and Thee Gamefanatic said in their answer, you can also select a different template depending on the OS image you're attempting to boot. Be aware that these templates are mutually exclusive - this means that you will not be able to boot a Windows OS image if you select the "Microsoft UEFI Certificate Authority" template.
Microsoft has a thorough deep dive into Secure Boot and how it works available on this blog:
https://blogs.technet.microsoft.com/dubaisec/2016/03/14/diving-into-secure-boot/
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
add a comment |
Disable Secure Boot option in the VM Settings:
This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
add a comment |
I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.
Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
add a comment |
This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
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%2f1026190%2fhyper-v-vm-wont-boot-from-cd-error-unsigned-images-hash-is-not-allowed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.
To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.
Update:
As mentioned by Itai Bar-Haim in the comments, and Thee Gamefanatic said in their answer, you can also select a different template depending on the OS image you're attempting to boot. Be aware that these templates are mutually exclusive - this means that you will not be able to boot a Windows OS image if you select the "Microsoft UEFI Certificate Authority" template.
Microsoft has a thorough deep dive into Secure Boot and how it works available on this blog:
https://blogs.technet.microsoft.com/dubaisec/2016/03/14/diving-into-secure-boot/
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
add a comment |
This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.
To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.
Update:
As mentioned by Itai Bar-Haim in the comments, and Thee Gamefanatic said in their answer, you can also select a different template depending on the OS image you're attempting to boot. Be aware that these templates are mutually exclusive - this means that you will not be able to boot a Windows OS image if you select the "Microsoft UEFI Certificate Authority" template.
Microsoft has a thorough deep dive into Secure Boot and how it works available on this blog:
https://blogs.technet.microsoft.com/dubaisec/2016/03/14/diving-into-secure-boot/
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
add a comment |
This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.
To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.
Update:
As mentioned by Itai Bar-Haim in the comments, and Thee Gamefanatic said in their answer, you can also select a different template depending on the OS image you're attempting to boot. Be aware that these templates are mutually exclusive - this means that you will not be able to boot a Windows OS image if you select the "Microsoft UEFI Certificate Authority" template.
Microsoft has a thorough deep dive into Secure Boot and how it works available on this blog:
https://blogs.technet.microsoft.com/dubaisec/2016/03/14/diving-into-secure-boot/
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.
To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.
Update:
As mentioned by Itai Bar-Haim in the comments, and Thee Gamefanatic said in their answer, you can also select a different template depending on the OS image you're attempting to boot. Be aware that these templates are mutually exclusive - this means that you will not be able to boot a Windows OS image if you select the "Microsoft UEFI Certificate Authority" template.
Microsoft has a thorough deep dive into Secure Boot and how it works available on this blog:
https://blogs.technet.microsoft.com/dubaisec/2016/03/14/diving-into-secure-boot/
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
edited yesterday
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
answered Jan 14 '16 at 8:19
ThomasThomas
2,4073813
2,4073813
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
add a comment |
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya.
– Rob
Jun 30 '16 at 19:08
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ?
– Raphael Teubner
Dec 4 '16 at 18:19
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation.
– Thomas
Dec 5 '16 at 1:01
5
5
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm.
– Itai Bar-Haim
Feb 7 '18 at 8:16
Works perfectly!
– Damian
Aug 31 '18 at 9:33
Works perfectly!
– Damian
Aug 31 '18 at 9:33
add a comment |
Disable Secure Boot option in the VM Settings:
This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
add a comment |
Disable Secure Boot option in the VM Settings:
This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
add a comment |
Disable Secure Boot option in the VM Settings:
This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
Disable Secure Boot option in the VM Settings:
This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
answered Oct 1 '16 at 11:52
MikhailMikhail
84511322
84511322
add a comment |
add a comment |
I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.
Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
add a comment |
I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.
Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
add a comment |
I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.
Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.
Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
answered Oct 28 '17 at 18:05
Thee GamefanaticThee Gamefanatic
211
211
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
add a comment |
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
how do you set the value of $VM?
– code_monk
Nov 24 '17 at 16:41
1
1
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen.
– devrelm
Dec 11 '17 at 16:04
add a comment |
This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
add a comment |
This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
add a comment |
This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
answered Jun 12 '18 at 9:22
Jeevan KulkarniJeevan Kulkarni
111
111
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%2f1026190%2fhyper-v-vm-wont-boot-from-cd-error-unsigned-images-hash-is-not-allowed%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
