Will look into it although it may take a while as the line number is beyond the actual GUI scripts total i wrote, i think that referring to a #include which gets added to the top thereby moving my code to the end..
Fixed the subscript out of range (hopefully), after investigation it was when testing the BIOSVersion string from Win32_BIOS, if the result was a invalid result then it caused the array check to fail. Now it will return 'N/A' if invalid for any reason. Also fixed a 'potential' same issue when checking the possible theme name, which uses a similar system for scanning the data. A invalid result will be either N/A or nothing. Uploaded .35 to post #3 I was right that when compiled the #include files push the main script towards the end, so from my 200kb file it ends up over 1.25MB !
Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v0.10.2.35 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 11/27/2022 -- 16:38 {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 being unable to detect. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 10 Enterprise N 2015 LTSB OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.10240 {UBR:19567} Language : English (United States) Native Language : English Installed/Available Languages : en-US Stock Keeping Unit {SKU} : 126 Experience Pack : N/A Installation Date : 8/31/2015 at 7:33 AM {UTC} Shipped with Reserved 7GB : N/A Dirty Shutdown Count : 6 Build Branch : th1 Product ID : 00330-20000-00001-AA615 {Extended: 03612-03302-000-000001-03-1033-10240.0000-2432015} TimeZone {TZUtil} : W. Europe 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 Hypervisor Present : No Virtual Machine Data : VirtualBox {Open-Source Hypervisor} Windows Key 1 Installed : D69TJ (Last 5 digits shown) Windows DpID4 Installed : D69TJ (Last 5 digits shown) Windows Default Installed : 4C2J8 (Last 5 digits shown) Windows Default4 Installed : 4C2J8 (Last 5 digits shown) TPM Information : N/A =================================================================================================================== System Drive C: Partition Information =================================================================================================================== Drive Type : Non SSD BUS Type : Serial ATA (SATA) Total Space : 31.51 GB Free Space : 18.33 GB Partition Type : MBR Firmware Boot Type : Legacy/MBR Mode {R:1} Secure Boot Status : N/A File System : NTFS Model Name : VBOX HARDDISK Disk and Partition Information : Driveletter | Disk #, Partition # | Model Name {50 Chars max} | Size 'GB' \\.\PHYSICALDRIVE0 C: | Disk #0, Partition #1 | VBOX HARDDISK | 31.51 GB \\.\PHYSICALDRIVE1 S: | Disk #1, Partition #0 | VBOX HARDDISK | 8.37 GB Drive letters/Partitions are shown as they are defined via the connected ports in the BIOS. =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 4193844 KB (4 GB) Available Physical : 2723796 KB (2.6 GB) Total Page Size : 12844596 KB (12.25 GB) Available Page Size : 11387892 KB (10.86 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 4011232 KB (3.83 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 : VirtualBox Graphics Adapter for Windows 8+ Adaptor DACType : Oracle Corporation Adaptor Driver Information : 5.2.45.0 {2020/07/31} Adaptor Status : Active Adaptor Name : Not Detected Adaptor DACType : N/A Adaptor Driver Information : N/A Adaptor Status : Inactive Virtual Desktop Resolution : 3840 x 2070 Bits Per Pixel : 32 Video Mode Description : 3840 x 2070 x 4294967296 colors {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 being unable to detect. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : Red Hat VirtIO Ethernet Adapter Connection Status : Connected =================================================================================================================== Processor 1 Information =================================================================================================================== Name : AMD FX-8370 Eight-Core Processor Architecture {Bits} : 64 L2 Cache Size {KB} : L3 Cache Size {KB} : -- Current Speed {MHz} : 4085 Physical Cores : 1 Logical Cores : 1 Processor Id : Virtualization Mode : Enabled Manufacturer : AuthenticAMD [AMD] Description : AMD64 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 : N/A Valid SLIC Name : No Valid SLIC Table Possible Brand Theme : VBox {System Manufacturer} SLIC Table Status : SLIC table with valid marker present {v2.4} 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 =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : N/A Wallpaper Style : Fill image to display resolution Current Theme Used : Custom.theme Installed Dot Net Frameworks : 2.0 3.0 3.5 4.6 4.0 Installed Powershell Versions : 1.0, 2.0, 3.0, 4.0, 5.0 Security Product Name{s} : Avast Antivirus Defender Tamper Protection : Disabled Defender Service Status : Boot Windows Firewall Service State : Running {Reg: Auto} Windows Activation Status : VL activation expires 179 Days / 258088 minutes Windows Licence Reason : Valid key was used for the product's licensing channel 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 ------------------------------------------------------------------------------------------------------------------- "No Valid SLIC Table", yet "SLIC table with valid marker present {v2.4}". But it won't crash anymore.
I think the bios info is confusing something, it works on other pc's it could be VBox, i had a bit of hassle when i had a vbox vm setup and attempting to add a slic table in. Msdm was the one that broke the VM so be careful if adding a MSDM table into a vbox vm! Will have to recheck but not sure if i can sort it as the Win32_bios isn't giving the data back in this case or is but invalid or no object found, cant catch the error at moment.. But at least the 2.4 with marker is working. At least no crashes because that was the only routine the line number was referencing... If the bios data isnt valid for some reason then the routine sets N/A (or no slic table) return to prevent crashes. SLIC/BIOS Data : N/A <----- tells me that the returned data was not valid..
I know on some HP/Lenovo/Sony and the odd Acer the slic is obscured when win8.x and above is installed, not sure if that is what is happening in the LTSB/C case? It is the bios that does the 'hiding', doubt vbox does that, not seen it in the changelogs
Uploaded .36 to post #3 Added extra error checking. If the biosversion result gives an error via the WMI call then 'No WMI Object" will be displayed, if the result is invalid for some other reason then 'N/A' is shown. This also helps with debugging.
What does it do at "1% Initialization"? On build 25247.1000, it hangs there and hasn't moved on for a long time. CPU utilization for the process is 90%-100% the whole time. reg.exe, findstr.exe and multiple command windows constantly open and close, but I'm slowly getting the impression that it's running around in circles...
1% -10% is detecting OS information, it has Pshell, vbscript etc running. I just endtask and re-run the exe.
It never moves away from 1%, and hangs every time. New log from 2015 LTSB: Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v0.10.2.36 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 11/27/2022 -- 18:27 {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 being unable to detect. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 10 Enterprise N 2015 LTSB OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.10240 {UBR:19567} Language : English (United States) Native Language : English Installed/Available Languages : en-US Stock Keeping Unit {SKU} : 126 Experience Pack : N/A Installation Date : 8/31/2015 at 7:33 AM {UTC} Shipped with Reserved 7GB : N/A Dirty Shutdown Count : 7 Build Branch : th1 Product ID : 00330-20000-00001-AA615 {Extended: 03612-03302-000-000001-03-1033-10240.0000-2432015} TimeZone {TZUtil} : W. Europe 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 Hypervisor Present : No Virtual Machine Data : VirtualBox {Open-Source Hypervisor} Windows Key 1 Installed : D69TJ (Last 5 digits shown) Windows DpID4 Installed : D69TJ (Last 5 digits shown) Windows Default Installed : 4C2J8 (Last 5 digits shown) Windows Default4 Installed : 4C2J8 (Last 5 digits shown) TPM Information : N/A =================================================================================================================== System Drive C: Partition Information =================================================================================================================== Drive Type : Non SSD BUS Type : Serial ATA (SATA) Total Space : 31.51 GB Free Space : 18.34 GB Partition Type : MBR Firmware Boot Type : Legacy/MBR Mode {R:1} Secure Boot Status : N/A File System : NTFS Model Name : VBOX HARDDISK Disk and Partition Information : Driveletter | Disk #, Partition # | Model Name {50 Chars max} | Size 'GB' \\.\PHYSICALDRIVE0 C: | Disk #0, Partition #1 | VBOX HARDDISK | 31.51 GB \\.\PHYSICALDRIVE1 S: | Disk #1, Partition #0 | VBOX HARDDISK | 8.37 GB Drive letters/Partitions are shown as they are defined via the connected ports in the BIOS. =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 4193844 KB (4 GB) Available Physical : 2801632 KB (2.67 GB) Total Page Size : 12844596 KB (12.25 GB) Available Page Size : 11452828 KB (10.92 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 4011200 KB (3.83 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 : VirtualBox Graphics Adapter for Windows 8+ Adaptor DACType : Oracle Corporation Adaptor Driver Information : 5.2.45.0 {2020/07/31} Adaptor Status : Active Adaptor Name : Not Detected Adaptor DACType : N/A Adaptor Driver Information : N/A Adaptor Status : Inactive Virtual Desktop Resolution : 3840 x 2070 Bits Per Pixel : 32 Video Mode Description : 3840 x 2070 x 4294967296 colors {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 being unable to detect. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : Red Hat VirtIO Ethernet Adapter Connection Status : Connected =================================================================================================================== Processor 1 Information =================================================================================================================== Name : AMD FX-8370 Eight-Core Processor Architecture {Bits} : 64 L2 Cache Size {KB} : L3 Cache Size {KB} : -- Current Speed {MHz} : 4085 Physical Cores : 1 Logical Cores : 1 Processor Id : Virtualization Mode : Enabled Manufacturer : AuthenticAMD [AMD] Description : AMD64 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 : No WMI Object Valid SLIC Name : No Valid SLIC Table Possible Brand Theme : VBox {System Manufacturer} SLIC Table Status : SLIC table with valid marker present {v2.4} 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 =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : N/A Wallpaper Style : Fill image to display resolution Current Theme Used : Custom.theme Installed Dot Net Frameworks : 2.0 3.0 3.5 4.6 4.0 Installed Powershell Versions : 1.0, 2.0, 3.0, 4.0, 5.0 Security Product Name{s} : Avast Antivirus Defender Tamper Protection : Disabled Defender Service Status : Boot Windows Firewall Service State : Running {Reg: Auto} Windows Activation Status : VL activation expires 179 Days / 257976 minutes Windows Licence Reason : Valid key was used for the product's licensing channel 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 -------------------------------------------------------------------------------------------------------------------
at least i know the wmi object is the issue of the original crash. will look into the initialize section.
Scratch that, seems like it is the same as with the 10% "hang". It eventually completes and is just needing a looong time for reasons unknown. Log from Dev, as you see, the Dell SLIC is detected right. So, VM isn't preventing detection, seems like version is. Code: ------------------------------------------------------------------------------------------------------------------- Query Tool GUI v0.10.2.36 ------------------------------------------------------------------------------------------------------------------- Log Date {UTC}: 11/27/2022 -- 18: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. On Hypervisors some results may be missing due to being unable to detect. GUI Font Used : Lucida Console Size: 11 =================================================================================================================== Operating System Information =================================================================================================================== Installation Type : Client Name : Microsoft Windows 11 Enterprise Insider Preview OS/CPU Architecture : CPU and OS is 64 bit Build : 10.0.25247 {UBR:1000} {22H2} Language : English (United States) Native Language : English Installed/Available Languages : en-US Stock Keeping Unit {SKU} : 4 Experience Pack : 1000.25247.1000.0 Installation Date : 11/21/2022 at 15:28 PM {UTC} Shipped with Reserved 7GB : No Dirty Shutdown Count : N/A Build Branch : rs_prerelease Product ID : 00329-00000-00003-AA874 {Extended: 03612-03290-000-000003-03-1033-25247.0000-3252022} TimeZone {TZUtil} : W. Europe Standard Time Hours offset from GMT : 1 Daylight Saving In Effect : No Daylight Adjust Clock Mode : Enabled/Checked Upgrade or Clean Installation : Upgraded on 9/8/2019 {UTC} Previous OS Upgraded From : Windows 10 Pro Hypervisor Present : No Virtual Machine Data : VirtualBox {Open-Source Hypervisor} 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 : Non SSD BUS Type : Serial ATA (SATA) Total Space : 33.5 GB Free Space : 10.95 GB Partition Type : MBR Firmware Boot Type : Legacy/MBR Mode {R:1} Secure Boot Status : N/A File System : NTFS Model Name : VBOX HARDDISK Disk and Partition Information : Driveletter | Disk #, Partition # | Model Name {50 Chars max} | Size 'GB' \\.\PHYSICALDRIVE0 C: | Disk #0, Partition #1 | VBOX HARDDISK | 33.5 GB \\.\PHYSICALDRIVE1 S: | Disk #1, Partition #0 | VBOX HARDDISK | 8.37 GB Drive letters/Partitions are shown as they are defined via the connected ports in the BIOS. =================================================================================================================== Memory Information =================================================================================================================== Total Physical : 4193844 KB (4 GB) Available Physical : 1932100 KB (1.84 GB) Total Page Size : 12844596 KB (12.25 GB) Available Page Size : 10250456 KB (9.78 GB) Total Virtual Size : 4194176 KB (4 GB) Available Virtual : 3999920 KB (3.81 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 : VirtualBox Graphics Adapter for Windows 8+ Adaptor DACType : Oracle Corporation Adaptor Driver Information : 5.2.45.0 {2020/07/31} Adaptor Status : Active Adaptor Name : Not Detected Adaptor DACType : N/A Adaptor Driver Information : N/A Adaptor Status : Inactive Virtual Desktop Resolution : 3840 x 2070 Bits Per Pixel : 32 Video Mode Description : 3840 x 2070 x 4294967296 colors {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 being unable to detect. =================================================================================================================== Network Adaptor Information =================================================================================================================== Adaptor 1 Name : Red Hat VirtIO Ethernet Adapter Connection Status : Connected =================================================================================================================== Processor 1 Information =================================================================================================================== Name : AMD FX-8370 Eight-Core Processor Architecture {Bits} : 64 L2 Cache Size {KB} : L3 Cache Size {KB} : -- Current Speed {MHz} : 4085 Physical Cores : 1 Logical Cores : 1 Processor Id : Virtualization Mode : Enabled Manufacturer : AuthenticAMD [AMD] Description : AMD64 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 : DELL - 1 Valid SLIC Name : Dell Possible Brand Theme : VBox {System Manufacturer} SLIC Table Status : SLIC table with valid marker present {v2.6} 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 =================================================================================================================== Miscellaneous Information =================================================================================================================== Which MRP Version Used : CY22M09D30-R147.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} : Windows Defender Defender Tamper Protection : Enabled Defender Service Status : Auto Windows Firewall Service State : Running {Reg: Auto} Windows Activation Status : VL activation expires 158 Days / 228130 minutes Windows Licence Reason : Valid key was used for the product's licensing channel 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 -------------------------------------------------------------------------------------------------------------------
I will add extra % progress bits so where it 'hangs' i can find out which bit it taking a long time on. It seems random as sometimes its ok others it can just lock up. I will upload that to the #3 area in the morning as too tired at moment.
this will have roughly more increments in the 1% - 20% areas which will hopefully stop where it 'hanging' i might then be able to locate the part, probably one of the wmic or PS calls...
I know i use wmic calls via a runwait() command which isnt perfect but saves a lot of code for a single result. Im guessing it may be the way i have to parse the stdout to get the result. Same way with the odd pshell line, will have to rewrite parts that causing the long delays where i can.
If it was that tosh laptop i have 30 mins be quick lol But no it should be faster than that even on a vm. If it takes longer than 30 seconds i endtask the qt and re run it. I just thought it was my clevo laptop i use that hung as i got several things on the go. Will see where i can speed things up. The 1 to 15% is all the os detection stuff, like tpm, edition, upgraded info etc quite a lot, may split some into other areas. *edit fixed spelling - (phone autocorrect had a bad hair day i think!)
Hopefully speeded things up as now on the processwait (when such external commands like WMIC etc) is run i have limited to a max of 5 seconds to obtain the result from the call, plus a additional 100th second delay to allow the process's PID to be closed to prevent memory leaks, although AutoIT does close the opened PIDs at the end of program run (or exit from a crash). The 5 seconds may need to be adjusted if it too quick, but that can be tweaked as time goes on, im guessing 5 secs is close to ideal but a max of 10 seconds may be required on some slow commands.