Spoiler MRP - OEM Query Tool v16.1 Enhanced 07:04 PM Fri 28/04/2017 Basic OEM Information For This Computer --------------------------------------- OS Name: - Windows 10 Pro [x64] OS Edition/SKU: - Professional OS Language Name/Code: - en-US ( 1033 [409h] ) OS Locale: - en-US OS Language Value: - ENU Processor: - Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Processor Cores: - [4] Logical Processors: - [4] Processor Architecture: - [64 Bit] HDD Mode: - [AHCI] HDD Partition Type: - [MBR] Bios Version: - [F8, 09/30/2010] Total Physical Memory: - [12279 Mb] - Note: Memory Amounts May Available Memory: - [8723 Mb] Not Be Accurate. Scanned DMI ----------- #1 CSProduct Name: - P55-USB3L #2 CSModel Name: - P55-USB3L #3 CSBaseboard Prod: - P55-USB3L #4 CSProduct Vendor: - Gigabyte Technology Co., Ltd. #5 CSManufacturer: - Gigabyte Technology Co., Ltd. #6 Baseboard MFR: - Gigabyte Technology Co., Ltd. #7 Serial/Service Tag: - Not Shown On Saved Report. #8 BIOS ID: - GBT #9 SLIC OA: - Un-Listed #10 Installed PID Key: - Key Not Shown On Saved Report. #11 MSDM Key [OEM-DM]: - Un-Listed #12 BIOS Mode: - Legacy #13 Certificate: - Un-Listed #14 License Status: - Licensed SUMMARY ------- OEM Theme/Branding: - Gigabyte [id:-'#4'] OEM Activation Vista/7: - Un-Listed Valid OEM OS: - Un-Listed SLIC Table ---------- Un-Listed MSDM Table ---------- Un-Listed Certificate ----------- Un-Listed Maybe it's something about GPT? HDD detect normally with me on MBR
Spoiler: Mainsystem (selfbuild) QT Results Code: MRP - OEM Query Tool v16.1 Enhanced 07:07 PM Fri 04/28/2017 Basic OEM Information For This Computer --------------------------------------- OS Name: - Windows 10 Pro [x64] OS Edition/SKU: - Professional OS CompositionEditionID - Professional OS Language Name/Code: - en-US ( 1033 [409h] ) OS Locale: - en-US OS Language Value: - ENU Processor: - Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Processor Cores: - [4] Logical Processors: - [8] Processor Architecture: - [64 Bit] HDD Mode: - [AHCI] HDD Partition Type: - [MBR] Bios Version: - [P1.10, 03/25/2013] Total Physical Memory: - [15808 Mb] - Note: Memory Amounts May Available Memory: - [12431 Mb] Not Be Accurate. Scanned DMI ----------- #1 CSProduct Name: - To Be Filled By O.E.M. #2 CSModel Name: - To Be Filled By O.E.M. #3 CSBaseboard Prod: - C216 WS #4 CSProduct Vendor: - To Be Filled By O.E.M. #5 CSManufacturer: - To Be Filled By O.E.M. #6 Baseboard MFR: - ASRock #7 Serial/Service Tag: - Not Shown On Saved Report. #8 BIOS ID: - ALASKA #9 SLIC OA: - Un-Listed #10 Installed PID Key: - Key Not Shown On Saved Report. #11 MSDM Key [OEM-DM]: - Un-Listed #12 BIOS Mode: - Legacy #13 Certificate: - Un-Listed #14 License Status: - Licensed SUMMARY ------- OEM Theme/Branding: - Asrock [id:-'#6'] OEM Activation Vista/7: - Un-Listed Valid OEM OS: - Un-Listed SLIC Table ---------- Un-Listed MSDM Table ---------- Un-Listed Certificate ----------- Un-Listed Must have to do with the special chipset or UEFI/GPT, latter we can check in VM.
@BALTAGY It could be GPT. I remember Secure Boot can give some odd results when enabled, usually the SLIC if any present hence why i put that notice when it enabled.
Re Query Tool : Think i may of sussed the AHCI / IDE controller glitch, a slight timing problem in the checking.... Just double/triple checking things to make sure it has sorted it... -- Nope still same.... Spoiler: Boring explanation why [unable to define]..... Seems like the checks i am doing are correct, some custom chipsets may store the IDE/AHCI information in another area which WMIC not 'see' , usually it would default to IDE as the area has: Win32_IDEController as one of the results so my check returns IDE, a second check looks for AHCI which if the word AHCI is actually present will show something like: Intel (or other name for chipset provider) .... SATA AHCI Controller.... As the word AHCI is present then the check would change from IDE to AHCI, it not change if that word not present in the returned data. My default 'Unable to define' message would normally get over written either by IDE or AHCI, but as these custom chipsets not have that info stored in a place where WMIC looks then neither type is present so it returns as a no result, so my default message/variable is NOT overwritten. So if you have a custom chipset in your computer sadly nothing i can do to detect the controller info. As it only for information and is not critical for the QT or indeed MRP then i am not going to worry over it.
I've tested 16184 with the latest project (i used the bios file and EFI): I got an error after i gone thru the OOBE settings: "explorer.exe stopped working" Code: Multi-OEM/Retail Project Version : 170421-R55.0 - BaseLine [MRP/MDL] Required files present and extracted successfully. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: Fri 04/28/2017 [CHKOV] Windows 10 Pro Insider Preview x64 version detected. [CHKOE] Professional Edition installed. [CHKOB] Build Version: 16184.1001.amd64fre.rs_prerelease.170424-2211 [CHKOR] Build Revision: 1001 [OSLNG] Edition Language/Code: en-US ( 1033 [409h] ) [OSLNG] OS Locale: en-US [OSLNG] OS Language Value: ENU [MBDMI] Motherboard BIOS DMI Information [MBDMI] #1 CS Product Name : [VMware7,1] [MBDMI] #2 CS Model Name : [VMware7,1] [MBDMI] #4 CS Vendor Name : [VMware, Inc.] [MBDMI] #5 CS System Name : [VMware, Inc.] [MBDMI] #6 Baseboard Name : [Intel Corporation] [MBDMI] #8 BIOS ID : [INTEL] [HDDTY] Info: Standard HDD Detected. [CHKLF] Rename 'System Drive' flag enabled, 'C:' changed to 'Windows_10_Pro'. [CKDMI] Reading DMI for manufacture information. [THMOK] VMware [VMware] manufacture will be used for theme/branding. [BRND1] > Branding Extra Checks Section. [FTMNP] Force theme text file not present. [CHKMN] Computer Model Name: Undefined. [BRND2] > Brand Transfer Section. [BGDFC] Desktop backgrounds folder created. [W8XAP] > Windows 8.x/10 User Account Picture Management Section 1. [RMXML] OOBE.xml file deleted. [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. [THMMN] > Theme Management Section. [THMRP] VMware theme has been applied. [WXLS1] Log-In Background {img100.jpg} replaced. [TTFS0] > Transfer Theme Files Section. [OIFCS] System32\oobe\info folder has been created. [OIFCS] Required theme files transferred to System32\oobe\info folder. [TDYUP] > Deletion of unused MRP files. [BRNOK] Branding script has completed. [ADMAN] Add-On Manager Started. [CMSDM] > Checking if required Visual C 2012 DLL's are present. [CMSDM] > Required Visual C 2012 DLL's have been temporarily installed. [CMSDM] Checking BIOS for MSDM Table data. [CMSDM] No MSDM Table/Key detected in BIOS. [CMSDM] > Temporary Visual C 2012 DLL's used have been uninstalled. [ADMVM] Detected a 'Default DMI' VMware Virtual Machine. [USRAC] Enhanced Log-On screen has been enabled. [USRAC] 'User Account Picture' registry entry applied. [USRRO] 'Registered Owner' registry entry corrected. [USRD0] Detected 'defaultuser0', attempting to remove the account... [USRD0] Removal of 'defaultuser0' account successful. [AMBMP] > Checking BIOS's mode and System drive's partition type. [AMBMP] BIOS Mode: UEFI, Partition Type: GPT [AMHDC] HDD Controller Mode: AHCI [CHKLS] > Checking if Windows is activated/licensed. [CHKLS] License Status: Notification [CHKLS] Note: System reboot maybe required to complete 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. = ================================================================================ Enhanced Log Mode: Deactivated. The Multi-OEM/Retail Project has now completed. Will re-test asap, to see if it was something build related or MRP.
Looks like MRP completed ok, no errors shown within the log. Possible it is the preview build, depends what M$ have added/removed/tweaked.
Have done a silent update to the Query Tool - now v16.2, uploaded and link is now live. First post updated with password - almost forgot that bit! Added a time delay to the WMIC HDD controller mode checks to give a bit extra time to attempt to define, also altered the unable to define message to: [Unable To Define Mode - Possible Customized Chipset] Think this hopefully explains the possibility why it failed to say if IDE or AHCI when that message appears. Altered some of the information screens to now reflect what tasks are being performed at that stage as they was out of sync when moving code about when testing the HDD mode part. The CompositionEditionID line will now only appear if the EditionID and CompoEdID do not match, this will avoid any confusion why for 'normal' Editions it appeared twice. Other note: On Paste.co link has larger text as a few people mentioned the text was a bit too small. Added a Welcome bit too.
Finally did a new test-install: Code: Multi-OEM/Retail Project Version : 170421-R55.0 - BaseLine [MRP/MDL] Required files present and extracted successfully. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: Sat 04/29/2017 [CHKOV] Windows 10 Pro Insider Preview x64 version detected. [CHKOE] Professional Edition installed. [CHKOB] Build Version: 16184.1001.amd64fre.rs_prerelease.170424-2211 [CHKOR] Build Revision: 1001 [OSLNG] Edition Language/Code: en-US ( 1033 [409h] ) [OSLNG] OS Locale: en-US [OSLNG] OS Language Value: ENU [MBDMI] Motherboard BIOS DMI Information [MBDMI] #1 CS Product Name : [VMware Virtual Platform] [MBDMI] #2 CS Model Name : [VMware Virtual Platform] [MBDMI] #4 CS Vendor Name : [VMware, Inc.] [MBDMI] #5 CS System Name : [VMware, Inc.] [MBDMI] #6 Baseboard Name : [Intel Corporation] [MBDMI] #8 BIOS ID : [DELL] [HDDTY] Info: Standard HDD Detected. [CHKLF] Rename 'System Drive' flag enabled, 'C:' changed to 'Windows_10_Pro'. [CKDMI] Reading DMI for manufacture information. [VMWCF] VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. [THMOK] Dell [VMware] manufacture will be used for theme/branding. [BRND1] > Branding Extra Checks Section. [FTMNP] Force theme text file not present. [CHKMN] Computer Model Name: 'VMware Virtual Platform' applied. [BRND2] > Brand Transfer Section. [BGDFC] Desktop backgrounds folder created. [W8XAP] > Windows 8.x/10 User Account Picture Management Section 1. [RMXML] OOBE.xml file deleted. [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. [THMMN] > Theme Management Section. [THMRP] Dell theme has been applied. [WXLS1] Log-In Background {img100.jpg} replaced. [TTFS0] > Transfer Theme Files Section. [OIFCS] System32\oobe\info folder has been created. [OIFCS] Required theme files transferred to System32\oobe\info folder. [TDYUP] > Deletion of unused MRP files. [BRNOK] Branding script has completed. [ADMAN] Add-On Manager Started. [CMSDM] > Checking if required Visual C 2012 DLL's are present. [CMSDM] > Required Visual C 2012 DLL's have been temporarily installed. [CMSDM] Checking BIOS for MSDM Table data. [CMSDM] Professional is installed, the MSDM Key will be saved only. [CMSDM] Processing MSDM Key for Edition status. [CMSDM] > Show MSDM Edition and Var Information. [CMSDM] > Var: OSVER {WMIC} : 'Professional' [CMSDM] > Var: RealEdition : 'Professional' [CMSDM] > Var: KeyEditionID : 'ProfessionalEducation' [CMSDM] MSDM Key Information: Win 10 ProfessionalEducation MSDM [CMSDM] The MSDM Key is not for the Edition installed, saved only. [CMSDM] See C:\MSDM-Key.txt for the saved MSDM key details. [CMSDM] > Temporary Visual C 2012 DLL's used have been uninstalled. [ADMVM] Detected a 'Default DMI' VMware Virtual Machine. [USRAC] Enhanced Log-On screen has been enabled. [USRAC] 'User Account Picture' registry entry applied. [USRRO] 'Registered Owner' registry entry corrected. [USRD0] Detected 'defaultuser0', attempting to remove the account... [USRD0] Removal of 'defaultuser0' account successful. [AMBMP] > Checking BIOS's mode and System drive's partition type. [AMBMP] BIOS Mode: Legacy, Partition Type: MBR [AMHDC] HDD Controller Mode: AHCI [CHKLS] > Checking if Windows is activated/licensed. [CHKLS] License Status: Notification [CHKLS] Note: System reboot maybe required to complete 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. = ================================================================================ Enhanced Log Mode: Deactivated. The Multi-OEM/Retail Project has now completed.
[CMSDM] blah blah is installed, the MSDM Key will be saved only. This will appear on insider/preview Editions if there is a MSDM table present as i think insider Editions are only activated with the insider key, it used to be. If they can also be activated now via a valid MSDM table, (if one is present), and Edition is a match for the OA3 key then i can change the flag so that they will activate via MSDM. Otherwise it will just save the key and ignore auto insertion.
No, insiders are activated the same way as official builds (oem : dm/HWID/key), The old insider account activation disappeared during the pre_releases of 14393 RS2. @s1ave77 : this is my standard test VM with the oem : dm for Pro-edu, the first attempt was with an oem : dm for core (if i remember correctly). The first attempt glitched just after OOBE, this new test ran just fine Will do more testing later
Ah ok wasnt sure if the way these newer insider ones no longer used the 'insider' key. I will change the flag and set as 0 = use msdm if present. Thanks for confirming. MRP 55.1 has the flag changed for insider editions, if MSDM key present and a match to the Edition installed it will use the key insertion as per non insider ones.
That why i always use MSDM or OA3 instead on oem: dm, i am so used to referring to the msdm key this way.
There was nothing wrong in the log, afaik. I installed standard pro on a VM with an oem : dm for pro-edu.
Log was ok, just noticed it had that line i referred to in previous post. Didn't realize M$ changed from insider key to 'normal' ways to activate. Have altered code in MRP so not to ignore the msdm key if it present and for the installed edition it will use that instead of ignoring it. I am guessing some Server editions also can use MSDM? 'WebServer Next' as seen in the pkconfig file. Gez this is getting confusing lol.