Avoiding Reactivation on Windows Guests

[jlacroix]

Hello everyone. My second (and final) question of the day revolves around Windows guests on Linux hosts. I have a laptop (currently Arch Linux) that runs a Windows 7 VM with Office 2010 also installed. Both Windows 7 and Office 2010 are genuine licensed copies.

Here's the problem. I frequently try new Linux distributions on my laptop. I have exported my VM to a file using the GUI export utility. Whenever I import it back into my laptop after installing Linux, I have to reactivate both Windows and Office. It's so bad, in fact, that I have the three-user version of Office 2010, and Microsoft thinks I have it on more than one machine (making me have to activate by phone) even though I have only ever installed Office on this laptop and have never used the other two installations. Windows 7 makes me call in to activate each time as well, because I must have passed how many times you can activate Windows before Microsoft starts asking questions.

I have Googled on this issue, and have found that exporting the VM should work, at least according to what I've read. However, each time I reimport the VM, it needs to be activated again, even though I use the same settings each time. Is there any way to stop the reactivation from being necessary?

[imachavel]

windows activation is a pain


method 1: Deleted by board moderator

method 2: Deleted by board moderator

Watch language and do not post hacking or cracking information again

[jlacroix]

Thank you for your reply. However, I'm not necessarily looking for a way to crack Windows 7's or Office 2010's activation. What I want to do is retain the fact that I already activated the OS and Office, and not need to reactivate Windows and Office if I reinstall the host OS on my laptop.

I can understand if I was using the VM on a different system, but I was hoping that Virtualbox could retain all the hardware ID's and whatever else that is tripping Windows into needing to be reactivated. Maybe there's a setting, or maybe there's a different utility I need to use. Right now, I'm thinking of checking out Linux Mint XFCE (Debian Edition) on my laptop, and I know if I save the VM and re-import it after installing the OS, I'll run into activation again.

And yes, I do get a message after importing the VM that activation is required in three days or something like that. This message is visible when you check the computer properties within Windows 7.

[imachavel]

I don't know what to tell you. I don't know if it's possible. the activation key isn't saved in a folder in linux. it's saved in a folder in windows in the virtual machine. and the folder for the virtual machine is, yes, in fact on the linux host os. BUT, why do you need to reactivate windows if the virtual state is saved and reloaded? you have to reinstall windows? every time you reinstall windows, this same process is going to occur, one way or another. it's a pain, but there is no way to save the activation key in the install settings even when capturing an image. a captured image saves two things, the settings once windows is loaded, and the install files. install configuration I believe is not saved. if I'm wrong I'm wrong but I can't see any other explanation for why windows needs to be reactivated.

Content removed.

[Perryg]

will I get banned from these forums for explaining to you how to crack windows

It a strong possibility!

[imachavel]

good lord. well in that case I have no solution. sorry. any friends that can help you out?

[jlacroix]

To be clear, I'm not reinstalling Windows each time. I'm going into the GUI and exporting the VM before I wipe my system and reinstall Linux. What I'm struggling to understand is why I have to reactivate Windows and Office when I'm reimporting the same VM into Virtualbox again. To me, I liken this to copying the .VirtualBox folder (with all the VM's) and copying the file back (which also doesn't work). I'm trying to understand what makes this necessary, and how to stop it.

No offense to anyone, I really appreciate the help. I'm just trying to understand what causes this problem, and I believe that there has to be a (legitimate and legal) way around this pain.

[Perryg]

The activation has to do with the uuid change when creating the guest. Windows sees this as a changed motherboard and that is enough to trigger activation.
However, instead of exporting and importing which does trigger this you can (since version 4.* of VirtualBox) simply copy the entire guests folder out to a saved location. Then copy it back into the new install and place it back in the VirtualBox VMs folder and dbl click the *.vbox file. Since this does not re-install anything it does not require re-activation.

[imachavel]

I have GOT to memorize this for when I have this same exact problem one day

[jlacroix]

The activation has to do with the uuid change when creating the guest. Windows sees this as a changed motherboard and that is enough to trigger activation.
However, instead of exporting and importing which does trigger this you can (since version 4.* of VirtualBox) simply copy the entire guests folder out to a saved location. Then copy it back into the new install and place it back in the VirtualBox VMs folder and dbl click the *.vbox file. Since this does not re-install anything it does not require re-activation.

Thank you!!! You not only explained why this occurs, you gave me a solution. I really appreciate it!

[Foxy1]

Thank you for the warning. I amalgamated my C & D drives and installed some additional RAM in my laptop before creating my 1st 2 new vms...The guests are both XP, host too. Now I find that my legitimate Microsoft Office requires reactivation. I shaln’t be doing it, there is plenty of good apache stuff.