Just checking on my other pc which has Intel HD graphics... It has 01/28/20 What is strange on my other ps the cpu is a G3220 Haswell, but that has a date of 2013, i would of thought as it integrated into the cpu that the gpu date be the same.
Researching on the net found out that the Intel HD Graphics first appeared in 2010, so if anything it should say mm/dd/10 , very strange!
Not sure, that is the only location in the registry that has any date for the Videobios. WMIC has no way of reading that info, only name (which i use to obtain that).
The guy who wrote GPUz made his own driver that reads the gfx cards direct and its in C++ as far as i know so i wouldn't understand it if i had the source code for that driver lol
Just my 2ยข GPU-Z reports that the release date for this HD Graphics 4600 is 1 June 2013... My laptop has the Nvidia GeForce GTX 860M but I use the HD Graphics 4600 as the Primary (Default) Graphics and the GTx 860M for specific programs...
Must be windows not obtaining the correct date info for Intel graphics, or interprets it in a back-to-front way? Will remove that videobios date or ignore it if Intel grfx is detected on next QT.
Query Tool v24.3 uploaded. Removed the line for Video Bios Date. It is not 100% reliable. It is only cosmetic so it not affect the QT itself. Have left the GPU Name in just renamed that as 'GPU Primary Adaptor Name' as that part seems to work! Sorry about releasing a version that not meet standards.
16362 CoreSL activated by Pro HWID: https://forums.mydigitallife.net/th...build-16362-pc-skip-ahead.75123/#post-1370866 MRP log is there too
Most odd that Core SL gets activated by a Pro DL! Unless a Core HWID in the VM activated it? Shouldn't do either as it a different Edition.
Code: Multi-OEM/Retail Project Version : 170914-R65.0 - RC [MRP/MDL] Required project files extracted successfully. DeCompile has detected a 'VMware' Virtual Machine. OEM's folder detected, structure appears OK. Enhanced Log Mode: Enabled. W10TB option enabled: Windows 10 Title Bars will be Colorized. OS Installation Date/Time: 15.09.2017 -- 01:28am [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version Installed : Windows 10 Pro for Workstations x64 [OSINF] Edition {Registry} : ProfessionalWorkstation [OSINF] Edition {WMIC} : ProfessionalWorkstation [OSINF] Build Information : 16288.1.amd64fre.rs3_release.170909-0851 [OSINF] Update Build Revision : 1 [OSINF] Edition Language/Code : de-DE { 1031 [0] } [OSINF] Locale : de-DE [OSINF] Language Name Value : DEU [OSINF] ======================= [MBINF] ======================= [MBINF] Motherboard Information [MBINF] ======================= [MBINF] #01 CS Product Name : [VMware Virtual Platform] [MBINF] #02 CS Model Name : [VMware Virtual Platform] [MBINF] #04 CS Vendor Name : [VMware, Inc.] [MBINF] #05 CS System Name : [VMware, Inc.] [MBINF] #06 Baseboard Name : [Intel Corporation] [MBINF] #08 BIOS or SLIC ID : [DELL] [MBINF] #09 SLIC Version : [v2.2] [MBINF] #11 MSDM Brand Name : [Dell] [MBINF] ======================= [CMINF] ======================= [CMINF] CPU/Memory Information [CMINF] ======================= [CMINF] CPU Name/Type : [Intel{R} Core{TM} i5-3570K CPU @ 3.40GHz] [CMINF] CPU Description : [Intel64 Family 6 Model 58 Stepping 9] [CMINF] CPU Architecture : [32/64 Bit Instruction Set] [CMINF] CPU Cores/Threads : [2] / [2] [CMINF] Total Physical Memory : [5403 Mb] [CMINF] Available Memory : [4867 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Pro-WS'. [CKDMI] Querying BIOS for manufacturer branding information. [NODMI] No valid DMI Manufacturer detected, using SLIC name. [THMOK] Dell [#08] manufacturer detected for automated theme/branding. [CHKMN] Computer Model Name: 'VMware Virtual Platform' has been applied. [BRND1] -> Branding Extra Checks Section. [FTHNU] Force_Theme file was not detected. [THMMS] -> OEM Brand Transfer Management Section. [WPCHK] Wallpaper.jpg transferred. [BGDFC] Desktop backgrounds folder created. [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg. [W8XAP] -> Windows 10: User Account Picture Management Section 1. [RMXML] OOBE.xml file processed. [UBREP] User.bmp replaced. [UPREP] User.png replaced. [UPREP] User-40.png replaced. [WXAP2] -> Windows 10: User Account Picture Management Section 2. [UPREP] User-32.png replaced. [UPREP] User-48.png replaced. [UPREP] User-192.png replaced. [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg. [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg. [OTFTS] -> OEM Theme Files Transfer Section. [OTFTS] OEM theme folder has been created. [OTFTS] OEM files have been transferred. [THMSA] Dell theme has been applied. [BSHCS] Branding script has completed. [ADMAN] Add-On Manager: Started. [CMSDM] Querying BIOS for any MSDM data. [CMSDM] Processing MSDM Key... [CMSDM] -> Show WMIC/MSDM Edition/Channel Information. [CMSDM] -> {WMIC} OS Edition : 'ProfessionalWorkstation' [CMSDM] -> {MSDM} KeyEditionID : 'ProfessionalWorkstation' [CMSDM] -> {MSDM} ChannelID : 'MSDM' [CMSDM] Key Detection Routine Used : 1 [CMSDM] MSDM Key Information: Win 10 ProfessionalWorkstation [CMSDM] The detected MSDM key can be used for the Edition installed, saved and applied. [CMSDM] The MSDM key details have been saved in C:\MSDM-Key.txt. [USRAC] Windows 10 Enhanced Log-On screen has been enabled. [W10TB] Windows 10 TitleBar Grey Colorization applied. [USRAC] 'User Account Picture' registry entry applied. [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected. [USRD0] Detected 'defaultuser0', removal process started. [RDUPM] Removal of 'defaultuser0' account was successful. [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type. [AMBPS] BIOS/Boot Mode : Legacy [AMBPS] Partition Type : MBR [AMHDC] SSD/HDD Mode : AHCI [CHKLS] -> Checking if Windows is activated/licensed. [CHKLS] License Status: Notification [CHKLS] Online connection required to complete MSDM activation. [ADMAN] Add-On Manager: Completed. [CLNUP] MRP Clean Up Routine Processed. ================================================================================ = Please Note: It is advisable to logout or reboot your computer when possible = = to allow the User and Log-On background pictures to finalize. = ================================================================================ The Multi-OEM/Retail Project has completed.
[NODMI] No valid DMI Manufacturer detected, using SLIC name. Thanks for the test @s1ave77 - realized the VM detection routine was in wrong place so it never checked that , have sorted that now and re-wrote the section too, more efficient now and has expanded capabilities. Just testing latest T3.... *edit* New VM routine works perfectly. Now shows: [VMWSD] VMware with a SLIC detected, using Dell [#08] for branding. or [VMWMD] VMware with a MSDM detected, using Dell [#11] for branding. Dell is used in this example, this will change to the name detected in the SLIC or MSDM (if present).
MRP 65.0 is about out of Test 5 RC stage, just a few more quick tests. Added DarkGrey - Active/LightGrey - Inactive Win 10 Titlebar colorization. Choice of Blue, Grey or the default white titlebars - this last one is when the 'W10TB=No' is set in the oobe.cmd. Which is the default setting as it is REM'd ( :: ) out so its disabled. If you set the option to colorize 'W10TB=Yes' but not the 'WXTBColor' option (Blue or Grey) it will default to Blue. As always by default any user options are OFF/disabled by default so you can decide if you wish to use them or not. Quite a bit of re-coding and changes to some sections has been done, it is now more efficient, extra error checks added and old ones upgraded. Tests have not detected any new bugs as such but as always cannot guarantee there isn't a sneaky one that will appear on someones computer setup!
MRP 65.0 is now out of RC testing stages and now is Baseline. Uploaded - First post updated with new password. Query Tool 25.0 uploaded too, nothing exciting but a little re-coding done too. See ChangeLog.txt for details. The oobe.cmd also has information within about the flag/options available. OFF by default.