How to get Windows 7 for VM?

[MarkFoley]

No doubt this question has been posted, but I'm new to the forum and didn't find anything ...

I've just downloaded and installed virtualbox 5.1 on Ubuntu 16.04 (the host). I've create my first virtual machine which I intend to be a Windows 7 guest. Now what? The computer I've installed this on is dual-boot Ubuntu/Windows 7. Can I get the WIN7 installation off this machine and into the VM? Windows computers ship with Windows 7 installed, so there isn't really and DVD available. Is there a way to create and ISO from an existing Windows 7 installation?

I know this is elementary, but how to you actually get Windows 7 into the VM?

[towo2099]

I know this is elementary, but how to you actually get Windows 7 into the VM?

https://www.microsoft.com/en-gb/softwar ... d/windows7

[MarkFoley]

I just tried that for the Win7 installed on my laptop. Go the message:

Error

The product key you've entered appears to be for software which was pre-installed by the device manufacturer. Please contact the device manufacturer for software recovery options.

Other options?

[The Raven]

I was faced with a similar situation on my first Windows virtualisation
migration project.

What I did was as follows :
1. Used Paragon Backup to take a complete image backup of my existing
Windows system partition.
2. Create a Windows VM with all the required virtual devices defined,
disk, Ethernet etc.
3. Start the newly created Windows VM using the Stand-Alone Paragon
Backup cd. At this point, you're actually mimicking a bare-metal
restore of your Windows image taken in step 1 within the Virtual machine.
4. Restore your image taken in step 1 to the vdi defined to your VM.
5. Once completed, change boot order within the VM to Disk before CD
and restart the guest.

Windows will start, detect the new (virtual) hardware and ask for (at least)
one reboot.
You will also have to go through Windows Activation due to the number of
hardware changes detected.

Please remember, once you have virtualised your Windows system, the other
instance *MUST* be wiped out, otherwise you will be in breach of the EULA -
namely having the same Windows Licence activated simultaneously on
two different machines (the virtual one in VirtualBox and the real one
on the dual boot).

I've now virtualised both my Windows systems in this manner.

[mpack]

The product key you've entered appears to be for software which was pre-installed by the device manufacturer. Please contact the device manufacturer for software recovery options.

OEM product keys can't be used to activate retail Windows installs, and vice versa. You also mustn't mix home vs pro keys etc.

As to Raven's suggestion, it might work but the P2V'd Win7 will certainly ask to be reactivated, and branded OEM images don't always activate on different hardware (and the virtual hardware is very different).

[The Raven]

I should have stated that both my Windows 7 installs that I virtualised
in that manner were *RETAIL* licences.

In fact I even still had the install CD's in their boxes. However,the prospect
of re-installing from scratch inside a VM and then waiting a whole day
for WIndows Update meant that the backup/restore method described
above was a rather easy decision to make.

[MarkFoley]

I did get the Windows VM installed, although I didn't use the backup image technique The Raven suggested. However, I do have Acronis images, so I'm going to post a question on their forum about whether these can be used to restore to a VM. I would think that if Paragon can do it, so can Acronis (and if not, time to switch backup software!).

I used a Windows Pro 64 installation DVD I had downloaded for a different in-office computer. When installing, I use the product key from the target computer (sticker on box). That all seemed to work, although it took 17 hours just to search for Windows updates.

mpack: as to your comment, " Win7 will certainly ask to be reactivated", that's not a problem. If we go this route in that's exactly what we'll do. I expect this Windows VM will ask me to reactivate sometime in the next 28 days.

Now, I face a different problem. I'll submit a different message to keep issues distinct.

[mpack]

I do have Acronis images, so I'm going to post a question on their forum about whether these can be used to restore to a VM.

Of course they can - a VM is just like any other PC. You'll need an ISO of the Acronis recovery CD.

A very old (but still valid) discussion of mine on the subject:
viewtopic.php?f=7&p=109762

Note however that the tool you use for imaging doesn't affect the issues discussed above. A Disk2VHD image has exactly the same content as an Acronis image, and it's the image content which determines what the image will do when you boot it. I wouldn't bother with Paragon Backup unless you already have that tool and are familiar with it.

[The Raven]

it took 17 hours just to search for Windows updates.

That can be improved on fresh installs.
Once you have Windows 7 installed, you need to install (manually)
patches KB3138612 and KB3145739. KB3138612 is a new version
of the Windows Update Client. For some odd reason you also need
the other (apparently unrelated) patch as well.
Once these are both installed, subsequent Windows Update runs
are (relatively) faster. Both can be obtained from the Download Center.

Without wishing to veer too far off topic, Windows Update will always
be slow as its Component Based Servicing (CBS) is fundamentally flawed.
In Windows 10 they appear to be trying to circumvent the underlying
problem by making all service cumulative, thus reducing the amount
of pre-requisite checking required. In fact, last week it was announced
that cumulative servicing was coming to Windows 7 and 8.1 as well, although
initially only starting from October 2016 Patch Tuesday onwards.