Yes, QT 93 will be ready soon, due to illness and other factors, delays in the whole project structure was an unfortunate occurrence. Getting back on track now, not rushing as this is where silly errors creep in. The MSDM key routine has had a makeover/upgrade in both the QT and MRP, should be more resilient than before, also gives a little bit more info in MRP when a MSDM is present.
Within MRP 111 if any MSDM table/key is present then it should show a bit more information now, (as shown in the above log), there are several error messages, (if any are detected), that could be displayed depending on the 'problem', they are 'hopefully' self explanatory -- if they are shown. Also Reason Status is a little bit cryptic at times but if all ok and no problems all is good. Common ones are Mis-Matched Editions, ie a Core MSDM with Pro installed, or Matched editions which is when the MSDM key is inserted for activation of the installed matching edition. New error ones include if the MSDM key is not a valid 8.1/10 key (ie one that is incorrectly generated or a Win7 key!), if the key length is wrong, invalid hash/checksum or something wrong with the internal structure of the table. Plus many others. About 17 in total
QT 93.0 will be released within the next 16hrs - just a few little bits to tidy up and create the changelog etc. MRP 111 is hopefully ready for the end of this week barring any last minute problems.
Understatement of the year. Please, take it easy. Health is important and cannot be fixed with a simple update! Focus on recovering and don't rush.
Most of the code for the project files was done prior to being in hospital, sadly i not had time to write any notes what i did the night before that day, so since being home i have had to compare old/new scripts to see what changes i made. Plus new developments for the MSDM error checking which is one thing that has been needing to be done anyway for a while. All in all not a huge amount has been required to be done, code wise, the change logs may miss some little bits out which i can't 'see' or remember what was done, but as long as the programs work as intended, (which fingers crossed they will), then it's a small price to pay for lack of written documentation. Just sorting out the change log for the QT and then i can archive it and get it uploaded etc shortly.
Query Tool v93.0 has been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT 93 Summary + Added Dirty Shutdown Counter, if the OS was shutdown incorrectly such as: a) Power outages. b) Pressing the on/off button to force switch off. c) Pressing reset. d) Failing Hardware. e) Having the 'force' shutdown tasks/services registry tweaks set to less than 10000 (10 seconds). If anything causes the OS to detect a problem then this counter will show the number of times this happened. On some OS's this counter number may not show or have N/A displayed. + Updated MSDM key detection and data routines, it should now be more resilient to corrupted tables or incorrect key data. Plus give more information regarding the MSDM table data if it is present. + Checks if the OS has the 7GB reserved flag set, for Windows 10 (19h1+) only. NOTE: If a build for 19H1 is after 18362 it may not be shown as an Insider/Preview OS.
Would help if you explained what isn't working The usertweaks.cmd provided is a bare bones script, it is up to the end user to fill in the bits they want to 'tweak' etc. The 'tweaks' added in the barebones are just examples of what can be done.
If the setupcomplete.cmd, shown in your picture, has lines that either delete the scripts folder (RD or RMDIR) or have a shutdown command then they can affect the running of MRP.
well remove the lines SHUTDOWN /R /T 5 and RMDIR /S /Q "%Windir%\Setup\Scripts" because MRP will auto clean that folder up and any contents once you reboot after setup has completed. As for programs not installing, maybe because the shutdown command was the culprit as it was set to 5 seconds before rebooting so none of the silent installs had time to be performed fully. ?
As the setupcomplete.cmd is outside the scope of the project (as it not part of it) then support is limited as so many outside factors.