Multi-OEM/Retail Project {MRP} - Mk3

@Klomar, I can add that reg entry into the project with checks to make sure it is not 'run' for anything other than W10 , the current defaultuser0 removal subroutine will still run but if the files are already gone it will ignore that anyway, the RegOwner (Winver issue) fix is done prior to the removal process. Hopefully a win-win .

@all
I'am beta testing an updated project at the moment making sure the User810.png side is fully operational along with some other streamlining of the code. Taking some time due to testing various Vista/7/8.x/10 /editions/32bit/64bit to make sure nothing 'breaks'. A few minutes editing the code, then hours upon hours of testing!

Just trying to keep the project fresh and keep the download links active as i have noticed some go 'offline'. May have to rename the project's 7z filename to something like MRP_[date].7z to slow down the link removals...

 

You need to login to view this posts content.

 

Re: OEM's.7z

That's what i have done, if things change in the future then it can be updated as and when the project is ready to use png or the current bmp format for the USER810 file .

 

Project Updated

First post download link/changelog updated.

Have renamed the 7z file to MRP_DD-Month-Year.7z format to hopefully keep download links active for longer.

Time for a break

 

Will be changing download system shortly (just in process of uploading everything and processing the links etc) .

I was just continuing the way it was done before, sorry about that folks.

 

Ok think it all sorted now... using the ********* link.

You may get challenged if your a human captcha, once confirmed you are a real person, the links etc will be shown, took a while to re-upload, re-hash check the files more so as my ISP is slooow tonight on uploading.

Have only done a couple of download links and hopefully a lot less pop ups etc, if it worse, blame Mr.X for the suggestion

 

@all

To clarify some newer updates (or features added within those updates for W10), may cause the project to malfunction, it not happen all the time just the odd occasion.

It may be caused by some of the updates that are pending, ie those that are integrated but are not done until the OS has installed, it could overwrite some settings that the project uses to do the branding etc.

The project will still work, (as a fail-safe system is in place), it's just for information if something goes strange. The Project.log file will list anything failed and if this is posted in the thread or via PM, (remove any MSDM/Retail keys first please), I can hopefully see where something can be tweaked that does not break something else.

As all my testing is done with baseline ISO's it is impossible to keep a check that any new updates integrated change any OS settings that was previously working with the project.

 

Project Updated!

Project Updated! All links now live.

See change log for more details.

A BIG thanks to Mr.X for helping test this latest update.

 

@MMIKEE Oops Knew i had missed something, the QT itself has been updated i forgot to update the Version string. Thank you for letting me know, i will do a silent update shortly with the corrected version number.

Edit: Have redone the links. QT string corrected in MRP and its own 7z.

 

Slight update to project - found a small glitch that will mainly affect any Vista users. Plus a few code tweaks to help shave off a few seconds of installation time.

Have removed the Query Tool from the project's archive, this will make any changes to the QT in the future easier to maintain its own download link as there will be no need to redo the main project archive as well, saving a bit of time doing re-archiving/hashing etc.

Also tidied up the first post to make it look neater

 

There will be a minor update to the MRP shortly...

It may be a day or so time i get to upload it as at the moment my internet is intermittent, hopefully sometime tomorrow my ISP will have sorted the problem out in my area.

The project log output has had a little tidy up as can be seen below. Your date format will depend on your location.

Spoiler

Code:

Multi-OEM/Retail Project Version : 161118-r26f [MRP/MDL] 
Project files present and extracted successfully. 
OEM's folder detected. 
OEM's folder structure is OK. 
 
OS Installation Date: 18/11/2016 
 
13:53:32.73 Defined Windows 10 Home Single Language x64 version found. 
13:53:33.01 Defined CoreSingleLanguage edition found. 
13:53:40.91 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 
13:53:41.33 Defined HP manufacture found for theme branding. 
13:53:43.89 No OEM-DM key detected. 
13:53:43.91 Force theme text file not present. 
13:53:44.82 System product not defined. 
13:53:44.82 Backgrounds folder created successfully. 
13:53:52.15 Deletion of OOBE.xml file successful.  
13:53:52.17 User.bmp backed-up and replaced successfully.  
13:53:52.63 User.png backed-up and replaced successfully.  
13:53:52.70 User-40.png backed-up and replaced successfully.  
13:53:53.46 User-32.png backed-up and replaced successfully.  
13:53:53.46 User-48.png backed-up and replaced successfully.  
13:53:53.56 User-192.png backed-up and replaced successfully. 
13:53:53.59 Img105.jpg backed-up and replaced successfully. 
13:53:53.95 Theme backed-up and replaced successfully. 
13:53:54.07 Img100.jpg backed-up and replaced successfully. 
13:54:02.12 Advanced logon screen for Windows 10 enabled successfully.
13:54:02.14 Info folder created successfully. 
13:54:02.34 Files moved to System32\oobe\Info folder successfully. 
13:54:11.15 Cleanup reg entry added successfully.
13:54:11.15 Installation script has completed successfully.
13:59:45.28 Windows 10 login user picture reg entry successfully applied. 
13:59:45.33 Found defaultuser0, attempting to remove folder and fix reg entry. 
13:59:45.67 Removal of defaultuser0 folder successful. 
13:59:45.88 BIOS Mode: Legacy, Partition Type: MBR. 
13:59:45.88 Device not connected to the Internet, online activation failed. 
13:59:49.29 License Status: Error, not licensed. 
14:00:02.19 Cleanup script has completed successfully. 
14:00:02.19 UserTweaks.cmd present attempting to apply. 
14:00:02.19 UserTweaks.cmd completed. 
 
============================= Windows 10 Users =============================  
Please Note: It is advisable to logout or reboot your computer when possible  
             to allow the user/logon background pictures to finalize.         
============================================================================  

To keep this post tidy click below for news about the 'UserTweaks.cmd' shown in the Project.log file above.

Spoiler

A new add-on called 'UserTweaks.cmd' is now integrated - partially, meaning it will be available as a separate downloaded 7z file which when extracted the files within can be added to the $oem$\$$\Setup\Scripts folder if you require. Read the UserTweaks-ReadMe.txt first!

This is mainly for users who know how to edit a batch script, examples have been given to what the script expects to 'see' and work with. However I have tried to make it as easy to use, read the text file and more novice users should be able to get it to work.

This will allow you to put your own 'REG ADD' tweaks etc within the batch file or use standard .reg files. The readme file will give more details on how to set it up. Have added a subroutine to allow registry key ownership too. But be very careful on certain reg keys as you can really upset the OS, what you take ownership of is at YOUR own risk!

The script is called just before the desktop appears so if you add programs to install etc this will cause a delay. Also as the script is run under SYSTEM control there may not be any text output, so avoid using echo commands or anything asking for user input as this may not be displayed and will cause the script to 'hang' as if the program added is asking for user input you might not be able to physically see what it is asking for you to do!

For installing programs it may be wise to use another method for installing those that require any user input.

The script was designed just for simple .reg files for which it performs as expected.

IMPORTANT:
Do NOT invoke a reboot within this script or unpredictable results may happen, if you need to reboot the computer please do so AFTER the desktop has appeared and the system is fully operational.

The UserTweaks.cmd add-on is entirely optional and is not needed for the project to function, hence why it is available as a separate download, if the project detects the file it will work on it, if it is not in the scripts folder it will ignore it and carry on.

 

Unless the site it on has modified something and re-hashed it but yes as long as the hash matches what is on MDL it good to go

Got my internet back to normal so going to upload the new MRP and usertweaks add-on


EDIT: New MRP uploaded along with the new add-on UserTweaks.7z.