In the qt it reads the Value from the registry, if defender has been removed by editing etc the registry is not always updated too, so there is always some bits left. If defender is intact and you just disable the real-time option in its dashboard it can confuse the qt , I still need to address that. The to do list has grown
This morning my laptop went into the repair boot loop, took me a couple of hours to get it out of the looping. It turned out to be panda av had somehow decided to uninstall itself when I turned off the laptop last night. After fixing the 'missing' file that the boot manager was complaining about in the event log/dump. I decided to look at programs and features to make sure panda was gone which it was. Then I used bulk crap uninstaller and I saw copilot had installed yesterday, yet I never saw it on the start menu or in apps in settings not even on the taskbar?? I didn't think it was on win10 and certainly not without any ai chip as this laptop is from 2011 era!! I not see it download or install but the date was last night, I not use wusince February and wu is set to notify anyway. Defender is gone and disabled as that was annoying me.
I only saw copilot when I used bulk crap uninstaller as I wanted to make sure the registry was clear of any panda av bits left over. It was not showing anywhere else which confused me. Bcu removed copilot. How it sneaked on I don't know, makes you wonder what other s**te ms can sneak in through the backdoor!!
Have uploaded the product channel ID compiled autoit file (zipped) for beta testers if they wish to help test if i have got the right offset (as there could be 2 areas in the binary block in the registry used to filter the value). No idea if it will work on any OS below windows 10 as i not got access to that test laptop until the weekend after a hospital appointment. I have guessed the offset as it seems it can be in more than one place, there is a lot of 00 (zero/null) areas in the binary block, i just used the 2nd area i saw the pattern i was looking for, as it seemed to be in the same place on w10 and 11. I have added in a check if the OS is 32 or 64 bit architecture as that can make a difference too if the binary result is in the registry, this was a issue with powershell but that acted very strange even if you 'forced' pshell to look at 64 bit registry... Anyway using the simplified method in AutoIT is so much faster than PShell, and no WMI in sight either!
Have uploaded GUI QT v1.08f for beta testers This has the new binary code routine in for the key channel ID, it will fall back to WMI method if something not right (hopefully), the log and GUI will show {Binary : PKC} or {WMI : PKC} depending on which routine is used. Sorted the 'HWID/Digital Store Licence' reference as i forgot about that... Technically it should work on win7 based OS's too, not too sure about win8.0 as i think i had other plans for that OS and not got round to adding that part in.. It is experimental as i not been able to check on anything other than 'Retail', such as when using KMS/MAK/OEM_DM etc as unsure what the values are - i just guessed they use same format as WMIc does... Can adjust as needed, after all it is a beta.
Yes as most are Retail, but those with LTSB/C or Enterprise etc that is using KMS, MAK, plus those with OEM_DM being used or the SLP ones i have guessed they are values that are the same used with WMIc productkeychannel ID's... Such as a Server that can be KMS or other key based and not Retail as i doubt if m$ made that Retail
Windows 7, something isn't right yet (N/A): However, the test code shows it correctly. Code: E:\Download\Test-Channel-ID>Channel-ID.exe OEM:SLP
Yeah I think I not cleared a variable with n/a in which on a test further on if the variable is non blank it not get the new info added to show. At least the code is ok for the binary to hex to string and working. On wmi/c it would return oem_slp so at least now I can fix that easy. Thanks for testing that really helps.
No problem. A few small tests can always be done, although coincidentally, a whole boatload of updates has just dropped, keeping me busy for a while.
Have uploaded the GUI QT v1.08g for beta testers Updated the Product Key Channel to be more 'verbal', if the returned value not match my list then it will either just show the value as it is or try to use the WMI method as backups. Have now covered, (hopefully in my list), WS12, WS16, WS19 and WS22 plus VT:IA (Server VM activations), N/A should no longer show - if i got everything wrong then it will be a blank value! Result from my laptop (W10 HWID) Code: Windows Activation Status : Activated Windows Licence Reason : Digital Store Licence Windows Product Key Channel : Retail with HWID {Binary:PKC} Device has KMS Enabled : No KMS Auto Renewal (hook) : No {Binary PKC} is using the updated routine, if {WMI PKC} then it will be the original WMIc method.
If this QT gets the seal of approval i will change it to v1.09 and upload for general use and update post #2 with the new download link either later today or tomorrow morning.
Spoiler: [Postable]-GUI_QTv1.08g_[18.30]_[MP200] Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v1.08g ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 03/12/2025 -- 18:30 {24-hour} Some results may be shortened to fit the output stage, such as RAM information or storage drive names. This is the postable report that does not contain full serial or sensitive information. GUI Font Used : Lucida Console | Size: 10 | DPI Scale: 1 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 10 IoT Entreprise LTSC Edition Name {Registry} : IoTEnterpriseS Composition Name {Registry} : EnterpriseS OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.19044 {UBR:5487} {21H2} Initial Full Build Information : 19041.1.amd64fre.vb_release.191206-1406 Build Branch : vb_release {Vibranium} Setup/Install Locale : Français (France) GeoID Nation ISO Location : France Current Keyboard Language : French - France {1036} Current Keyboard Name : Étendu (101 ou 102 touches) Number of Function Keys : 12 Keyboard Description : Clavier standard PS/2 Installed/Available Languages : fr-FR Stock Keeping Unit {SKU} : 191 Experience Pack : 1000.19061.1000.0 Installation Date/Time {UTC} : 11/18/2023 at 16:25 PM Last Boot Up Date/Time {UTC} : 03/12/2025 at 18:31 PM Product ID : 00484-40000-00001-AA498 {Extended: 03612-04844-000-000001-03-1036-19044.0000-2722024} Time Zone Data : Romance Standard Time Hours offset from GMT : 1 Daylight Saving In Effect : No Daylight Adjust Clock Mode : Enabled/Checked Upgrade or Clean Installation : Upgraded on 11/18/2023 {UTC} Previous OS Upgraded From : Windows 10 IoT Enterprise LTSC 2021 Touch Device : No Touch device detected StorageSense Policy : Disabled {0x0} Number of Licensed Users : 1 Data Execution Prevention : OptIn/Default {Ref: 2} DEP Available : Yes DEP 32Bit Applications : Yes DEP Drivers : Yes DEP Support Policy : Enabled for OS Kernel, essential binaries and all Windows based Services. Clipboard History Service : Manual {Value:3} Clipboard History : Disabled {0} Allow Cross Device History : Enabled {Default} Allow Clipboard History : Enabled {Default} Current Power Policy Used : Home/Office Desk Power Plans Available : Balanced Only {Others may be 'hidden'} Current Active Power Plan : Balanced Long File Paths Enabled : No {0x0} NTFS is not set to allow file paths greater than 260 characters Part of a Domain : No Domain/Device Role : Standalone Workstation {0} Portable OS {Win to Go} : No Feature Update Status : Not paused Quality Update Status : Not paused WSH Availability Status : Windows Scripting Host is not restricted. {All Users} WSH 'DisplayLogo' Value : Enabled {1} [All Users] HVCI Protection Status : N/A Download Over Metered Internet : Not Configured {default} Exclude Drivers from MS/WU : Yes Pointing Device {Mouse} : Souris HID WMIC.EXE information : WMIC.exe appears to be operative in this build. Hypervisor Present/Installed : No Virtual Machine Data : This computer does not appear to be a virtual machine Shipped with Reserved 7GB : No Dirty Shutdown Count : 11 VL/KMS Capable/Permitted : No KMS Activation In Use : No Win7 ESU {POS7} Patch {exp} : Not required on this OS Windows Key 1 Installed : PDQGT (Last 5 digits shown) Windows DpID4 Installed : PDQGT (Last 5 digits shown) Windows Default Installed : 6F7W2 (Last 5 digits shown) Windows Default4 Installed : 6F7W2 (Last 5 digits shown) TPM Information : Active : Yes, Enabled : Yes, Owned : Yes, Version : 2.0, Vendor : Intel =============== Windows 11 Checks =============== Checked for W11 Target Upgrade : Yes Target Build Number : N/A Device is OEM Specific : N/A DirectX 12 Detected : N/A Device is Genuine : N/A Touch Capable Hardware : N/A Upgrade Experience {1} : N/A Upgrade Experience {2} : N/A Upgrade Fail Reason{s} : N/A Bypass TPM Check : N/A Bypass Secure Boot Check : N/A Bypass RAM Check : N/A Allow W11 WU Upgrade : N/A CompatTelRunner.exe {Appraiser} : Process is not running. {File is present in C:\Windows\System32} If 'N/A' is shown then the data may not of been fully compiled by the OS or via WU yet. When Fail Reason's are listed then they are not compatible and will be blocked for the upgrade. If any Upgrade Experience's are listed as 'Orange' then they will require attention to pass the OS checks. If CompatTelRunner.exe is prevented from running then the W11 checks will not be performed. =================================================================================================================== Booted System Drive Partition Information =================================================================================================================== Drive Type : SSD BUS Type : NVMe Total Space : 237.56 GB Free Space : 185.87 GB Partition Type : GPT Firmware Boot Type : UEFI Mode {R:2} Secure Boot Status : Enabled [Ref:1] File System : NTFS System Drive Letter : C: Bitlocker Protection Status : Volume C: is not a BitLocker volume {2}. Interface Information : What mode an interface is in IDE Controller Mode : Advanced Host Controller Interface {AHCI} SCSI Controller Mode : Microsoft Storage Spaces Disk and Partition Information : Driveletter | Disk #, Partition # | Model Name {50 Chars max} | Size 'GB' \\.\PHYSICALDRIVE1 C: | Disk #1, Partition #1 | FORESEE XP1000F512G | 237.56 GB \\.\PHYSICALDRIVE1 E: | Disk #1, Partition #3 | FORESEE XP1000F512G | 238.68 GB \\.\PHYSICALDRIVE0 D: | Disk #0, Partition #0 | Samsung SSD 870 QVO 4TB | 3654.46 GB \\.\PHYSICALDRIVE0 H: | Disk #0, Partition #1 | Samsung SSD 870 QVO 4TB | 71.56 GB Drive letters/Partitions are shown as they are defined via the connected ports in the BIOS. Partitions without Drive letters assigned are not shown. =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 16512272 KB (15.75 GB) Available Physical : 13270576 KB (12.66 GB) Total Page Size : 17560848 KB (16.75 GB) Available Page Size : 14364900 KB (13.7 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 4009808 KB (3.82 GB) Memory Type : DDR4 {26} Memory Error Correction : Non-ECC Memory Slots Fitted : 4 Memory Slots Used : 1 Memory Slots Free : 3 Motherboard's Max Memory : 134217728 KB (128 GB} DIMM Information {First Eight} : Controller1-ChannelA-DIMM0 16384MB @ 3200MHz =================================================================================================================== Graphics Information =================================================================================================================== Adaptor Name : Intel(R) UHD Graphics Adaptor DACType : Internal {iGPU} Adaptor Driver Information : 31.0.101.4889 {2023/10/29} Adaptor Video Ram {See Notes} : 1024 MB {Routine:1R1} Adaptor Status : Active Adaptor Name : Not Detected Adaptor DACType : N/A Adaptor Driver Information : N/A Adaptor Video Ram {See Notes} : N/A Adaptor Status : Inactive Virtual Desktop Resolution : 1920 x 1080 Bits Per Pixel : 32 Video Mode Description : 1920 x 1080 x 4294967296 couleurs {Ref:1} WinSAT Scores/Status : {Via WMIC} Processor : 9,2 Memory : 9,2 Desktop Graphics : 6,5 D3D Gaming : 6,5 {Set same as Graphics as usually 9.9} Primary Hard Drive : 8,35 Base Score Rating : 6,5 The 'Experience Index' scores was valid at time of the query. Some values may not be accurate due to 32 bit API limitations. VRam does not include any 'Shared' or 'Dynamically' allocated memory. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 2 Name : Intel(R) Ethernet Connection (16) I219-V Connection Status : Connected MAC Address : 54:EF:92:xx:xx:2C Adaptor 3 Name : TAP-Windows Adapter V9 Connection Status : Media Disconnected MAC Address : 00:FF:26:xx:xx:80 Adaptor 4 Name : Intel(R) Wi-Fi 6 AX201 160MHz Connection Status : Media Disconnected MAC Address : A4:F9:33:xx:xx:D6 Adaptor 5 Name : Bluetooth Device (Personal Area Network) Connection Status : Media Disconnected MAC Address : A4:F9:33:xx:xx:DA =================================================================================================================== Processor 1 Information =================================================================================================================== Name : 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz Architecture {Bits} : 64 L2 Cache Size {MB} : 7680 L3 Cache Size {MB} : 12288 Current / Max Speed {MHz} : 2688 / 2688 {Not Turbo Speed} Physical Cores : 6 Logical Cores : 12 Processor Id : 0xBFEBFBFF000806D1 Virtualization Mode : Enabled Manufacturer : GenuineIntel [Intel] Description : Intel64 Family 6 Model 141 Stepping 1 Motherboard Connection : U3E1 OS Loaded Microcode Revision : 0x000000003C000000 Bios Microcode Revision : 0x000000003C000000 Processor Family : 205 Sockets/CPU's Present : 1 Feature Set : 0x000000003D1B3FFF FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MONITOR DS-CPL VMX EST TM2 SSSE3 SDBG FMA CX16 XTPR PDCM PCID SSE4.1 SSE4.2 X2APIC MOVBE POPCNT TSC-DEADLINE AES XSAVE OSXSAVE AVX F16C RDRND Motherboard Connection is based on a OS internal database, MS may not have updated it. Microcode registry values are converted from binary to hexadecimal, not reliable for all devices. =================================================================================================================== DMI/BIOS Information =================================================================================================================== System Manufacturer : Shenzhen DOKE electronic co., LTD System Product Name : MP200 BaseBoard Manufacturer : Default string BaseBoard Product : Default string BaseBoard Version : Default string PC System Type : Mobile {2} UEFI Certifications : None detected UEFI DBX Revocations {Exp} : None detected MS S/Boot CVE-2020-10713 : Boothole fix does not appear to be available in UEFI BIOS Vendor : American Megatrends International, LLC. BIOS Release Date : 05/11/2023 BIOS Version : 5.19 Primary BIOS : Yes SMBIOS Present : Yes SMBIOS Version : 3.3 SLIC/BIOS Data : ALASKA - 1072009 Valid SLIC Name : No Valid SLIC Table {See notes below} Possible Brand Theme : Shenzhen {System Manufacturer} SLIC Table Status : No valid SLIC table {See notes below} Emulated SLIC : Not required/used for this OS MSDM Key Description : No MSDM key Description found MSDM Key Detected : Not Present MSDM Key OS Version/Edition : N/A Notes : When in UEFI mode the SLIC information may not be shown fully as it may be partially 'hidden' by the OEM/BIOS. =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : CY23M07D17-R153.TR10 Wallpaper Style : Fill image to display resolution Current Theme Used : Custom.theme Installed Dot Net Frameworks : 2.0 3.0 3.5 4.8 4.0 Installed Powershell Versions : 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 Windows Activation Status : Activated Windows Licence Reason : No critical issues found Windows Product Key Channel : Volume: {Binary:PKC} Device has KMS Enabled : Yes KMS Auto Renewal (hook) : No MS Office {MSI/Traditional} : Not Checked as a C2R version detected C2R MS Office : Office 21, RETAIL(MAK) channel {x64} C2R Excluded Apps : None C2R Last Update Channel : Production 2021 LTSC C2R Office Activation Status : Grace ends in 0 Days / 0 minutes C2R Partial Product Key : MTGXF Office Reason Information : C004F009 Office MAK/KMS Information : No MAK or KMS activation detected =================================================================================================================== Security Information =================================================================================================================== Defender Tamper Protection : Both Tamper and Cloud-delivered Protections are disabled Defender TProtection Exclusions : Disabled Defender Service Status : Disabled Defender Code Integrity Mode : N/A Defender Credential Guard : Disabled Windows Firewall Service State : Running {Reg: Auto} Security Product Details : {If detected} Windows Defender - Disabled and updated. ESET Security - Enabled and updated. ------------------------------------------------------------------------------------------------------------------- End of Report -------------------------------------------------------------------------------------------------------------------
Why strange? From my laptop, W10 activated by KMS: Code: Windows Activation Status : Activated Windows Licence Reason : No critical issues found Windows Product Key Channel : Volume: {Binary:PKC} Device has KMS Enabled : Yes KMS Auto Renewal (hook) : No The only thing strange is that it does not mention KMS, is that what you mean? Should it be Volume:KMS?