MRP v66.0E has been uploaded. First post updated with new password. No need to see the change-log as most of the progress has been shown in previous posts. Updated Credits to include @mad_max for informing me of this potential bug. Now i think it time for a beer!
I'm glad to hear that and thank you for really good piece of software. Now it's working nice and smooth even on my pretty old mobo.
Thank you for notifying me about it, never thought it could be a critical bug! I know it is a rare occurrence but as shown some OEM's may have a dummy table added, it also could happen if someone has a bios mod done to add a SLIC and it corrupts the MSDM table. Its now 'patched' and the code checks are in place for a better solution later.
I made bootable usb with Win 7 SP1 Ultimate and I plugged $oem$ folder. However, the installation fits when "setup is preparing your computer for first use" and I have to shut down the laptop because it is not going. On another bootable usb stick I do not have $oem$ folder and the installation goes smoothly. Sorry, I do not speak English.
Strange not had a problem with staying on that screen. No one has reported it 'hanging' at that point. I do know it can take a while at that screen sometimes. MRP has completed at that stage of setup as oobe stage has finished and the OS's setup has entered the finalization process (Image_State_Complete for a technical term).
It not matter VM or Real PC, the OS's setup still runs the same way. Has the OS been 'edited' with nlite/toolkit? Is there a setupcomplete.cmd to run something? Do you use a unattend.xml file to do other 'tweaks' to the setup? These can affect how MRP works but usually it will carry on and note things in the log file. Plus as i mentioned the MRP has completed at that stage of setup because oobe/Specialize states have been done, the OS is now in the final stage. I do not think it a project fault as no one else has mentioned it before, even my beta testers who used Win7 for our tests have said anything about it 'sticking' at any point.
I only experienced some problems with my old win 7 setupcomplete.cmd with the exit commandline at the end, but the project didn't halt the windows install.
OK. I've done 8 clean installations today and my eyes are dying .. No installation with a new project has passed but with the old project they've been through. With installations of @Generation2 I have never had problems. Your project is following and using since you started and I never had a problem with this last one..But since I'm weak English here I will stop my discussion. Thank you for your time.
I think the key information there was Gen2 ! If it the AIO Win7 iso they do then with the pre-activators they put into it then i can see why there may be a problem. It is a conflict of some sort.
Code: Multi-OEM/Retail Project Version : 170919-R66.0E - BaseLine [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: Thu 09/21/2017 -- 3:04pm [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version Installed : Windows 10 Home Single Language x86 [OSINF] Edition {Registry} : CoreSingleLanguage [OSINF] Edition {WMIC} : CoreSingleLanguage [OSINF] Build Information : 16294.1.x86fre.rs3_release.170916-2023 [OSINF] Update Build Revision : 1 [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 : [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} i7-3770 CPU @ 3.40GHz] [CMINF] CPU Description : [x64 Family 6 Model 58 Stepping 9] [CMINF] CPU Architecture : [32/64 Bit Instruction Set] [CMINF] CPU Cores/Threads : [2] / [2] [CMINF] Total Physical Memory : [2895 Mb] [CMINF] Available Memory : [2492 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Core-SL'. [CKDMI] Querying BIOS for manufacturer branding information. [VMWSD] Default DMI 'VMware' with a Dell [#08] SLIC detected. [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 : 'CoreSingleLanguage' [CMSDM] -> {MSDM} KeyEditionID : 'Professional' [CMSDM] -> {MSDM} ChannelID : 'MSDM' [CMSDM] Key Detection Routine Used : 1 [CMSDM] MSDM Key Information: Win 8 Professional [CMSDM] The detected MSDM Key cannot be used for the Edition installed, saved only. [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: Licensed [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 maybe required to set the Title Bar colors etc. = ================================================================================ The Multi-OEM/Retail Project has completed. HWID activation
I originally had that line, but changed it as at the time of testing i wasn't sure of what colors would be used. It does show the color used later in the log because i read the saved environmental variable created during MRP. Will change it for next release.