[UPDATE: Removed Vista info: instead of troubleshooting Vista, upgrade it.]
Here are some troubleshooting steps — for my future reference as much as anyone else’s — for for gathering information for diagnosing and resolving Windows KMS client activation issues.
Quick Fix: Try this first!
|Windows 7 Enterprise Volume:||33PXH-7Y6KF-2VJC9-XBBR8-HVTHH|
|Windows 8 Enterprise Volume:||32JNW-9KQ84-P47T8-D8GGY-CWCK7|
|Windows 8.1 Enterprise Volume:||MHF9N-XY6XB-WVXMC-BTDCT-MKKG7|
|Windows 10 Enterprise Volume:||NPPR9-FWDCX-D2C8J-H872K-2YT43|
Enter the code above and attempt to reactivate. If it works, you should be all set. If it doesn’t, the following steps will help identify the issue.
Gathering data is essential to fixing problems. If you ask me (or other IT staff) for help with Windows activation, the first thing I will ask from you is the output of the commands below.
I recommend opening a text editor and copying all the commands and output into a file, which you can send to us if you need additional help resolving the activation issue.
NOTE: All these steps require running commands from a console window (cmd.exe), which you may need to run As Administrator. These commands work in Windows 7, 8 and 8.1.
1. Run ipconfig /all to capture current IP configuration information.
This could tell us whether the system is in a netreg-ed subnet and needs to register at http://netreg.uvm.edu, or if there are other basic network configuration problems. We really just need the Ethernet adapter, assuming that’s what is being used to connect the system to the network. We don’t need all the additional tunneling adapters, etc. If someone is using a wireless adapter, possibly with the VPN client, then info about those adapters also should be captured.