Windows Virtual Machine from .VHD
up vote
-1
down vote
favorite
I have virtualised a windows machine using "Disk2VHD" from microsoft sysinternals. I then used Windows virtual machine to create a VM from the .VHD file. I ensured the "Prepare for use in VM" box was checked.
Upon boot I get a "Windows not genuine" error, and the VM will restart.
I've mounted the VHD in diskmgmt, and can access all the information on the disk.
The system i've virtualised is a geniune OEM windows XP Machine. with a 60GB HDD.
Is this a problem of Hardware mis-match?
windows windows-xp virtual-machine
asked Nov 14 at 15:32
Thom G
46211
add a comment |
up vote
-1
down vote
favorite
I have virtualised a windows machine using "Disk2VHD" from microsoft sysinternals. I then used Windows virtual machine to create a VM from the .VHD file. I ensured the "Prepare for use in VM" box was checked.
Upon boot I get a "Windows not genuine" error, and the VM will restart.
I've mounted the VHD in diskmgmt, and can access all the information on the disk.
The system i've virtualised is a geniune OEM windows XP Machine. with a 60GB HDD.
Is this a problem of Hardware mis-match?
windows windows-xp virtual-machine
asked Nov 14 at 15:32
Thom G
46211
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have virtualised a windows machine using "Disk2VHD" from microsoft sysinternals. I then used Windows virtual machine to create a VM from the .VHD file. I ensured the "Prepare for use in VM" box was checked.
Upon boot I get a "Windows not genuine" error, and the VM will restart.
I've mounted the VHD in diskmgmt, and can access all the information on the disk.
The system i've virtualised is a geniune OEM windows XP Machine. with a 60GB HDD.
Is this a problem of Hardware mis-match?
windows windows-xp virtual-machine
asked Nov 14 at 15:32
Thom G
46211
I have virtualised a windows machine using "Disk2VHD" from microsoft sysinternals. I then used Windows virtual machine to create a VM from the .VHD file. I ensured the "Prepare for use in VM" box was checked.
Upon boot I get a "Windows not genuine" error, and the VM will restart.
I've mounted the VHD in diskmgmt, and can access all the information on the disk.
The system i've virtualised is a geniune OEM windows XP Machine. with a 60GB HDD.
Is this a problem of Hardware mis-match?
windows windows-xp virtual-machine
windows windows-xp virtual-machine
asked Nov 14 at 15:32
Thom G
46211
asked Nov 14 at 15:32
Thom G
46211
asked Nov 14 at 15:32
Thom G
46211
asked Nov 14 at 15:32
Thom G
46211
asked Nov 14 at 15:32
Thom G
46211
46211
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36
add a comment |
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Yes. OEM licenses are tied to the hardware (the CPU&motherboard) that they were sold on. "License lives and dies with the computer it was originally installed on" to quote a forum post.
- https://community.spiceworks.com/topic/1963771-licensing-after-virtualizing-windows-xp-physical-machine
- https://www.experts-exchange.com/questions/26534530/How-to-Legaly-P2V-an-XP-OEM-Machine.html
(Retail licenses also require hardware check, but may be reactivated on a different system a few times. VLK licenses in WinXP aren't bound to the system at all.)
If you have a Retail or VLK key, it might be possible to change the license key on an existing system using this script from MS Support or this "key update tool" (both from Microsoft), although the article doesn't say whether it'll allow changing between different licensing channels.
answered Nov 14 at 15:36
grawity
228k35477540
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Yes. OEM licenses are tied to the hardware (the CPU&motherboard) that they were sold on. "License lives and dies with the computer it was originally installed on" to quote a forum post.
- https://community.spiceworks.com/topic/1963771-licensing-after-virtualizing-windows-xp-physical-machine
- https://www.experts-exchange.com/questions/26534530/How-to-Legaly-P2V-an-XP-OEM-Machine.html
(Retail licenses also require hardware check, but may be reactivated on a different system a few times. VLK licenses in WinXP aren't bound to the system at all.)
If you have a Retail or VLK key, it might be possible to change the license key on an existing system using this script from MS Support or this "key update tool" (both from Microsoft), although the article doesn't say whether it'll allow changing between different licensing channels.
answered Nov 14 at 15:36
grawity
228k35477540
add a comment |
up vote
1
down vote
accepted
Yes. OEM licenses are tied to the hardware (the CPU&motherboard) that they were sold on. "License lives and dies with the computer it was originally installed on" to quote a forum post.
- https://community.spiceworks.com/topic/1963771-licensing-after-virtualizing-windows-xp-physical-machine
- https://www.experts-exchange.com/questions/26534530/How-to-Legaly-P2V-an-XP-OEM-Machine.html
(Retail licenses also require hardware check, but may be reactivated on a different system a few times. VLK licenses in WinXP aren't bound to the system at all.)
If you have a Retail or VLK key, it might be possible to change the license key on an existing system using this script from MS Support or this "key update tool" (both from Microsoft), although the article doesn't say whether it'll allow changing between different licensing channels.
answered Nov 14 at 15:36
grawity
228k35477540
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Yes. OEM licenses are tied to the hardware (the CPU&motherboard) that they were sold on. "License lives and dies with the computer it was originally installed on" to quote a forum post.
- https://community.spiceworks.com/topic/1963771-licensing-after-virtualizing-windows-xp-physical-machine
- https://www.experts-exchange.com/questions/26534530/How-to-Legaly-P2V-an-XP-OEM-Machine.html
(Retail licenses also require hardware check, but may be reactivated on a different system a few times. VLK licenses in WinXP aren't bound to the system at all.)
If you have a Retail or VLK key, it might be possible to change the license key on an existing system using this script from MS Support or this "key update tool" (both from Microsoft), although the article doesn't say whether it'll allow changing between different licensing channels.
answered Nov 14 at 15:36
grawity
228k35477540
Yes. OEM licenses are tied to the hardware (the CPU&motherboard) that they were sold on. "License lives and dies with the computer it was originally installed on" to quote a forum post.
- https://community.spiceworks.com/topic/1963771-licensing-after-virtualizing-windows-xp-physical-machine
- https://www.experts-exchange.com/questions/26534530/How-to-Legaly-P2V-an-XP-OEM-Machine.html
(Retail licenses also require hardware check, but may be reactivated on a different system a few times. VLK licenses in WinXP aren't bound to the system at all.)
If you have a Retail or VLK key, it might be possible to change the license key on an existing system using this script from MS Support or this "key update tool" (both from Microsoft), although the article doesn't say whether it'll allow changing between different licensing channels.
answered Nov 14 at 15:36
grawity
228k35477540
answered Nov 14 at 15:36
grawity
228k35477540
answered Nov 14 at 15:36
grawity
228k35477540
answered Nov 14 at 15:36
grawity
228k35477540
228k35477540
add a comment |
add a comment |
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%2f1375364%2fwindows-virtual-machine-from-vhd%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
Besides the fact that you shouldn't be using XP in 2018, the OEM license is valid only for the hardware it was sold with. Using the OS in a VM requires another license (and you can't obtain one now for XP anyway).
– GabrielaGarcia
Nov 14 at 15:36