UserTweaks.cmd - Add-on.
========================

Please read this help file completely.
--------------------------------------

There is a few things to get right to make this script work that only YOU can do.

Files to be copied: UserTweaks.cmd, the UserTweaksFiles folder.

Place these files into the $oem$\$$\Setup\Scripts folder along with the DeCompile.exe,
OOBE.cmd, [OEM's.7z if used]. Your Scripts folder should now look like this:

\$oem$\$$\Setup\Scripts\
			 DeCompile.exe
			 OOBE.cmd
			 OEM's.7z (if using the OEM branding)
			 MRPConfig.ini (if using any Options for MRP)
			 UserTweaks.cmd
			 UserTweaksFiles (the folder)
 
Also the '.reg' files for your OS version(s). ie W7LM.reg/W10CU.reg etc within the 
UserTweaksFiles folder.

You can use several '.reg' files as long as they are correctly named for the OS they are required
for within the Scripts folder because UserTweaks.cmd was written to only use the '.reg' files
that are for the installed OS. 

The example .reg files included don't do anything just examples.

Example: Windows7 installed, then the '.reg' files used will be W7CU.reg and W7LM.reg all 
other '.reg' files will be ignored.

To use registry (.reg) files you must use the following filenames:

For Windows 10:
 W10CU.reg for Current User entries.
 W10LM.reg for Local Machine entries.

For Windows 8:
 W8CU.reg for Current User entries.
 W8LM.reg for Local Machine entries.

For Windows 8.1:
 W81CU.reg for Current User entries.
 W81LM.reg for Local Machine entries. 

For Windows 7:
 W7CU.reg for Current User entries.
 W7LM.reg for Local Machine entries.

For Windows Vista:
 WVCU.reg for Current User entries.
 WVLM.reg for Local Machine entries.

For Windows 10 Preview specific:
 W10PCU.reg for Current User entries.
 W10PLM.reg for Local Machine entries.

I split the .reg files for Current User and Local Machine to make it easier
to add entries for those sections.  You could put all within one of the .reg
files if you so wish but wiser to keep CU and LM ones separate. 

Local Machine ones can have sections for HKUsers, HKClasses, they're ones for 
system wide usage. Having CU/LM .reg files makes it easier to look after and
debug if you have a entry that don't work.

You can also use REG ADD ... for your tweaks if required, just put them 
within the correct OS section within the UserTweaks.cmd file.

For registry permissions, if the SetACLxXX.exe file is present the script will
copy the correct OS bit version to your \Windows folder renamed as SetACL.exe to
make things easier for the script to work.

Using the CALL :RegOwn "registry path/key to gain ownership of" for example:

	CALL :RegOwn "HKLM\SOFTWARE\Microsoft\Internet Explorer"
	CALL :RegOwn "HKLM\SOFTWARE\Microsoft\Internet Explorer\Main"

This will set 'Administrator' ownership of the given registry key.

If using the :RegOwn subroutine, do them BEFORE the SET MRPHKCU/MRPHKLM lines or
your tweaks that require ownership will not take place.

A word of warning, do NOT go blindly taking ownership of registy keys or you
could end up having a non-working OS!

A registry hives to be VERY VERY careful with are HKEY_USERS and HKEY_CLASSES_ROOT
messing about with permissions within those hives can cause catastrophic failures
of the OS - YOU HAVE BEEN WARNED!

Any registry/other tweaks you add, or any modifications to the script is 
at YOUR OWN RISK, *NO* support will be given.

Simple SSD check is available, see within the script how to use.

The script is provided 'as-is' - it functions correctly *IF* you follow the 
instructions. Try to avoid using ECHO or anything that requires user input
such as installing programs. The reason being this script is run as SYSTEM and
any text output or user input required actions may NOT show anything on the 
screen and cause the system to appear 'hung'.  Use another method to install
any programs that require you to interact with it.  IF you know how to edit
the batch file it is possible to convert this script quite easy into a
standalone tweak/program adding system. If you have silent installing programs
you can use them with UserTweaks as long as none ask for any user input etc.

If you require a reboot for your tweaks to work, please do NOT invoke a reboot 
within the script.  Wait until the desktop appears and the OS is fully functional
then do a manual restart of the computer, failure to do this the OS may ignore 
your settings or in the case W10 the userpic/logon background may fail to work.

If you have any suggestions on how to improve the script or any errors within 
this textfile please contact via Private Message.  The script is a 'rough and 
ready' one that does the job, it's not perfect as little error control is added.

Credits:
========

SetACL by Helge Klein
Homepage:   http://helgeklein.com/
Copyright:  Helge Klein
License:    Freeware

Simple SSD Detection written and used within MRP by mxman2k