Query Tool v30.1 uploaded, first post updated with new password. Change Summary + Added 'Digital License' if one is detected, for example: #14 License Status - Licensed {Retail/Digital License} or #14 License Status - Licensed {OEM_DM/Digital License} - Windows 10 only. - Removed 'Channel' word as due to the padding used and fixed length it sometimes would chop off the wording. No other changes made, hence why the .1 version change.
hmm the Slic Version showing possible emulation (but the fixed length chopped it off!). Not sure why it detected a emulation minor glitch, not changed any code in that area.
Code: MRP - OEM Query Tool v30.1 Enhanced -- Wed 10/11/2017 -- 10:18pm ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Name - Windows 10 Pro x64 OS Edition {Registry} - Professional OS Edition {WMIC} - Professional OS Build Number - 16299 OS Update Build Revision - 15 {Baseline Release} OS Language Name/Code - en-US / { 1033 [409h] } OS Locale - en-US OS Language Value - ENU OS Installation Date - 10/10/2017 2:53:53 AM CPU Name - Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz CPU Description - Intel64 Family 6 Model 58 Stepping 9 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [4] / [8] HDD Mode/Partition - [AHCI] / [MBR] Bios Version - [P1.10, 03/25/2013] Total Physical Memory - [15808 Mb] Available Memory - [8121 Mb] GPU Primary Adaptor Name - [Intel{R} HD Graphics 4000] -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - To Be Filled By O.E.M. #09 SLIC Version - No SLIC Table Detected {Possib #02 CSModel Name - To Be Filled By O.E.M. #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - C216 WS #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - To Be Filled By O.E.M. #11 MSDM Edition - Undefined #05 CSManufacturer - To Be Filled By O.E.M. #11 MSDM Brand Name - Undefined #06 Baseboard MFR - ASRock #12 BIOS/Boot Mode - Legacy/MBR #07 Serial/Service Tag - Undefined #13 Certificate - Not Present #08 BIOS or SLIC ID - ALASKA #14 License Status - Licensed {Retail/Digital License} ----------- - Summary - ----------- OEM Theme/Branding - Asrock [id: #06] OEM Activation Vista/7 - Un-Listed Valid OEM Consumer OS - Un-Listed .Net Versions Detected - v1.1.4322 v2.0.50727 v3.5 v4.0.30319 v4.7.02556 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 ** End of Query Tool report. ** I have the windslic entry still in my boot options, maybe because of that?
Ah yeah never thought of that! As WindSlic is detected as an emulation the QT would pick it up if it still present on the HDD. Phew thought i had screwed up something lol.
I tested on loads of pc's/vm's to make sure no gremlin sneaked in. Another undocumented feature that the QT detects WindSlic is still present.
I knew the code was written in ages ago before i took over the project, never actually seen it in action. Was a shock lol.
@The_Guardian, I saw the MAK key stuff in the code and never touched it or even tested it But yes it works
I have made changes to the QT to show {Emulated?} instead of {Possible Loader}. I wont release v30.x just yet as more tests will need to be done. *edit* Issue was because of dual-booting with 7 (using loader), it confused the QT. The QT will ignore the emulation tests if the OS the QT is run on does not detect a SLIC. Tests in progress and once happy with results I will upload the new QT. Sorry for the quick updates but i am one that wants to make sure everything runs as expected. This is the reason i ask for feedback, if you are unsure of the results found in the QT or MRP mention it, i cant fix something i not know about!
Query Tool v30.3 Uploaded, first post updated with new password. + Fixed emulated/loader detection glitch, this was on dual+ boot systems as the QT would still 'see' the loader was present even when on a OS that it was not used on ie W8.x/10. + A little code tidy up due to the above fix.
Can I ask something different here? Since you are all cool and all... You know what you're talking about... You can help me understand. I used these files and this method to create my own ISO, and successfully used it before (a previous version) 1- I wanna know what we are doing here, What does that $oem$ folder or oobe and others do? Generally, what are we doing tweaking those files? 2- Is this all for activation? How does this differ from other ways of activation like daz? (I remember I had problems with classic ways of activation, and then someone pointed me here and this worked) 3- I remember reading something like "If you have genuine windows and it's your first installation of a pirated copy, then it won't work", is this true? If so, why? 4- While I'm at it, can I add simplix updates to the iso, easily?
First off MRP uses the OEM activation system, for vista/7/server using SLIC, Cert and SLP-Key, 8.x/10 uses MSDM (internal key within the bios). Roughly the same way the OEM maker would set up their systems with branding and activation. Also Brands the computer depending on DMI (internal bios area with board manufacture such as Acer,HP etc), or SLIC/MSDM brand name. You can also use a custom branding if you so wish, or tell MRP to use another brand, all details are within the Optional folder in the archive on how to do that. If you wish to use Loader or KMS solutions you need to use those within either SetupComplete.cmd or manually after OS installation. All information is on the first post. I will be writing up a PDF when i get time with how everything works to make things hopefully clearer as some of the information on the first post is slightly out of date due to the advancements within the project.
Simplix is another program, to do that you need to see the Simplix thread here on MDL on how to use/integrate the updates. https://forums.mydigitallife.net/th...egrate-hotfixes-into-win7-distribution.45005/