Generally, this situation is resolved by phoning the activation line,
asking to speak to a human, and telling that human that the PC you are
attempting to activate the product is in fcat the same PC that it is
currently activated on.
The bug is not that the activation code tells you the license is in
use (it is, it's on the PC that "changed").
The bug is that an unchanged PC is detected as having been "changed so
much" that it is seen as a different PC.
That's the part I'd want to drill down into.
The OP wrote, and I quote:
"Windows said it needs to reactivate windows due to a hardware change,
although I never changed anything."
Possible "changes" include BIOS and driver updates that can break
previous assumptions as to what the hardware is "called".
Such "changes" are not real hardware changes of course, and that the
DoS payload can't tell the difference, is a serious limitation
Courts are too fallible for many nations to allow the irreversible
death penalty, and a system that can't tell the difference between
software and hardware changes is too fallible for a DoS payload, IMO.
OTOH, maybe this thing is so buggy (or exploitable) that the payload
hatched when there really were no changes at all. If the system
cannot safeguard itself against malware that can trigger a false
alarm, then it is too insecure for a DoS payload, IMO.
------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope