I know from past experience that slipstreaming can cause issues if not done correctly. MDL has some master's at doing AIO and slipstreaming so it is a matter of what method was used and what order the updates were slipstreamed. Your right about the activators being included in a lot of AIO ISO's or slipstreamed ISO's, that can be bad news. Most end users just see an AIO or slipsteam ISO and they get excited without doing research on the method used and if any extra's are included. Great job on the project by the way. You have mastered it. "Important: If you use a 3rd party 'homebrew' ISO for installing Windows from such groups as Gen2 please be aware due to their 'pre-activation' and OEM additions this may cause your install to fail or 'hang' due to conflicts with MRP." I love it.
That's OK, but I use MRP for many years as well as Gen2 installations and I've never had problems like with the latest version of MRP. I went back to the old MRP and it all worked again.
I finally finished my other project. I get to use the new mrp tomorrow on wife computer. Its a Toshiba so I dont expect any issues.
@The_Guardian with Toshiba, you may see the conflict resolution kick in if the CSName has Satelite in the DMI, as i parse it in a slightly different way to obtain the Toshiba name in this case. It works quite well. -----------------------------------------Regarding 3rd Party AIO Etc ISO's The later Gen2 iso's, (maybe other versions like them), with their 'pre-activation' cause the conflict because they may use a modified setupcomplete.cmd and something within that is what causes the install to 'hang', whatever they add upsets the Windows setup when used with the latest Project. I cannot give support for those type of ISO images because i do not know what they add, or any other hidden 'extras' !
Last time i've seen one it contained a cmd with pages of code, looked like someone cut/paste all code in one.
An update with QT/MRP and a dummy MSDM table. Alphawaves has kindly patched/edited the tools used to obtain the information to allow MRP/QT to process the tables. Tested and they work perfectly. So now the project will have two methods to detect a dummy/corrupted table. Many thanks @Alphawaves
Updated Query Tool v27.0 with new tools from Alphawaves. Few other little tweaks done while adjusting code. See changelog.txt, nothing exciting i am afraid. First post updated with new password and download link for the QT27 is ready. MRP will be updated when the next release is out of testing. Not for a little while yet!
Code: Multi-OEM/Retail Project Version : 170926-R67.0.T3 - 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 to Grey. OS Installation Date/Time: Tue 09/26/2017 -- 11:51pm [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version Installed : Windows 10 Pro x64 [OSINF] Edition {Registry} : Professional [OSINF] Edition {WMIC} : Professional [OSINF] Build Information : 16299.0.amd64fre.rs3_release.170922-1354 [OSINF] Update Build Revision : 0 {Baseline Release} [OSINF] Edition Language/Code : en-US / 1033 {409h} [OSINF] Locale : en-US [OSINF] Language Name Value : ENU [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 : [INTEL] [MBINF] ======================= [CMINF] ======================= [CMINF] CPU/Memory Information [CMINF] ======================= [CMINF] CPU Name/Type : [Intel{R} Core{TM} i7-3770 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 : [4095 Mb] [CMINF] Available Memory : [3600 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Pro'. [CKDMI] Querying BIOS for manufacturer branding information. [VMDMI] A standard VMware VM detected with no valid SLIC or MSDM present. [THMOK] VMware [#VMware] 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] VMware theme has been applied. [BSHCS] Branding script has completed. [ADMAN] Add-On Manager: Started. [CMSDM] Querying BIOS for any MSDM data. [CMSDM] No MSDM Table/Key detected in BIOS. [USRAC] Windows 10 Enhanced Log-On screen has been enabled. [W10TB] Windows 10 'Grey' Title Bar 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 completed. [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 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. = = = = A Log/Sign out will be required to set the Title Bar/Taskbar colors etc. = ========================================================================================= The Multi-OEM/Retail Project has completed.
[OSUED] Cloud - Unsupported Edition, MRP will still attempt branding. Ooh looks like will have to alter a flag for Cloud Edition lol I gather that is using the Manufacture Mode ?
Yes, the info @Tito provided worked, now we have to set Manufacture mode to OFF automatically, after MRP ran. Used reg key: Code: reg add HKLM\Windows10S\ControlSet001\Control\CI\Policy /v ManufacturingMode /t REG_DWORD /d 1
I guess no one noticed i had uploaded Query Tool v28.0 this morning. Uploaded it and updated the first post with new password and forgot to post about it! A few bits done to the QT, listed in the changelog. Have shaved off a few more seconds in processing time due to a compaction of one the databases. Also a 3 pronged test to check a valid or invalid MSDM table. Thanks to Alphawaves for the latest tweak to the tools used. Hopefully all bases covered on that area now.