Code: Valid SLIC Name : Toshiba Possible Brand Theme : Toshiba {System Manufacturer} SLIC Table Status : SLIC table with valid marker present {v2.1} MSDM Key Description : TOSQCI|Toshiba MSDM Key Detected : 29WJQ (Last 5 digits shown) MSDM Key OS Version/Edition : Win 8.1 Core More MSDM info added in next release of the GUI QT, sadly only for w8.x and above as cannot get the OA3 Key below w8 with current method.
MSDM: Shows the OS/Edition the key is for. Experimental. Only available for windows 8.0 and above as OA3Key is not available below 8.0 OS. Other small code tweaks to results...
Using a method used in the old QT, that i have modified for AutoIT use, hopefully managed to obtain any OS3Key (MSDM product key) from the BIOS on Vista/7 too. Cant test that until a bit later. Cannot obtain if a loader is present or not as i get some 'unhandled console error' so that bit is not available for now...
Beast: Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v0.10.2.4 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 11/12/2022 -- 06:50 {24-hour} Some results may be shortened to fit the output stage, such as RAM information. This is the postable report that does not contain full serial or sensitive information. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 10 Enterprise OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.19045 {UBR:2006} {22H2} Language : Deutsch (Deutschland) Native Language : Deutsch Installed/Available Languages : de-DE Stock Keeping Unit {SKU} : 4 Experience Pack : 120.2212.4180.0 Installation Date : 6/19/2022 at 1:49 AM {UTC} Shipped with Reserved 7GB : Yes Dirty Shutdown Count : 1 Build Branch : vb_release Product ID : 00329-00000-00003-AA075 {Extended: 03612-03290-000-000003-03-1031-19044.0000-1702022} TimeZone {TZUtil} : W. Europe Standard Time Hours offset from GMT : 1 Daylight Saving In Effect : No Daylight Adjust Clock Mode : Enabled/Checked Hypervisor Present : No Virtual Machine Data : This computer does not appear to be a virtual machine Windows Key 1 Installed : 2YT43 (Last 5 digits shown) Windows DpID4 Installed : 2YT43 (Last 5 digits shown) Windows Default Installed : 8HV2C (Last 5 digits shown) Windows Default4 Installed : 8HV2C (Last 5 digits shown) TPM Information : N/A =================================================================================================================== System Drive C: Partition Information =================================================================================================================== Drive Type : SSD BUS Type : Serial ATA (SATA) Total Space : 1862.28 GB Free Space : 1789.28 GB Partition Type : GPT Firmware Boot Type : UEFI Mode {R:2} Secure Boot Status : Disabled [Ref:1] File System : NTFS Model Name : Samsung SSD 860 EVO 2TB =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 67009408 KB (63.91 GB) Available Physical : 60567252 KB (57.76 GB) Total Page Size : 71203712 KB (67.91 GB) Available Page Size : 63618564 KB (60.67 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 4008288 KB (3.82 GB) Memory Type : DDR4 Memory Error Correction : Non-ECC Memory Slots Fitted : 4 DIMM Information {First Four} : DIMM_A1 16384MB @ 3000MHz DIMM_A2 16384MB @ 3000MHz DIMM_B1 16384MB @ 3000MHz DIMM_B2 16384MB @ 3000MHz =================================================================================================================== Graphics Information =================================================================================================================== Adaptor Name : NVIDIA GeForce RTX 2070 Adaptor DACType : Integrated RAMDAC {Addon} Adaptor Driver Information : 30.0.14.7168 {2021/08/05} Adaptor Status : Active Adaptor Name : Microsoft Remote Display Adapter Adaptor DACType : Adaptor Driver Information : 10.0.19041.1865 {2006/06/21} Adaptor Status : Active Virtual Desktop Resolution : 2560 x 1600 Bits Per Pixel : 32 Video Mode Description : 3840 x 2160 x 4294967296 Farben {Ref:1} Some values may not be accurate due to 32 bit API limitations. For accurate VRam use DxDiag or other tool. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : RZ608 Wi-Fi 6E 80MHz Connection Status : Media Disconnected Adaptor 2 Name : Intel(R) Ethernet Controller (3) I225-V Connection Status : Connected =================================================================================================================== Processor 1 Information =================================================================================================================== Name : AMD Ryzen 9 3900X 12-Core Processor Architecture : 64 L2 Cache Size : 6144 L3 Cache Size : 65536 Current Clock Speed : 3801 Physical Cores : 12 Logical Cores : 24 Processor Id : 178BFBFF00870F10 Virtualization Mode : Enabled Manufacturer : AuthenticAMD Description : AMD64 Family 23 Model 113 Stepping 0 =================================================================================================================== DMI/BIOS Information =================================================================================================================== System Manufacturer : ASUS System Product Name : System Product Name BaseBoard Manufacturer : ASUSTeK COMPUTER INC. BaseBoard Product : TUF GAMING X570-PRO WIFI II BaseBoard Version : Rev X.0x BIOS Vendor : American Megatrends Inc. BIOS Release Date : 08/13/2021 BIOS Version : 0305 Primary BIOS : True SMBIOS Present : True SMBIOS Version : 3.3 SLIC/BIOS Data : ALASKA - 1072009 Valid SLIC Name : No Valid SLIC Table Possible Brand Theme : Asus {System Manufacturer} SLIC Table Status : No valid SLIC table MSDM Key Description : No MSDM key Description found MSDM Key Detected : Not Present =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : CY21M04D12-R136.0.BL 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 Security Product Name{s} : COMODO Antivirus Defender Tamper Protection : Both Tamper and Cloud-delivered Protections are enabled Defender Service Status : Auto Windows Firewall Service State : Running {Reg: Auto} Windows Activation Status : VL activation expires 179 Days / 257863 minutes Windows Licence Reason : Valid key was used for the product's licensing channel Windows Product Key Channel : KMS Client {VOLUME_KMSCLIENT} Device has KMS Enabled : Yes KMS Auto Renewal (hook) : No MS Office {MSI/Traditional} : Not Detected C2R MS Office : Not Detected C2R Excluded Apps : N/A C2R Last Update Channel : N/A C2R Office Activation Status : N/A C2R Partial Product Key : N/A Office Reason Information : No reason information to show/No Issues Office MAK/KMS Information : No MAK or KMS activation detected ------------------------------------------------------------------------------------------------------------------- Two active graphics adaptors might even be correct, the QT has been run over Remote Desktop.
The active flag is set when BPP is detected as usually that is only available when the gfx card is in use, when it not the primary then BPP is not available. A simple test i know but wmi(c) not return any other easy way to say which one is primary as such , cannot rely on VideoAdapter1 etc as i found out before so have to get a bit creative
I don't see it as error. The original RTX2070 SUPER is still active (locally, the login screen is shown when a remote user is logged in). And the RDP adaptor is also active with getting the image onto the RDP client. Even the two different resolutions are both correct. 3840x2160 is the original resolution, and 2560x1600 the one I use for RDP. Edit: The machine has been purchased and assembled when the prices were still.. manageable. 64GiB is a compromise, as I frequently work with VMs. Want to upgrade to 128GiB eventually. RTX 2070 SUPER isn't that super, only 8GiB VRAM (SUPER is now what was formerly known as ROG STRIX). My brother owns a ZOTAC RTX 3090 which has 24GiB IIRC.
The virtual desktop and actual desktop resolutions are new to me, but if you alter the resolution even by scaling (as i do on my laptop) the two are different so that why i list them. Might be useful to someone. I was trying to get the Monitor native resolution but not all displays return the info so i left that alone, not really important.
My main pc is a compromise too, at the time i could not afford more ram (reused from previous pc) , the new i5 was expensive but wanted something similar to the i5-6400 i had but more up to date and potentially w11 ok. A lot of things was reused, although the NVMe is new, the NV 1050ti is same but does what i need for the games i play (when i get time ) My 1050ti is a ROG Strix 4GB - was a bargain as at the time retail was over 250 GBP but as i know the shop owner i got it trade/shop price ( was used in a display pc for a month or so) , cost me just over 100 GBP
Have just uploaded the latest GUI QT v0.10.2.6 to the beta test area - as it highly experimental and could crash - my tests seem to be ok but not tested on a MSDM pc yet and that is where it could fall over on. I will test on a tosh laptop with a msdm table later this morning.
Hm, we had that topic before. It's possible to insert an MSDM table into a VirtualBox VM. Checking that out...
I know. Earlier in the topic, we had the "I want to insert a non-MSDM key into the MSDM table" phase, and trained QT to detect that. Just trying to get something for testing, fast.
From a Windows 7 Enterprise E VM (leftover from testing). MSDM key is detected. It's not a valid one, thus the N/A is correct. But, detection works. Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v0.10.2.6 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 11/12/2022 -- 10:56 {24-hour} Some results may be shortened to fit the output stage, such as RAM information. This is the postable report that does not contain full serial or sensitive information. On Hypervisors some results may be missing due to unable to detect. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 7 Enterprise E OS/CPU Architecture : CPU is 32 bit Build : 6.1.7601 {UBR:26174} Language : English (United States) Native Language : English Installed/Available Languages : en-US Stock Keeping Unit {SKU} : 70 Experience Pack : N/A Installation Date : 10/19/2022 at 17:22 PM {UTC} Shipped with Reserved 7GB : N/A Dirty Shutdown Count : N/A Build Branch : N/A Product ID : 00355-259-7448856-85031 {Extended: 00355-00170-259-744885-03-1033-7600.0000-3152021} TimeZone {TZUtil} : W. Europe Standard Time Hours offset from GMT : 1 Daylight Saving In Effect : No Daylight Adjust Clock Mode : Enabled/Checked Hypervisor Present : No Virtual Machine Data : VirtualBox {Open-Source Hypervisor} Windows Key 1 Installed : H9DH4 (Last 5 digits shown) Windows DpID4 Installed : H9DH4 (Last 5 digits shown) Windows Default Installed : TCKVR (Last 5 digits shown) Windows Default4 Installed : TCKVR (Last 5 digits shown) TPM Information : N/A =================================================================================================================== System Drive C: Partition Information =================================================================================================================== Drive Type : Non SSD BUS Type : Serial ATA (SATA) Total Space : 49.9 GB Free Space : 38.58 GB Partition Type : MBR Firmware Boot Type : Legacy/MBR Mode {R:1} Secure Boot Status : N/A File System : NTFS Model Name : VBOX HARDDISK ATA Device =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 3145272 KB (3 GB) Available Physical : 2708088 KB (2.58 GB) Total Page Size : 6288880 KB (6 GB) Available Page Size : 5858756 KB (5.59 GB) Total Virtual Size : 2097024 KB (2 GB) Available Virtual : 1981372 KB (1.89 GB) Memory Type : N/A Memory Error Correction : Memory Slots Fitted : WMI call not available on this OS DIMM Information {First Four} : N/A =================================================================================================================== Graphics Information =================================================================================================================== Adaptor Name : Standard VGA Graphics Adapter Adaptor DACType : Adaptor Driver Information : 6.1.7600.16385 {2006/06/21} Adaptor Status : Inactive Adaptor Name : Not Detected Adaptor DACType : N/A Adaptor Driver Information : N/A Adaptor Status : Inactive Virtual Desktop Resolution : 1600 x 1200 Bits Per Pixel : N/A Video Mode Description : {Ref:1} Some values may not be accurate due to 32 bit API limitations. For accurate VRam use DxDiag or other tool. On Hypervisors some results may be missing due to unable to detect. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : Intel(R) PRO/1000 MT Desktop Adapter Connection Status : Connected =================================================================================================================== Processor 1 Information =================================================================================================================== Name : AMD FX-8370 Eight-Core Processor Architecture : 32 L2 Cache Size : L3 Cache Size : Current Clock Speed : 4080 Physical Cores : 1 Logical Cores : 1 Processor Id : Virtualization Mode : Query not present on this OS Manufacturer : AuthenticAMD Description : x86 Family 21 Model 2 Stepping 0 =================================================================================================================== DMI/BIOS Information =================================================================================================================== System Manufacturer : innotek GmbH System Product Name : VirtualBox BaseBoard Manufacturer : N/A BaseBoard Product : N/A BaseBoard Version : N/A BIOS Vendor : N/A BIOS Release Date : 12/01/2006 BIOS Version : VirtualBox Primary BIOS : True SMBIOS Present : True SMBIOS Version : 2.5 SLIC/BIOS Data : ALASKA - 1 Valid SLIC Name : No Valid SLIC Table Possible Brand Theme : VBox {System Manufacturer} SLIC Table Status : Unable to check on this OS MSDM Key Description : MSDM Key Detected : Y7V26 (Last 5 digits shown) MSDM Key OS Version/Edition : N/A =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : CY22M09D30-R147.BL Wallpaper Style : Fill image to display resolution Current Theme Used : basic.theme Installed Dot Net Frameworks : 2.0 3.0 3.5 4.8 4.0 Installed Powershell Versions : 1.0, 2.0 Security Product Name{s} : No Security Installed Defender Tamper Protection : Disabled Defender Service Status : Auto Windows Firewall Service State : Running {Reg: Auto} Windows Activation Status : Initial grace expires Days / 9660 minutes Windows Licence Reason : Running within the valid grace allowance Windows Product Key Channel : KMS Client {VOLUME_KMSCLIENT} Device has KMS Enabled : Yes KMS Auto Renewal (hook) : No MS Office {MSI/Traditional} : Not Detected C2R MS Office : Not Detected C2R Excluded Apps : N/A C2R Last Update Channel : N/A C2R Office Activation Status : N/A C2R Partial Product Key : N/A Office Reason Information : No reason information to show/No Issues Office MAK/KMS Information : No MAK or KMS activation detected ------------------------------------------------------------------------------------------------------------------- About the "hang" at 10%. At least for me, it is never truly hanging. It just has a long delay sometimes, for some arcane reason...
Sorry for late reply lost internet at home (they said when i rang it was planned maintenance -- maybe for them but i wasn't informed ) So now at a friends where i can test the MSDM in a tos**ta laptop I put that msg about if it hangs as sometimes it can sit there on the OS 10% part for ages, although usually that when i am just running the script and not when compiled, odd time it has sat there for over a minute and no idea why or what it is sticking on, probably a WMI call who knows i never see any errors in the console window of the editor... Usually if it sticks a end task of the QT and a re-run then all is ok again.
I remember all the MSDM/SLIC insertion phase that is going back a while S1ave77 did all the MSDM binary files etc as i always buggered something up and trashed the VM's