Hmm seems the License channel screwed up Unless it was a key entered? Odd as all the tests ive done it got it right
That machine is licensed via "Windows for refurbished devices", it is indeed a COA OEM:NSLP key. All OK. Code: //--- The Ultimate PID Checker v1.2.0.606 Блин by janek2012 --- Product Key : *****-*****-*****-*****-R9CHG Profile : E:\Keychecker\Ultimate\Win_X_21H2#IB\pkeyconfig.xrm-ms Validity : Valid Product ID : 00326-00740-81565-AAOEM Advanced ID : XXXXX-03260-074-081565-02-1033-7601.0000-3212021 Activation ID : 30d469c6-a78f-4476-b5c8-af78d5b6a5fb Edition Type : Core Description : Win 10 RTM Core OEM:NONSLP Edition ID : [TH]X19-99555 Key Type : OEM:NONSLP EULA : OEM Crypto ID : 3260 Benchmark : 0.312 seconds
Phew, thought something had messed up, i rechecked everything , the qt does 2 checks one via wmic, or vbs, the other via slmgr and then parses the results for key words.
In Windows 10 Enterprise LTSC, DeCompile.exe is falsely detected as Trojan:Win32/Triggre!rfn, causing its execution to be blocked and MRP to fail. Can you make it so that it adds a temporary exclusion in defender?
I have tried to but because defender grabs it before it is run to add the exclusion. Plus during normal oobe install defender should not interfere, only if you attempt to run decompile outside of oobe will any AV nab the file.
If you are running a in-place upgrade or repair and you are using a AV such as defender then it would be needed to manually add C:\Windows\Setup folder to the exclusion zone in the respective AV BEFORE running the windows setup. This covers any files MRP or 'user tweaks' etc uses. Remove the exclusion later - but MRP will attempt to remove them from Defender once it has completed as mentioned below. But if booting from usb/dvd and a clean install then no need to add any exclusions because defender etc would not be running at that stage. Hopefully by then MRP has added the setup/scripts folders to exclusion section. When MRP completes it will auto remove the added defender exclusions.
On a clean installation if mrp not being run it can be for the following reasons: If a valid msdm is present as oobe is skipped unless a ei.cfg or pid.txt file is used. Oobe.cmd has an error within that causes the file to be ignored. A corrupted decompile.exe which will obviously not run. Unsupported os ie below vista. For a clean installation defender will not be running at that early stage unless ms have changed how it works, or is just ignoring oobe for some unknown reason.
Another time mrp may not be run or any oobe stage run scripts such as setupcomplete.cmd is: Win 1x Enterprise 2021 LTSC. Cloud/S mode. This is due to internal hard coding within the kernel. Not sure if there will be a workaround for those os's at a later time. Maybe using a unattended xml way? There may be other conditions that could prevent oobe projects being run which I'm not aware of. MRP 141 is delayed slightly because of last minute checks and tidying of code.
Looks like a updated Query Tool v118 (118.1) will be released soon, as when WMIC not in the OS, (or using the /NW switch), and when the alternative routines are in use , the CPU WinSAT scores may not show correctly, or at all. Also there was a mix up in variables for when VL_Client was in use, or not, when using the alternative routines. Testing it now and will upload the new version tomorrow.
Query Tool v118.1 uploaded, 2nd post's download link, password and hashes updated. Spoiler: QT 118.1 Summary + Fixes a few missed WMIC replacement routines so that CPU WinSAT scores are now shown correctly. + Fixed some CPU information that did not always show, ie L2/L3 cache etc. + Fixed Windows License information when using the alternative routines. + Other small code updates.
There is still a few issues to fix with the qt. So a new qt will address those, it mainly concerns wmic less os's at the moment. Busy today so no time to fix.