Is there a validation-state checker for Win-7? (like xpinfo.exe for XP)

[Nomen]

Win-XP created a hash at install time based on about a dozen different hardware serial numbers or codes, and over time some of those hardware components could change and not trigger an on-line re-validation. Some of these hardware items were CPU type, amount of installed RAM, type of video card, CD-drive model, NIC mac address, hard drive type/model, volume serial number, etc. Each item got 1 "vote" (the mac address got 3 all by itself). If the total votes dropped below 5, XP would invalidate itself and force you to perform on-line re-validation. There was a program called "xpinfo.exe" that would display all the hardware items and show which of them were giving a "yes" vote.

So that's how I understand the validation scheme for XP.

How does it work with Windows 7? Is there a similar hash generated based on hardware components? Is there a program like "xpinfo" that will tell you  the current state of which components agree with the original Windows install state?
 

[jaclaz]

The XP "votes" mechanism was detailed here (just for the record):

http://aumha.org/win5/a/wpa.htm
 

and the XPINFO (and related papers) are here:
http://www.licenturion.com/xp/

The Windows 7 mechanism (not as detailed as in the above):

http://searchitchannel.techtarget.com/feature/How-Windows-7-hardware-upgrades-affect-licensing

 I don't know if anyone already tried doing something like xpinfo for 7. 

jaclaz

 

 

[Tripredacus]

Windows 7 does not use the votes like XP. It does have a file integrity checklist that it uses instead. Too many or wrong files not matching expected checksums will trigger notification mode.

Fortunately, unlike XP, Windows 7 will not lock you out of the OS if activation breaks. Some thing just don't work like Personalization.

There are 2 main methods for checking out details of Windows 7 activation. From elevated cmd, you can run slmgr.vbs -dlv which will show some information in a pop-up window. This command also works up to current versions of Windows 10. For Vista and 7, there is a tool from MS called MGADiag that you can get more detailed information, including a list of files that do not match the checksums. This program is not meant to be used on Windows 8 and above (the results it generated on those OSes are not helpful for troubleshooting an activation issue).

[jaclaz]

1 hour ago, Tripredacus said:

Windows 7 does not use the votes like XP. It does have a file integrity checklist that it uses instead. Too many or wrong files not matching expected checksums will trigger notification mode.

So, the given article is just rubbish?

http://searchitchannel.techtarget.com/feature/How-Windows-7-hardware-upgrades-affect-licensing

Quote

What triggers the need to reactivate Windows? As intended, each hardware component gets a relative weight, and from that WGA determines whether your copy of Windows 7 needs reactivation. The weight and the number of changes is apparently a guarded secret. If you upgrade too much at once, WAT decides that your PC is new, and things can get messy.

The actual algorithm that Microsoft uses is not disclosed, but we do know the weighting of components is as follows, from highest to lowest: ...

jaclaz
 

[Tripredacus]

Ok well there are some caveats. It may depend on what edition you are using. For example, Retail (which allows for transfer to new hardware) may be more forgiving than System Builder edition which doesn't. Also I do not consider a motherboard to be a minor upgrade. A person should expect to have to reactivate Windows if you change the motherboard.

For my own personal experience, I've only had to reactivate a Windows 7 system after changing a motherboard. Not for anything else like video cards, disk drives or network cards.

Fortunately, for Windows 7, it is fairly easy to reactivate. Ensuring internet access is present, most of the time you can just run slmgr.vbs -ato. And nowadays, the phone activation is better than it once was, where the Activation number will give you an option to text you a link where you can go to a website to do the number groups if need be. Way easier than talking to someone on the phone!

[jaclaz]

It's not about caveats, the given article doesn't say anything different from what you just reported.

Whether you call it "votes" or not the essence is the same, if the "integrity" of a file is checked, *something* must be there to compromise it in case of hardware change, and whether the new (not fully known) set of triggers is "morally correct" or "to be expected" (or not), or whether the used method is "forgiving" and "fairly easy to reactivate" doesn't really answer the OP question.

Both slmgr.vbs -dlv and MGADiag do not AFAIK actually give any useful information on what is the situation, more or less we have a "black box" that *sometimes*  will issue a request for reactivation, and most probably each of the zillion versions and licence types have different "black boxes".

jaclaz