Had one report that the 'add TI ct menu' not always work on windows 11. It could be a powershell issue as it seems to be on a few installs which have been 'edited' by image tools. Could be a missing dependency of some sort?
Have uploaded gui qt v1.02-rc5 for beta testing. Updated the defender checks, plus added a note at the bottom that mentions if defender has been removed to ignore the information shown. Will try to sort something to detect if defender has been removed and set those results to null. As at present I look at the registry for results.
Spoiler: Query Tool GUI v1.02-RC5 Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v1.02-RC5 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 01/18/2025 -- 23:35 {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. On Hypervisors some results may be missing due to being being undefined within the VM's configuration file{s}. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 11 IoT Enterprise LTSC Edition Name {Registry} : IoTEnterpriseS Composition Name {Registry} : EnterpriseS OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.26100 {UBR:2894} {24H2} Initial Full Build Information : 26100.1.amd64fre.ge_release.240331-1435 Build Branch : ge_release {Germanium} 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.26100.36.0 Installation Date/Time {UTC} : 01/18/2025 at 19:7 PM Last Boot Up Date/Time {UTC} : 01/18/2025 at 23:0 PM Product ID : 00484-40000-00001-AA648 {Extended: 03612-04844-000-000001-03-1036-26100.0000-0182025} 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 : Clean Previous OS Upgraded From : N/A 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 : Automatic {Value:2} 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 : OS Preset or Customized Current Active Power Plan : OS Preset or Customized 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 : Undefined Exclude Drivers from MS/WU : Yes Pointing Device {Mouse} : VMware Pointing Device Hypervisor Present/Installed : No Virtual Machine Data : VMware {Hypervisor} Shipped with Reserved 7GB : No Dirty Shutdown Count : N/A 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 : CBCPV (Last 5 digits shown) Windows Default4 Installed : CBCPV (Last 5 digits shown) TPM Information : Active : N/A, Enabled : N/A, Owned : N/A, Version : N/A, Vendor : N/A =============== 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 : Yes {1} CompatTelRunner.exe {Appraiser} : Process is not running. {File is not 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 : 59.24 GB Free Space : 48.38 GB Partition Type : GPT Firmware Boot Type : UEFI Mode {R:2} Secure Boot Status : Disabled [Ref:1] File System : NTFS System Drive Letter : C: Interface Information : What mode an interface is in IDE Controller Mode : Integrated Drive Electronics {IDE} SCSI Controller Mode : Microsoft Storage Spaces Disk and Partition Information : Driveletter | Disk #, Partition # | Model Name {50 Chars max} | Size 'GB' \\.\PHYSICALDRIVE1 D: | Disk #1, Partition #0 | VMware Virtual NVMe Disk | 100 GB \\.\PHYSICALDRIVE0 C: | Disk #0, Partition #1 | VMware Virtual NVMe Disk | 59.24 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 : 16776244 KB (16 GB) Available Physical : 15060556 KB (14.36 GB) Total Page Size : 19790900 KB (18.87 GB) Available Page Size : 18395632 KB (17.54 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 3984396 KB (3.8 GB) Memory Type : Synchronous DRAM {3} Memory Error Correction : Non-ECC Memory Slots Fitted : 64 Memory Slots Used : 1 Memory Slots Free : 63 Motherboard's Max Memory : N/A DIMM Information {First Eight} : RAM slot #0 16384MB @ MHz On Hypervisors some results may be missing due to being being undefined within the VM's configuration file{s}. =================================================================================================================== Graphics Information =================================================================================================================== Adaptor Name : VMware SVGA 3D Adaptor DACType : n/a Adaptor Driver Information : 9.17.7.4 {2024/03/26} Adaptor Video Ram {See Notes} : N/A 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 : {If available} Unable to show results as WMI{C} not detected. Unknown State. Some values may not be accurate due to 32 bit API limitations. VRam does not include any 'Shared' or 'Dynamically' allocated memory. On Hypervisors some results may be missing due to being being undefined within the VM's configuration file{s}. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : Intel(R) 82574L Gigabit Network Connection Connection Status : Connected MAC Address : 00:0C:29:xx:xx:F8 Adaptor 3 Name : TAP-Windows Adapter V9 Connection Status : Media Disconnected MAC Address : 00:FF:24:xx:xx:7C =================================================================================================================== Processor 1 Information =================================================================================================================== Name : Intel(R) Core(TM) i9-14900K Architecture {Bits} : 64 L2 Cache Size {MB} : 8192 L3 Cache Size {MB} : 36864 Current / Max Speed {MHz} : 3187 / 3187 {Not Turbo Speed} Physical Cores : 4 Logical Cores : 4 Processor Id : 0x1F8BFBFF000B0671 Virtualization Mode : Enabled Manufacturer : GenuineIntel [Intel] Description : Intel64 Family 6 Model 183 Stepping 1 Motherboard Connection : CPU 0 OS Loaded Microcode Revision : 0x2B010000 Bios Microcode Revision : 0x2B010000 Processor Family : 2 Sockets/CPU's Present : 1 Feature Set : 0x000000003D1B3DFF 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 : VMware, Inc. System Product Name : VMware20,1 BaseBoard Manufacturer : Intel Corporation BaseBoard Product : 440BX Desktop Reference Platform BaseBoard Version : None PC System Type : Desktop {1} BIOS Vendor : VMware, Inc. BIOS Release Date : 05/22/2023 BIOS Version : VMW201.00V.21805430.B64.2305221830 Primary BIOS : Yes SMBIOS Present : Yes SMBIOS Version : 2.7 SLIC/BIOS Data : INTEL - 6040000 Valid SLIC Name : No Valid SLIC Table {See notes below} Possible Brand Theme : VMWare {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. : On Hypervisors some results may be missing due to being being undefined within the VM's configuration file{s}. =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : CY24M07D26-R158.BL Wallpaper Style : Fill image to display resolution Current Theme Used : $OEM$.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 : VL activation expires 4748 Days / 6837398 minutes Windows Licence Reason : No critical issues found Windows Product Key Channel : KMS:Client {VOLUME_KMSCLIENT} {R:PKC} 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 =================================================================================================================== 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 : N/A Windows Firewall Service State : Running {Reg: Auto} Security Product Name{s} : {If detected} Windows Defender ------------------------------------------------------------------------------------------------------------------- End of Report -------------------------------------------------------------------------------------------------------------------
Gui qt v1.02 rcx has an array issue that needs to be sorted. I thought I had cleared them all but one slipped through.
Hopefully fixed the array issue with GUI QT v1.02-rc6 which i have uploaded for beta testers Also tweaked the security product section so if Defender's real time scanning is disabled/off then it will show that in the result list. If defender has been removed by image editing/DISM tools then the defender information can be ignored. Slight DPI Aware code added to the manifest but not sure how it will look as i cannot test as no 2k/4k etc type screens, fonts may still be too small but the GUI framework should auto adjust...
The array error was when checking for any MSDM key, if it is a generated or non MSDM key it would cause the routine to crash. I have hopefully managed to skip past that section if the key is a non MSDM key or is invalid in some way.
Before the forum shows another 522 error Have uploaded 159 BC5 for beta testers, this will hopefully turn into the released baseline version. Just added a simple test for AutoUnattend.xml - only for log info as it not used by MRP but can be affected by the xml depending on what is within the file and how it acts on the OS and file system.
As mentioned previously mrp checks if certain scripts and xml files are present because those external scripts can affect how mrp operates. Examples: They could remove services or use dism/powershell commands in a way that confuses any mrp tweaks selected. Delete files, folders or empty the temp folders before mrp has completed or even started. Alter or remove registry enteries that mrp my require to be present or have certain values. ≈=============== Having those log enteries help when a user has a failed mrp install to determine if its a problem in mrp or caused by a user's external script.