You still working hard at it mxman2k. lol Good to see you still got the project going. I will have to check out your next release. I haven't been online in months because of moving and health issues but I'm doing better now. As always, I wish you the best with this project.
Sometimes it can get stressful when a small change can affect so many other aspects and you are left puzzled why. Challenging to say the least More now as m$ seem to be tweaking the theme side as a few elements no longer work in newer builds and adjustments are required to compensate. Well i best get back to work, tea breaks are over so quick. Good to see you are ok, stay safe and well.
Regarding the non copying reg entries in NTUser.Dat - the funny thing is the majority of the processed options are actually present, so the MRP inserting part is working OK, it must be m$ just ignoring a few at this time as i cannot see anything changed in the code that has been in MRP for many months now.. The routine at the moment now also creates a small cmd script that is called via 'Runonce' entry when a new user is created and as the name says it is run once, you may see a cmd window appear with information on the copy processing of the options that was not being copied via NTUser.dat - a small work around but the Details view and most theme elements are now working again - until the next m$ OEM change! Obviously if you are not using the copy to new user option then that script is not used later on. It may be possible that defender will remove the temporary script, the only draw back then is the script won't be called/run on any new user created. I may add a defender exclusion for the file - however defender can still be awkward and flag anything it not like. Other than that MRP 131 is on schedule for a early November release
good night! Is it possible to run the project manually? For example, I installed Windows on a computer and later, the motherboard was changed (brand). Is there how to run the project manually to update the customizations?
Here is the manual registry info for changing the OEM info (system page), i've used this ages ago, maybe it's not working this way anymore. Code: reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\OEMInformation" /v Manufacturer /t REG_SZ /f /d "Manufacturer" reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\OEMInformation" /v Model /t REG_SZ /f /d "OS Edition" reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\OEMInformation" /v SupportURL /t REG_SZ /f /d "Support URL" reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\OEMInformation" /v Logo /t REG_SZ /f /d "%systemdrive%\Windows\OEM.BMP" The red marked txt you can modify.
I am working on the MRP OEM {Online} Branding program at the moment, a few glitches i have to iron out before i even think of presenting a test link to it
Here is a preliminary sneak peak of the OEM Branding GUI. Way too early for a alpha release as it is still in the design stages. Some parts work such as the showing and choosing the OEM Logo, also the Manufacture Name, Model Name and the Support parts are read from the registry (if not available they will be blank). Choosing the 'Wallpaper' button or any 'Applying' of info etc does not work at this time. There is no error checking at this stage so a large logo will probably crash the GUI. It has taken me months to get to this design, basic yes, however the end user will have to do some work themselves, such as entering any data they want, choosing the Logo/Wallpaper etc, as this is not going to be a auto set and forget like how MRP works as that would take ages to perfect and covert to a GUI. <-- Click for larger image. Lots of things will change before a public release is made, this gives you a rough idea of the concept. Obviously there are other better solutions out there and it is all user choice to what they wish to use.
it still works, also the keys - SupportHours - SupportPhone Also the path to the logo can be chosen freely. Tested Windows 7 and 10, x64, several editions. "OEM Configurator.exe" (OEM Configurator 2.0 in OEM-Configurator.zip from AskVG.com) works pretty too. Pitty that this version lost the function "remove OEM Information and logo" from version 1. "OEM Configurer.exe" (OEM Configurer in OEM-Configurer.zip from AskVG.com) didn't work. It seams, that is the version 1 of the tool OEM Configurator.exe (name has changed too) and did not support x64-OS.