==================

= MRP Change Log =

==================

Version Numbering: XX.YY[.ZZ]

XX Major, YY Minor, [ZZ Test Revision]

27th July 2017 61.0

===================

New look to the Project.log!

The OS and DMI/BIOS information now is displayed in a more structured format.

Re-worded some output lines which should make things a bit more easier to
understand. Even
though the log is designed to help me find any problems, I wanted to make it more
user friendly
in that it shows clearer progress of what MRP was doing during the installation
process and not
be all technical jargon.

Adjusted some error checking areas.

Quite a bit of re-writing to the branding/theme script has been done, this is what
takes the
time to get things ready for a release. If this script is altered in any way then
testing takes
a lot longer due to its complex/sensitive structure.

DeCompile has been tweaked as well, more checks added to make sure that MRP will
function
unless something happens it is not happy about.

If certain criteria is not met then as mentioned in another log entry below that
the project
will still run but in Reduced Function Mode (RFM). In this mode certain sections
may be
skipped, such as MSDM table checking, so for Win 8.x/10 your key will not be auto-
inserted
or even checked.

This only happens if you have removed .Net framework 4.x, why you would want to do
that is
not open for debate. Likewise for Vista/7 if .Net v2.x is removed certain sections
will also
be skipped, but branding and activation should still take place providing there is
any valid
DMI/SLIC information present.

Force_Theme routine has been revamped and with better error checking/parsing, it
may not be 100%
foolproof, so check your spelling of the brand name if you use this feature!

Due to the changes in the Force_Theme section you will need to use the latest
OEM's.7z file which is
provided within the main MRP archive. See Optional folder ->
Force_Theme_[readme].txt for more details
on which brands are affected, not all brands are, only a select few that did not
meet the new checking
routine was altered.

As a lot of work been done behind the scenes the version been bumped up instead of
a being a minor
60.1 version.

===================================================================================
==================
10th July 2017 60.0
===================

Added Cloud S detection although MRP cannot run on Win 10 Cloud S as it not a Store
App. But it will
detect the MSDM table of it if present now.

Re-Worded a few log entries hopefully looks clearer to what part does what.

Added new error checking routine for when/if Windows Setup crashes out in the OOBE
stage such as if a
network card is not present or something, MRP will carry on but will put a note
that an 'unexpected
reboot' has occurred and that the branding may of failed in some way.

Added new Alienware wallpaper(s) - thanks twiztidwolf. :)

Adjusted all wallpaper.jpg's to comply with the 256kb limit as some was a few bytes
over and could
cause problems with Vista/7 and the servers that are based on those OS's. So now
all wallpapers are
below 254kb to be sure. Asus was one that was a 4 bytes over and on a VM was ok,
yet on a real PC it
could cause a little problem.

Other code tweaks was done during the above changes nothing major just a few speed
up tweaks and
re-adjustment of a couple of error checking routines.

===================================================================================
==================
02nd July 2017 59.3
===================

Just a interm update, tweaked the Secure Boot detection (if your computer has
this enabled). May not be 100% accurate due to some changes in the way that
Microsoft has adjusted the 'keys' on some newer BIOS's - probably due to the
leaked master golden keys?

Fixed a few spelling mistakes, some you would not see unless you are using a
Virtual Machine with GPT in use.

There are a few re-wording and changes in some text, nothing major.

Added ASI Branding/Certificate(s) and SLP Key.

Asus, Gigabyte has had new wallpapers, higher quality less grainy look.

Added a note that on Vista/7 if the backgrounddefault.jpg is larger than 256kb

then it can cause Windows to either ignore it and use a default background or
give you a black background. This is a limitation for those older OS's, for
W8.x/10 this restriction does not seem present. However it may be wise to keep
to the 256kb limit for all OS's to be compatible and less errors.

If you use your own backgrounddefault.jpg (it must be within a folder called
Backgrounds within the brand folder), MRP will ignore automatically creating one
from the Wallpaper.jpg.
===================================================================================
==================

20th June 2017 59.2

===================

Few tweaks done, rewording here and there.

Enhanced checking done for .Net requirements if for some reason the .Net that is
required for MRP to fully function is not present then MRP will go into RFM (
reduced function mode), basically MSDM checking will not be done and a few other
little items that require .Net to be installed. This will only affect those that
use methods to remove certain parts from Windows via DISM or other tools and you
remove the .net feature(s). Mainly W8.x/10 but it can affect Vista/7 if a MSDM
table is present then it cannot be used for branding if DMI/SLIC branding fails.

Added enhanced error checking to most areas to prevent MRP from malfunctioning
due to a problem within the User Account Picture section when Windows 8.x/10
and Server 2012/2016 is installed. Was not a fault of MRP but how windows can
assign certain USERID (SIDs) it could cause a potential boot loop. Have added
new checks that will bypass that section if the 'bug' appears. Other branding
will still be OK.

Enhanced DefaultUser0 removal is now added, it has 3 stages, if one fails MRP
will try another method until it has been removed cleanly, failing the 3rd
attempt then you will have to remove the folder/account manually. Very Rare!

Other non important bits done too, just basic tidying up of some code areas.

===================================================================================
==================
12th June 2017 59.0
===================

Fixed a glitch that on certain brands the branding script could crash only
on Vista/7. Due to a error in a error checking routine of all things!

Few other tweaks done under the 'hood' slight rewording here and there etc.

Changed Fujitsu/FSC wallpapers from the grainy versions to a Hi-Res one.

Also DELL wallpaper(s) also been changed to Higher Res ones.

Gigabyte wallpaper(s) are now almost 4K res.

How the Theme (branding process now works):

1) Checks DMI for any manufacturer information.

2) Checks SLIC name and use that if no valid DMI info.

3) Checks MSDM table (even in Vista/7 now), for brand name. Use that if no valid
DMI or SLIC found.
Obviously the MSDM table is NOT used under Vista/7 MRP just obtains the brand
name from it.

4) Use Windows Default wallpaper/logos if none of the above can be used.

===================================================================================
==================
05th June 2016 58.1
===================

Just a tweak or two to fix Server 2012 (W7 kernel - ie NOT R2) OEM activation
routine,
it now works as intended.

Note: sometimes on Server's the Edition (WMIC) may say "Server (R)," but that does
not
affect MRP's function as it only a cosmetic thing that sometimes is ok others it
don't
display the name right.

Also re-worded a few bits to make more sense. Fixed missing batch error message
that
would sometimes appear.

===================================================================================
==================
04th June 2017 58.0
===================

Another milestone reached!

Now where to begin...

Ok, Branding is a lot more enhanced, using a new method to obtain the SLIC and now
MSDM brand name if they are present, if no DMI information it will use either the
SLIC or MSDM brand name to theme your computer. Failing all those you will get the
default windows theme. You can use the forced theme method to bypass if required
as
normal. Thanks to s1ave77's help in fixing my scripts where i nearly got it right.

There are a few more things going on to make the above happen but not bore you with
those details.

Various tweaks to wording, new sections added, well original ones split into new
ones.

Will now detect BIOS/Boot mode UEFI and GPT partition format for the system drive
better.
Still no Secureboot detection for Virtual Machines apart from maybe Microsoft's
Hyper-V.

For VMWare/VirtualBox you will see a note about not able to obtain Secureboot
information.

Servers: Now covers 2008, 2008R2 and 2012 for OEM SLP activation via a valid SLIC!
This
part took the longest to make work, if it fails blame s1ave77 as it was his idea to
add
this feature.

Now this part has been tested on Server 2008 R2 (personally) and it works perfectly
with
branding and activation! Server 2012 was tested by you guessed it, s1ave77 that OS
is
also working.

Vista based Server 2008, not been tested as it no longer supported by Microsoft(tm)
as far
as i know. So branding errors may occur on this one and you may have to turn on
certain
features manually then the theme should work, background picture may fail but not
going to
spend time sorting a unsupported OS - sorry. Valid OEM SLIC activation should work
though
so a bit of a bonus!

Other tweaks done not going to bore you, but a few speedup things and a partial re-
write of
most of the scripts to accomodate the new changes.

===================================================================================
==================
26th May 2017 57.0
==================

Some cosmetic changes to wording and log text output.

Added a check for Wallpaper.jpg you will see a note appear in the log if the file
size
is greater than 256kb. This only affects Vista/Windows 7 and Servers that use
those
Kernels, (6.0/6.1). Windows 8.x and Windows 10 are not affected.

If you use a Wallpaper.jpg file of your own and the size of the file is bigger than

256kb on Vista/7, Windows will ignore the file totally and use its own default
Wallpaper as the file size restriction is hard coded within a system file to be no
more
than 256kb. This is NOT a fault/bug of MRP it is how Windows was written at the
time.

The file size restriction seems to have been removed for Windows 8.x/10. For best
results
try to keep the file sizes below 2mb or your desktop may be slow to appear due to
the way
Windows processes the image(s).

The Wallpaper.jpg file size check code was written by s1ave77 as my original
attempt worked but
only some of the time. Thanks s1ave77, saved my sanity yet again!

Fixed a tiny bug with the AM/PM indicator, this also affected the Query Tool which
will be updated
along side MRP.

Also checked all Brand OEM's to make sure they are within the 256kb limit for the
Wallpaper.jpg file.
===================================================================================
==================
08th May 2017 56.0
==================

New method added to obtain the correct Edition name (Thanks S1ave77).

DeCompile.exe has had a few tweaks, nothing major just some that will help detect
certain
situations. Like OS pre-checks, if a Virtual Machine is being used with edited
bios/DMI.

Re-wording of some log output lines.

Fixed a glitch with Vista that also affected Windows 7 on the OS Name/Edition, I
know the OS
no longer supported but as Vista and 7 use mostly the same coding the adjustment
works for both.

OS Installation Date/Time: Should display the time in your localized time format.

Tweaked a couple of the error checking routines that slightly slowed down progress.

Version Bump to v56.0 as quite a bit of internal work been done.

DELL Brand folder within OEM's.7z, Wallpaper.jpg is the original DELL wallpaper,
wallpaper1.jpg is
the old wallpaper with the new DELL Technologies logo in the middle. You can
change to the new
one simply by deleting/renaming wallpaper.jpg and renaming wallpaper1.jpg to
wallpaper.jpg.

===================================================================================
==================
30th April 2017
===============

CompositionEditionID added if available will show. Usually the same as Edition but
on
some certain Windows 10 Editions this may have a different name. Pro-Edu is one
that
changes Edition name between Setup and the first reboot after oobe stage.

Changed NoMSDM flag to 0 to allow insider editions to activate normally via MSDM if

present and a match for the installed Edition.

If via WMIC call the IDE Controller for IDE/AHCI is unable to define the mode it
will
now mention that a possible customized chipset may be the cause. (Code used from
Query Tool)

Some slight rewording of log output lines.

Added more error checking to some areas that could possibly of caused MRP to
malfunction.

Fixed the VC 2012 DLL's uninstalled line in the log output (shown only if enhanced
mode activated).

Added extra checks in the MSDM section which sometimes caused an error and the
script failed.
Rare but made sure it no longer can cause this error. Hopefully!

Little tweaks here and there to keep things running smoothly.

Added a line space between when the Branding script finishes and the Add-On Manager
starts.

Added a 'Note:' message line if the Edition changes between Branding and Add-On
Manager, for example
Professional Education to Professional.

Added new Dell Technologies wallpaper, (others within the Dell brand if you not
like the default one),
also updated the logo's and User Account Picture.

===================================================================================
==================

21st April 2017

===============

Fixed a few little gremlins, they didn't affect the working of the project just put
the wrong
information line in the log that was designed for when Enhanced mode was active.

Also fixed a possible glitch that if a certain Edition is installed that does not
use a MSDM key
such as Server/Enterprise it may of inserted the MSDM key if it was present by
mistake which could
cause a change of Edition ie Enterpise to Professional.

Removed some duplicated test code that was there for a while and not required
anymore.

When checking if the computer is licensed, or not, it will now say what state it is
in at the time of
when MRP was ran.

For example you may see one of the following:

Licensed: You see this status after a successful activation.

Unlicensed/Not Licensed: This appears for unlicensed/not activated copies. For

Window 8.x/10 this
is normal if you are not connected online during the setup process, once connected
and your computer
has established a connection if your Retail/MAK Key/MSDM or HWID, (for the Edition
installed), is
correct it should then activate.

** Initial (Grace Period): This is the state after you have installed Windows, but
have not activated
it. You will be reminded to activate, or Windows will attempt to activate it online
automatically.
** Additional (Grace Period): If major hardware changes are made to your computer,
Windows may prompt
you to reactivate Windows.

** Notification: Once the grace period expires, you will see a message that
Activation is required.

** Non-Genuine (Grace Period): You may see this after Windows Genuine Advantage has
determined that
your Windows copy is not genuine.

Those marked with ** are usually seen for Windows Vista, Windows 7 and some Server
Editions based
on those Kernels. It is possible they can be displayed on later OS's too.

Notification can also be displayed on Windows 8.x/10 when no online connection is

present and Windows
cannot obtain either a HWID or check against the MSDM key (if present).
===================================================================================
==================

16th April 2017

===============

Fixed a problem with ProfessionalEducation that was being identified as

Professional - This only
occured when checking for a MSDM key and not affected other operations of MRP.

This new code change can be adapted for other Editions that change mid way though
installation but
for now a standard simple tweak has been used. A more advanced check will be added
later if other
Editions have this identity change!

For Windows 10 ONLY: Build Revision will now show if any updates have been
installed that alter the UBR
(Update Build Revision), number.

Added DEBUG information for MSDM key parsing, this will ONLY appear if you have
DeBug=1 set inside the
OOBE.cmd to allow advanced log entries. Useful when finding problems! Optional of
course, but for bug
reports that are posted in the main thread it would be nice to have the enhanced
log enabled so that it
is possible to find what went wrong for you. The standard log has enough
information anyway, but the
extra log information can help me sort things quicker.

A few other code tweaks in all the MRP script sections, including add-ons.

Redundant code no longer used has been removed.

Fixed the odd spelling and/or wording on some sections as the odd extra space or
full stop appeared etc.

===================================================================================
==================

7th April 2017

==============

A few changes to the text output within the Project.log file.

Removed or altered some of the enhanced debug mode text output.

Tidied up a few of the Add-On modules that had redundant code.

New checks for RS2 in place ready for any changes that may happen that may
require patches to be made for either a certain Version or Edition.

If DeCompile.exe detects any problems it will create a special Add-On to try

and compensate. This will only happen in some cases, possible triggers are any
integrated updates or WIM modifications that could cause MRP to malfunction.
Some All-In-One compilations may also trigger the Add-On Module 2. You may
see a success/failure message in the Project.log if the add-on 2.1x is created
and processed. The Addon just contains a few tricks and tweaks to hopefully
give a successul MRP installation, it does NOT affect any system files ONLY
MRP related internal code/files that the Project uses.

===================================================================================
==================
== End Of Log ==