How can I activate an older OS on a physical disk that I have bound to a Hyper-V Computer

Scott Phillips 0 Reputation points
2026-03-06T15:31:43.82+00:00

I am trying to set up a Hyper-V computer using a physical disk from another computer. It is an XP machine. It sets up and runs ok, but it wants to be activated. When I use the original key from the original installation, it says it is not valid. Is there any way to activate this? It gives me the option to phone in, but the phone number is no longer working.

Windows for home | Previous Windows versions | Licensing and activation
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-03-06T15:32:01.1266667+00:00

    Windows XP and other legacy Microsoft products still require activation, but assisted phone support for activating Windows XP is no longer available. Only the automated methods described in the Product Activation Wizard remain supported.

    Key points from the current behavior of legacy activation:

    1. Product activation is still required
      • Windows XP must be activated within the grace period; activation is used to validate that the license is legitimate and not used beyond the terms.
      • Moving an existing installation to different hardware (including into a VM) can trigger reactivation because it is treated as a different computer.
    2. OEM and hardware-bound licenses
      • Many XP installations (especially from large PC vendors) are OEM licenses that are tied to the original hardware and BIOS (for example via ACPI_SLIC/OEM activation mechanisms).
      • When that installation is moved to different hardware or a virtual machine, the original OEM activation mechanism no longer works, and the original key may be rejected as invalid in that new environment.
    3. Legacy activation support limits
      • For Windows XP and Windows Vista, assisted support (talking to a support agent) for activation is no longer available; only the automated systems exposed through the Product Activation Wizard are supported.
      • Product activation telephone numbers are not published directly; the correct regional number is obtained only through the Product Activation Wizard. If the number surfaced there is no longer working, there is no alternate assisted channel documented for XP.
    4. Practical implication for this scenario
      • An XP installation that has been moved from its original physical machine to a Hyper‑V VM is effectively on new hardware from the activation system’s perspective.
      • If the original key is OEM and tied to the original machine, it is not licensed for activation on different hardware (including a VM). In that case, activation on the Hyper‑V guest is not supported by the license terms.
      • If the automated phone/online activation paths exposed by the XP Product Activation Wizard no longer complete successfully, there is no supported way documented to force activation of that legacy OS instance on new hardware.

    In summary, when an XP installation is moved to a Hyper‑V VM and the original key is rejected, and the phone activation path provided by the wizard no longer works, there is no supported method to newly activate that XP instance on the virtual hardware. A properly licensed XP environment would need to be installed and activated according to its license terms on supported activation channels, or a supported, modern Windows version should be used instead.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.