[Unattended - specialize] auto activation setting not working

TT9tWhD$q

Member
  • host W10 Pro x_64 1909 b18363.657
  • target same as host
  • NTL 1.9.0.7304 Home portable
Having set auto activation - > true and a product key set in unattended -> user settings -> product key -> product key (setup) the OS is being auto activated however (wan connectivity permitted). That causes some grievance when testing a deployment scenario since the product key has to be revoked each time.,
 
Thought that perhaps settings -> windows -> automatic activation set to disabled would supersede but even with that setting in place, and the aforementioned, the OS is still getting auto activated. This is with the key being set in unattended -> user settings -> product key -> product key (setup).
 
Last edited:
Weird, even with no product key present in the unattended section and all auto activation been disabled the target still activated.

Which might be contributed to the target (testing) being physically on the same machine (same hard drive, different partition) and thus presenting a dual boot scenario. Guess will have to see whether it works out on a clean target.
 
With an install on a clean (non-dual boot) target the OS got automatically activated (meantime NTL updated to version 1.9.0.7330) despite three auto activation settings to the contrary. But then the target machine been previously activated (and deactivated) and MS may just keep track of the machine's hardware footprint/ID and activates nonetheless/regardless...
 
Back
Top