VMware deactivated XP Pro

[scbs29]

I recently dowloaded VMware server 2 for Windows to try it out. The
file was VMware-server-2.0.1-156745.exe.

I installed onto my Windows XP Pro SP3 system, accepting all of the
defaults, and rebooted as requested.

When I rebooted I was informed to the effect that my hardware had
changed drastically and that I had to reactivate my XP within 3 days.
Needless to say, my hardware had not changed, the only change was the
installation of VMware server.

My installation of XP Pro is 6 years old. In those 6 years I have
added 1Gb RAM, a second internal hdd and replaced the graphics card
when the fan on the original one died. I am sure you wil alll agree,
not an excessive number of changes.

Luckily I had installed using Ashampoo UnInstaller and was able to
remove all traces of VMware. I still had to contact Microft, however,
to reactivate my XP.

What is going on ??

Why did VMware server deactivate my XP installation? If I did decide
to go the VMware route for virtualisation is this likely to happen
again ?

If I reinstall and the same thing happens again, ie. my XP Pro is
deactivated, what is the reaction likely to be if I apply to activate
yet again ?

Also if I decide not to go the VMware route after trying it out then
uninstallation may well lead to my XP being yet again deactivated.

I am rather concerned about all this, since if I have to keep
reactivating then I might find myself in the position of those who I
gather have had their activation revoked.

I had a reply from a posting on the VMware forums that "The only
changes I can think of is the addition of 3 virtual network adapters
on the host. "
Could this be the problem ?
As I have inferred above, it is not the install/uninstall etc of
VMware that concerns me, but the effect of accumulative reactivations.

remove fred before emailing

 

[Jose]

I recently dowloaded VMware server 2 for Windows to try it out. The
file was VMware-server-2.0.1-156745.exe.

I installed onto my Windows XP Pro SP3 system, accepting all of the
defaults, and rebooted as requested.

When I rebooted I was informed to the effect that my hardware had
changed drastically and that I had to reactivate my XP within 3 days.
Needless to say, my hardware had not changed, the only change was the
installation of VMware server.

My installation of XP Pro is 6 years old. In those 6 years I have
added 1Gb RAM, a second internal hdd and replaced the graphics card
when the fan on the original one died. I am sure you wil alll agree,
not an excessive number of changes.

Luckily I had installed using Ashampoo UnInstaller and was able to
remove all traces of VMware. I still had to contact Microft, however,
to reactivate my XP.

What is going on ??

Why did VMware server deactivate my XP installation? If I did decide
to go the VMware route for virtualisation is this likely to happen
again ?

If I reinstall and the same thing happens again, ie. my XP Pro is
deactivated, what is the reaction likely to be if I apply to activate
yet again ?

Also if I decide not to go the VMware route after trying it out then
uninstallation may well lead to my XP being yet again deactivated.

I am rather concerned about all this, since if I have to keep
reactivating then I might find myself in the position of those who I
gather have had their activation revoked.

I had a reply from a posting on the VMware forums that "The only
changes I can think of is the addition of 3 virtual network adapters
on the host. "
Could this be the problem ?
As I have inferred above, it is not the install/uninstall etc of
VMware that concerns me, but the effect of accumulative reactivations.

remove fred before emailing

I think XP is behaving according to design.

When you activate (I don't know all the details), Microsoft keeps some
information about your license and hardware setup and considers then a
set.

This help prevent theft so that if your XP license is installed on
some vastly different hardware that does not match what it thinks it
should be, you will get that message.

Small hardware changes are tolerated, but sudden big changes raise the
flag of suspicion.

I don't know what VMWare did, but Microsoft seems to think it is a
problem because your licese doesn't appear to match your original
hardware anymore (not you personally - your license).

Say you got a whole new computer and tried to install your XP on it -
it might fail since it doesn't match the hardware it was originally
activated with. You might be a thief!

My understanding is if you call them and can convince them they will
reactive your somehow.

Just give 'em a call and they will be happy to help you, I'm sure.

Or, check with the VMWare people and see what they say.

 

[VanguardLH]

I recently dowloaded VMware server 2 for Windows to try it out. The
file was VMware-server-2.0.1-156745.exe.

When I rebooted I was informed to the effect that my hardware had
changed drastically and that I had to reactivate my XP within 3 days.

The installation added virtual devices for networking used by VMware to
communicate to the guests you define within it. Presumably you are
asking about the host OS and not a guest OS you created inside of VMware
Server.

Activation takes a snapshot of your hardware (its major subsystems).
When you change one or two, not enough has changed to make your host
look like a new computer. You can eventually make enough cumulative
changes that the prior snapshot is too different from the current
hardware setup. Then WGA kicks in again to have you re-activate.

So if you have a legitimate license for Windows XP, why didn't you
activate it (again)?