Multi-OEM/Retail Project {MRP} - Mk3

@BALTAGY, on that Vm could you type that REG Query line in a admin cmd prompt, you should get :

ERROR: The system was unable to find the specified registry key or value.

But if you get some results then VMware/Vbox must emulate s/boot somehow even if using non EFI mode, as on my W10 PC i'am using , (MBR/Legacy, EFI off and s/boot disabled) i get the error line above.

Many thanks.

What makes it even more odd is the QTool uses the same check!!

 

Thanks for testing BALTAGY.

Hmm very strange!, well as the s/boot bit is only for info purposes i will remove that check and log entry about it on next build, it not needed for anything. The important bit is GPT/MBR as that can be used for future MRP versions.

It seems during setup/oobe stage Windows must put that reg entry in as default then if secure boot is not available it removes it later, which is after MRP has ran its course, hence the false report. I can only assume that is what is happening, as it not needed for MRP itself i will take that bit of code out for the next version.

So folks for now if you know you don't have secure-boot enabled and it reports it is on. Ignore it.

 

Silent Update to MRP.

MRP Silent Update.

Have now removed the Secure Boot detection as it not required for MRP function, plus it caused some weird results!

Also added a bit more debug information if you enable that 'feature'.

Link updated.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Agree it no longer looks out of place with that symbol.

Seems about complete for beta stage.

Just doing a final install check to make sure the VirtualBox bit is correct, plus the oversight of checking for the drive label flag but then not saying anything, well it actually did, i just forgot to pipe the output to the log, duh!

Already compiled the baseline release. I'm confident everything is in place and worded properly. Famous last words lol.

Example W10 log output:

Spoiler

Code:

Multi-OEM/Retail Project Version : 170108-R50s-BaseLine  [MRP/MDL] 
 
Files present and extracted successfully. 
 
Enhanced Debug Mode: Activated. 
 
> Detecting if a Solid State Drive is present. 
> Checking OEM's Folder Structure.
OEM's folder detected, structure appears OK. 
 
OS Installation Date: 08/01/2017 
 
19:22:17.15 > Checking installed OS name. 
19:22:17.16 Windows 10 Pro x64 version found. 
19:22:17.18 > Checking installed OS Edition/SKU. 
19:22:17.63 Professional Edition/SKU installed. 
19:22:17.63 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 
 
DMI BIOS Information 
#1 CS Product Name   : [VirtualBox] 
#2 CS Model          : [VirtualBox] 
#4 CS Vendor         : [innotek GmbH] 
#5 CS System Manf    : [innotek GmbH] 
#6 Baseboard Manf    : [Oracle Corporation] 
#8 BIOS ID           : [VBOX] 
 
19:22:25.64 > Checking 'Drive Name' LblDrv flag. 
19:22:25.84 'LblDrv' flag was enabled, 'C:' will be renamed to 'Windows_10_Pro'. 
19:22:25.84 > Checking DMI for manufacture information. 
19:22:26.32 Defined VBOX [VirtualBox] manufacture found. 
19:22:26.32 VBOX [VirtualBox] manufacture will be used for theme/branding. 
19:22:26.32 > Checking BIOS for MSDM Key. 
19:22:28.45 No MSDM key detected in BIOS. 
19:22:28.45 > Branding Section Part 1. 
19:22:28.46 Force theme text file not present. 
19:22:29.14 > Checking BIOS for System Product Name. 
19:22:29.38 System Product Name, not detected. 
19:22:29.38 > Branding Section Part 2. 
19:22:29.38 Desktop backgrounds folder created. 
19:22:29.45 > Windows 8.x/10/Server 2016 User Account Section 1. 
19:22:29.45 OOBE.xml file deleted.  
19:22:29.46 User.bmp replaced.  
19:22:29.67 User.png replaced.  
19:22:29.74 User-40.png replaced.  
19:22:29.81 > Windows 10/Server 2016 Account/Background Picture Section 2. 
19:22:29.81 User-32.png replaced.  
19:22:29.82 User-48.png replaced.  
19:22:29.84 User-192.png replaced. 
19:22:29.85 {Background} img105.jpg replaced. 
19:22:30.20 > Theme Management Section. 
19:22:30.20 Resources aero.theme has been replaced. 
19:22:30.40 {Background} img100.jpg replaced. 
19:22:30.45 > Transfer Theme Files Section. 
19:22:30.46 System32\oobe\Info folder has been created. 
19:22:30.48 Required theme files transferred to System32\oobe\Info folder. 
19:22:30.48 > Deletion of obsolete files. 
19:22:30.73 MRP Branding script has completed.
19:28:03.73 > MRP Add-On Module in progress. 
19:28:04.60 > Checking if device is a 'default' Virtual Machine. 
19:28:04.62 > Detected: 'default' VirtualBox VM. 
19:28:05.18 Advanced Log-On screen has been enabled.
19:28:06.01 User Account Pictures registry entry applied. 
19:28:06.04 'Registered Owner' registry entry corrected. 
19:28:06.05 Detected 'defaultuser0', attempting to remove the folder... 
19:28:06.18 Removal of 'defaultuser0' folder successful. 
19:28:06.35 > Checking BIOS mode if Legacy/UEFI and drive type is MBR/GPT. 
19:28:22.29 BIOS Mode: UEFI, Partition Type: GPT 
19:28:22.29 > Checking Online Status. 
19:28:22.30 Device not connected to the Internet, online license check failed. 
19:28:27.13 > Checking if Device is activated/licensed. 
19:28:33.04 License Status: Not licensed. 
19:28:41.22 > Checking if 'UserTweaks.cmd' present. 
19:28:41.24 'UserTweaks.cmd' present, attempting to apply. 
19:28:41.57 UserTweaks.cmd has completed. 
 
============================================================================  
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 DeBug Mode deactivated.  
 
Thank you for using the project, MRP has now completed.

 

MRP Updated! (170108-R50s-BaseLine)

MRP has been updated, download link updated.

See Change Log for details.

 

@The_Guardian, hopefully it will all work ok with your recovery system.

Not tried it with any recovery software myself.

If it a Compaq/HP there 'may' still be a possible glitch with the DMI reading. Not had any reports of anything wrong since i added the tweaked conflict section. You know the problems that manufacturer has caused!

The latest QT has the 'tweak' added so if that shows the correct theme/info, it should technically be same with the main project.

 

I can understand some people not coming forward, i'm a relatively 'unknown' person, taking over an established project from two respected members of MDL.

I wish to express to everyone that the main core of the project is exactly the same as it always was, yes there are a few tweaks here and there. Nothing is radically changed.

The add-on module was created to make it easier to add things without upsetting the main core script. Server side branding would not of happened as swiftly without that module.

UserTweaks.cmd was created to allow end users more flexibility with their own requirements.

Without Mr.X, apologized and Baltagy's help with hours of testing, most of what has happened would still be in beta stages that help i'am really grateful of.

Also with major thanks to The_Guardian, who without having permission off of to continue this project, it would probably be extinct by now, I hope i have not let him down with the changes.

 

To find the download area on the first page click the spoiler: [Show] button under Download: this will take you to the ********* link where as mentioned you need to prove you are a human. Then you will see the links to use to obtain the required files. Make a note of the password or you wont be able to extract them.

OOBE mode means the project itself will only work while in Windows Setup mode. The 'how to' section will give information on how to add the $oem$ folder to the ISO/USB stick if using that method to install windows from.

All files required to make the project run for branding/activating, if possible, a computer during Setup are within the $oem$ folder which is within the compressed MRP's .7z file.

The 'possible' bit is if the PC has SLIC (Vista/7) or MSDM W8.x/10 available to activate, its all handled by MRP, the project.log found on the drive the OS installed on (C: usually) will detail any problems with activating, such as no SLIC found either within the bios, or not within the MRP database, for w8.x/10 if no MSDM key found in the bios.

The QTool is to be ran on a computer to see if the project will brand it properly, it does not brand anything itself just gives a report on what it finds. If the Summary section of the report has #x and the right brand name found (hopefully - unless your computer has some odd DMI information!), also a #x next to activation (mainly for win vista/7 SLIC's), then you should be ok. Use the QT first if possible on the PC you wish to use MRP on and if you are unsure please post the report.txt file that can be saved at the end of the QTool's execution.