QT 87.0 is nearing completion, got to test 20 with all the little tweaks needed to get things looking right. Taken longer than expected and it may still fail to detect some later Insider builds as m$ seem to be changing the way they are named internally or to the point where the naming is stored!
yeah that is something i have tried to rectify but it always seems to defeat what i try to compensate It is a glitch, wmic can give some odd results at times. More so with graphics memory, due to some using system ram and if they have some physical on-board ram too. *Edit* May now sorted that with a bit of 'FOR /F' loop magic to remove the first character if it is a minus sign.
Query Tool v87.0 has been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT87 Summary + Added Windows 10 {RS5+} Clipboard History status detection. + Updated Insider/Preview build detection and information about Rings etc. Due to changes in the newer Preview Builds the QT may not always detect it being an Insider OS, hopefully this will be sorted once m$ have settled on a standard IP build registry entry. + Updated MS Office detection routine, should be better at finding 2019 and C2R types. + Added Trim detection for SSD's (Win 7+), {Experimental} -- can state on W10 if enabled/disabled for NTFS and/or ReFS. ReFS can be used within certain W10 for drives already formatted or Editions which allow ReFS formatting etc, this is why it is shown. You can see for yourself on W10 open a command prompt window and type (or copy/paste): fsutil behavior query disabledeletenotify Then see the results. Parsing the results to cover the new wording and the old was a bit tricky and is why it is 'experimental' as cannot be 100% sure due to changes in the W10 Builds. + Fixed (hopefully) the graphics memory data sometimes showing a negative amount.
wmic.exe PATH Win32_VideoController GET AdapterRAM is what is used to obtain the data, it is not easy to parse if more than one adaptor as it all on one 'result' and a bit of work is needed to get the results in the right order etc. As always there are limitations with batch (even powershell which i not use) to get all the results sorted.