Query Tool v95.0 has been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT-95 Summary + Fixed a strange bug with Enterprise/Education etc Editions that are KMS capable which may show the KMS data by mistake when no valid key, (or the default OS key), was used. + Reduced System Tray/Taskbar flickering by 98% during running of the Query Tool. + Fixed rare 'hang' in certain scenarios. + Extra Meltdown/Spectre data, depends on the OS's registry status, if available then you may see the CVE/Retpoline etc data. Most is done via Windows Updates and may not show anything on this line. + Code tidy up and some new rewording on results.
yes, ie: OS Protection Status {REG} : CVE-2017-5715 {Spectre v2}, CVE-2017-5754 {Meltdown}. As i set the registry ages ago when the whole Meltdown/Spectre fiasco started. So i now show anything for that part. It will only show if the user has set the 'FeatureSettingsOverride' and 'FeatureSettingsOverrideMask' parts in the registry, even for Retpoline. Windows Updates now contain the microcodes etc and not use the registry as such.
Have updated my post above with some new information. Hopefully this will make things a bit clearer on some aspects of the QT's results.
I will show the first three numbers of the MAC and the very last (6th) number. It's just to mask the whole MAC address to prevent any possible 'spoofing' etc, as it will take a lot of effort to work out the other numbers shown as xx - unless someone is very determined and have a lot of spare time. As for MAK key section, i will look into it more, but for now will leave it as i have re-written until i get more time to work out a plan of action later.
There is no rhyme or reason for the last three numbers of the MAC, they simply are issued to devices serially. I have devices (Fritz!Box etc.) that use multiple successive MACs at once. Showing the first three is fine with me; I'm not interested in spoofing, however, knowing the manufacturer of the NIC hardware is useful information. As for MAK (MAC, MAK, ha!), no need to rush. Just wanted to point out that the stored pkey in Registry is an unreliable source of information. One can use WMIC for getting the channel used. Code: WMIC PATH SoftwareLicensingProduct WHERE (Name LIKE 'Windows%%' AND PartialProductKey is not NULL) GET Description /VALUE
The channel ID is present in the QT #14 License Status : Licensed [Retail/HWID] {0x4004F401} That uses the WMIC method and then the QT parses other parts for KMS/HWID/Key etc from that. We know WMIC is not 100% reliable and some of the results can be a bit ambiguous at best!
@coleoptere2007 , you posted the text from the display version - luckily you edited the MSDM key. On your desktop should of been a saved version with all keys and other certain data masked or not shown which is safe to post as it is. Also a QT-MSDM txt file as your computer has the bios information - never post that file as it for your, (the user's), reference only. It's odd that it has a MSDM with no name, but saying that i have a ASUS desktop board that has a W10 Core MSDM which activates but the name is ALASKA The name part is not important what matters is if it activates.