Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have WXP-64 running on a VM and, for testing and performance reasons, I would like to occasionally change the allocations for it. Changes might include:

  • Number of CPU cores,
  • Amount of RAM
  • Add/remove network adapters.

But I'm concerned that XP will demand re-activation and that I might eventually have licensing issues if I do this.

So, can anyone tell me:

  1. What kind of changes trigger re-activation in XP?
  2. Is there limits or caveat with regard to re-activation?

I've perused this question and the article it references, but wanted more recent and verified info.

(FWIW, I'm not trying to cheat: the OS copy was purchased explicitly for the VM.)

share|improve this question

Windows will trigger the o'l hardware change re-validation when there is an extensive harware change; updating your video card or changing a NIC won't do it but if you remove the drive and connect it to a sepperate machine it will request revalidation.

Microsoft allows the origional purchaser/ license owner to use 'said' license as you see fit and have details about their licenses on their site.

Generally the verification can be done in a few minutes through the prompt online or even on the phone so I would not worry about this step (it is annoying but unless you dig deep into Windows there is no way around it)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.