Hello I used The 67thQT and it did not save to the desktop nor any where else on my laptop. After The 67thQT is finished running do I just exit the program and it automatically saves to the desktop? Thank you.
The new MRP will fix that, its because it picked up on the word 'System' and thought it was systemmax. The QT67 gets it right because of the new DMI recheck routines which is now in the next MRP. [THMOK] Systemax [N/A] manufacturer was detected for automated theme/branding. is the clue! Technically it should of been set to Windows Default theme as the N/A bit should of switched it over, but because it had seen the 'System Product Name' it picked up on the System word. As mentioned before it all because of the theme names which have similar wording, the QT routine works 99.8% of the time, but during oobe stage some things react different hence why the MRP code had to be re-tweaked.
The QT will be updated shortly to v67.1 - there was a small glitch with VMWare and VirtualBox detection, was a oversight on my part when i updated the DMI routine i forgot to move the lines that detected the VMware/VBox DMI information and it would either pick 'Windows Default' or Intel (Vmware's SLIC name). Now it will say for VMware a DMI conflict and correct it to VMware. With VirtualBox it may DMI conflict depending on if 'Oracle VirtualBox' is present or just Oracle, it should then be corrected it to VBox theme. No other brands or HyperV etc was affected. Thanks to @Enthousiast for inadvertently detecting the glitch.
Query Tool v67.1 has been uploaded, 2nd post download link, password and hashes updated. Summary + Fixed a glitch with VMware and VirtualBox DMI detection thanks @Enthousiast for inadvertently finding it! No other brands or HyperV was affected. No other code changes done.
As mentioned before you need to set your AV's exclusion rule for %TEMP%\MRP-QT or whatever %TEMP% corresponds to. By default i think is C:\Users\YourUsername\AppData\Local\Temp , it can be checked by opening a P/Shell or Command Prompt and typing SET temp and pressing return which will show the expanded 'temp' variable. In the above example the rule for exclusion would be: C:\Users\YourUsername\AppData\Local\Temp\MRP-QT Likewise for Windows Defender or other AV's.
On my tests Defender doesn't even block the QT, it opens a report that the IT-Manager should start a scan and links to a website which explains how to enable direct actions setting (paraphrasing). Lately it doesn't even do that anymore (no exclusions made ever, for the QT)
I was thinking to update the other brand logos and resources as well, what do you think about that ???