The log reports do help in fine tuning the project and QT - if i notice something cosmetic/not in right place, i make a note and adjust the code base to fix it for next version. Have sorted MRP with the line about the 'Reason: xxxxxx' line to show 'No valid SLIC table' instead of 'No SLP key' like on the Samsung report, was a simple case of moving the check line up a few reason check bits. Also have updated the QT a bit too as well, so that be soon released, it will now show the MRP version used when the OS was installed - (if the project was used) - example :- Code: =======================================================[ Summary ]======================================================= OEM Theme/Branding - Msi [id: #04] OEM Activation {V/7} - Un-Listed Valid OEM Consumer OS - Un-Listed Valid OEM Server OS - Un-Listed MSDM Check Method Used - N/A Grace Time Remaining - N/A Detected .Net Versions - v1.1.4322 / v2.0.50727 / v3.5 / v4.0.30319 / v4.7.02046 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 License Status Reason - 0x4004F401: This computer has a valid Digital/Store License. MRP Version Used - 180208-R83.1 ==============================================[ End of Query Tool Report ]===============================================
Query Tool v61.0 has been uploaded and 2nd post's download link, password and hashes updated. Spoiler: QT 61.0 Summary Updated Reason Codes with some new text information to cover certain KMS situations. Added 'MRP Version Used' information this will show N/A if MRP was not used when the OS was installed and the data for the version used if it was. Changed wording on the Meltdown/Spectre lines slightly to mention 'some variants' of Spectre. Which is more accurate as there seems to be a few new ones appearing! Small tidy up of the code base.
Working on the next MRP Fixed a small glitch with Store when set to 'StoreOnly', for some strange reason i had an extra quote " which caused the entry to set to default 'Anywhere'. At least the error check worked!
With Gen2 installs you sometimes get the 'Possible Tampering' line, it depends on what they have done.
Working on two new options for Windows 10 Kernels... Set Diagnostic & Feedback to Basic and Never send data. Can be changed later if desired. Not sure if anyone wants to. Set Download from Other PCs on the Network to OFF. Also can be changed later if required. Managed to work out how they are set without triggering the Some settings are managed blah blah line. Although sometimes it can trigger that line, it depends on how the OS feel i think.
They are a few of the things i always set manually after a install, if i tried to use any tweaks before to set them, it always seemed to work until the next update session and it reset to FULL and was greyed out so was a bit annoyed. Now it stays set as Basic/Never send - unless I want to change them - which is never.