Multi-OEM/Retail Project {MRP} - Mk3

Discussion in 'MDL Projects and Applications' started by mxman2k, Oct 15, 2016.

  1. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Ok have found a work around, a bit long winded way but on my VM test it worked and not crashed the script! :)

    Just got to edit the main QT script and compile....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    #1362 mxman2k, Sep 18, 2017
    Last edited: Sep 19, 2017
    (OP)
    Link removed - Test 3 , OK

    Once this sorted then the MRP will need a bit of adjusting too!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    I guess you saw the "if the QT seems stuck here, press a key." message? it should appear only on win 7.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. mad_max

    mad_max MDL Junior Member

    Mar 31, 2014
    77
    40
    0
    That's right. In my home pc I don't have to press a key. Tomorrow I will see what will happen on my pc at work.
     
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Ok no worries. I wont make it QT v26.0 just yet until i know it has been fixed.

    Thanks for bringing it to my attention. Never realized that a dummy MSDM table could cause the glitch.

    MRP will have to be edited, but that a simple thing on that , just ignore looking for the MSDM table on any OS below Windows 8.0 like it used to.

    The routine in MRP was only to look for the name for branding if no DMI or SLIC was present. But as it may cause the project to crash it is best to bypass that section for now.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Have sent a PM/convo to Alphawaves to see if he can adjust the GenericX.exe code to give an invalid return or un-listed so it not cause this glitch to happen within MRP at oobe stage as you not see the error or know you have to press a key as all text output is not shown during that time.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mad_max

    mad_max MDL Junior Member

    Mar 31, 2014
    77
    40
    0
    Version 25.1 test3 working just fine. Stuck at "if the QT seems stuck here, press a key" and after that show me resaults:
     
  8. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    @mad_max thanks for letting me know :)

    Have made more progress in that have a better work-a-round (bit of a cheat really :p) to prevent any errors it also no longer pauses for a key press. :)

    Just need to do a test with MRP using the dummy table in a VM to see if it will work with that.

    As Alphawaves is busy with life outside of coding/MDL this will give him time have a look when he can.

    Meanwhile i can use my 'cheat' to at least prevent the QT from crashing.

    It is rare the invalid MSDM table will be present (unless a OEM such as Gigabyte ,or a self modded, BIOS has one), but it is nice to cover as many factors that could cause problems as possible.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Well have thrash tested my 'fix' for the invalid MSDM table detection, happy to announce it works!!

    It is still experimental for now so may glitch - however for non present table the check is ignored so a likely crash should not happen!

    Also while doing the tests there is a speed up tweak done too. :)

    If a MSDM table is detected, the check will show valid or invalid.

    There may be a slight pause while the checking of the table is done so no need to press any key now.. it will continue automatically.

    Just compiling the QT26.0 exe, update the changelog.txt, upload and will update first post with the new password etc. Be a few minutes... :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    QT26.0EBL (E = Experimental)
    First post updated with the Query Tool new password.

    See changelog.txt for details if you wish.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. MMIKEE

    MMIKEE MDL Senior Member

    Oct 6, 2012
    380
    361
    10
    upload_2017-9-19_7-57-20.png
    Works flawlessly on my ASUS Laptop w7 Pro-x64... :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    I see another Notepad++ user ;)

    Did the Valid MSDM table message appear after the .Net checks, it not matter if it not as the report shows the MSDM brand/edition info so it worked. :)

    I was mainly testing for Invalid table and only quickly looked when a valid one was present. :oops:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. MMIKEE

    MMIKEE MDL Senior Member

    Oct 6, 2012
    380
    361
    10
    Yes, the Valid MSDM table message appeared after the .Net checks... It seems Faaaaaaaaaaaaaaaster than previous versions... :D
    OBTW, I've been using Notepad++ for many years and it is my Text Editor of choice... It is so capable and easy to use...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    It's just a 'bit' faster ;) It could be even more if all the info screens was disabled. But left them active so people can see if there is a glitch or one of the error checks kick in.

    I have used Notepad++ with the project since last December as it helps detects some of my missing brackets lol, not always find them as i must confuse it at times lol.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Just in the editor sorting MRP for the invalid table stuff, its a lot harder in that because so much is interconnected, one mistake and the domino effect starts.

    Then once i think it sorted the multitude of testing begins... One good thing is that if Alphawaves can edit the Generic exe's with a patch then very little is needed to revert back to the original method used. win - win :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. MMIKEE

    MMIKEE MDL Senior Member

    Oct 6, 2012
    380
    361
    10
    I vote for KEEPING all the info screens enabled... I always monitor them as they progress to completion... On a fast PC / Laptop they ZING by quickly but I can deal with that... LOL
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Edits done to MRP -- The testing begins!

    Two on the go:

    1 - VMware VM - Windows 7 (Default DMI) - No SLIC, Invalid MSDM table.
    2- - RealPC - Windows 10 (Asus DMI) - Asus SLIC, No MSDM Table.

    The 3rd test (as ran out of monitors!), will be a Lenovo Tower with no SLIC, Genuine W10 Home MSDM.

    You can't really use a KVM switch when installing the Windows OS as it tends to forget the keyboard/Mouse when you switch between units. grr.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    #1379 mxman2k, Sep 19, 2017
    Last edited: Sep 19, 2017
    (OP)
    Test 2 - Real PC All ok no failures :) - so nice to have a SSD in that lol.

    Test 1 VM All ok no failures, ignored invalid MSDM table.

    Test 3 Lenovo - All ok no failures.

    Test 4 Vmware VM Windows 10 - No DMI, No SLIC, Invalid MSDM table. All ok no failures, detected invalid MSDM. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,320
    21,062
    210
    Here are the result logs. Boring i know, but a LOT of work gone into fixing the glitch, i know it probably be rare if it happens but now it has a 'fix' in place.

    Code:
    Multi-OEM/Retail Project Version : 170919-R65.4 - RC  [MRP/MDL]
     
    Required project files extracted successfully.
     
    DeCompile has detected a 'VMware' Virtual Machine.
     
    OEM's folder detected, structure appears OK.
     
    Enhanced Log Mode: Enabled.
     
    OS Installation Date/Time: 19/09/2017 -- 2:42pm
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version Installed     : Windows 7 Professional x64
    [OSINF] Edition {Registry}    : Professional
    [OSINF] Edition {WMIC}        : Professional
    [OSINF] Build Information     : 7601.23807.amd64fre.win7sp1_ldr.170512-0600
    [OSINF] Edition Language/Code : en-US / 1033 {409h}
    [OSINF] Locale                : en-GB
    [OSINF] Language Name Value   : ENG
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [VMware Virtual Platform]
    [MBINF] #02 CS Model Name     : [VMware Virtual Platform]
    [MBINF] #04 CS Vendor Name    : [VMware, Inc.]
    [MBINF] #05 CS System Name    : [VMware, Inc.]
    [MBINF] #06 Baseboard Name    : [Intel Corporation]
    [MBINF] #08 BIOS or SLIC ID   : [INTEL]
    [MBINF] #11 MSDM Brand Name   : [Invalid MSDM Table Data] 
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Core{TM} i5-6400 CPU @ 2.70GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 94 Stepping 3]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [1] / [1]
    [CMINF] Total Physical Memory : [2047 Mb]
    [CMINF] Available Memory      : [1643 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: HDD Detected.
     
    [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_7_Pro'.
    [CKDMI] Querying BIOS for manufacturer branding information.
    [DSLIC] Detecting any SLIC information.
    [VMDMI] A standard VMware VM detected with no SLIC or valid MSDM present.
    [NOSLC] No valid SLIC found for OEM activation.
    [THMOK] VMware [#VMware] manufacturer detected for automated theme/branding.
    [CHKMN] Computer Model Name: 'VMware Virtual Platform' has been applied.
    [BRND1] -> Branding Extra Checks Section.
    [FTHNU] Force_Theme file was not detected.
    [X64RP] Registry fix for x64 theme applied.
    [THMMS] -> OEM Brand Transfer Management Section.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [UBREP] User.bmp replaced.
    [OTFTS] -> OEM Theme Files Transfer Section.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [THMSA] VMware theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type.
    [AMBPS] BIOS/Boot Mode : Legacy
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] -> Checking if Windows is activated/licensed.
    [CHKLS] License Status: Out-of-Box Grace
    [CHKLS] System reboot maybe required to complete activation.
    [AMUTC] UserTweaks.cmd file is present, attempting to apply.
    [AMUTC] UserTweaks completed without errors.
    [ADMAN] Add-On Manager: Completed.
    [CLNUP] MRP Clean Up Routine Processed.
     
    The Multi-OEM/Retail Project has completed. 

    Code:
    Multi-OEM/Retail Project Version : 170919-R65.4 - RC  [MRP/MDL]
     
    Required project files extracted successfully.
     
    OEM's folder detected, structure appears OK.
     
    Enhanced Log Mode: Enabled.
     
    W10TB option enabled: Windows 10 Title Bars will be Colorized.
     
    OS Installation Date/Time: 19/09/2017 -- 2:17pm
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version Installed     : Windows 10 Pro x64
    [OSINF] Edition {Registry}    : Professional
    [OSINF] Edition {WMIC}        : Professional
    [OSINF] Build Information     : 15063.0.amd64fre.rs2_release.170317-1834
    [OSINF] Update Build Revision : 0 {Baseline Release}
    [OSINF] Edition Language/Code : en-GB / 2057 {809h}
    [OSINF] Locale                : en-GB
    [OSINF] Language Name Value   : ENG
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [H81M-HDS]
    [MBINF] #02 CS Model Name     : [H81M-HDS]
    [MBINF] #04 CS Vendor Name    : [ASUSTeK Computer INC.]
    [MBINF] #05 CS System Name    : [ASUSTeK Computer INC.]
    [MBINF] #06 Baseboard Name    : [ASUSTeK Computer INC.]
    [MBINF] #08 BIOS or SLIC ID   : [_ASUS_]
    [MBINF] #09 SLIC Version      : [v2.1]
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Celeron{R} CPU G1820 @ 2.70GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 60 Stepping 3]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] Total Physical Memory : [3896 Mb]
    [CMINF] Available Memory      : [3412 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: SSD Detected.
     
    [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Pro'.
    [CKDMI] Querying BIOS for manufacturer branding information.
    [THMOK] Asus [#04] manufacturer detected for automated theme/branding.
    [CHKMN] Computer Model Name: 'H81M-HDS' has been applied.
    [BRND1] -> Branding Extra Checks Section.
    [FTHNU] Force_Theme file was not detected.
    [THMMS] -> OEM Brand Transfer Management Section.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [W8XAP] -> Windows 10: User Account Picture Management Section 1.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [WXAP2] -> Windows 10: User Account Picture Management Section 2.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg.
    [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg.
    [OTFTS] -> OEM Theme Files Transfer Section.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [THMSA] Asus theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [CMSDM] Querying BIOS for any MSDM data.
    [CMSDM] No MSDM Table/Key detected in BIOS.
    [USRAC] Windows 10 Enhanced Log-On screen has been enabled.
    [W10TB] Windows 10 TitleBar 'Grey' Colorization applied.
    [USRAC] 'User Account Picture' registry entry applied.
    [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected.
    [USRD0] Detected 'defaultuser0', removal process started.
    [RDUPM] Removal of 'defaultuser0' account was successful.
    [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type.
    [AMBPS] BIOS/Boot Mode : Legacy
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] -> Checking if Windows is activated/licensed.
    [CHKLS] License Status: Notification
    [CHKLS] Online connection maybe required to complete activation.
    [AMUTC] UserTweaks.cmd file is present, attempting to apply.
    [AMUTC] UserTweaks completed without errors.
    [ADMAN] Add-On Manager: Completed.
    [CLNUP] MRP Clean Up Routine Processed.
     
    ================================================================================
    = Please Note: It is advisable to logout or reboot your computer when possible =
    =              to allow the User and Log-On background pictures to finalize.   =
    ================================================================================
     
    The Multi-OEM/Retail Project has completed. 

    Code:
    Multi-OEM/Retail Project Version : 170919-R65.4 - RC  [MRP/MDL]
     
    Required project files extracted successfully.
     
    OEM's folder detected, structure appears OK.
     
    Enhanced Log Mode: Enabled.
     
    W10TB option enabled: Windows 10 Title Bars will be Colorized.
     
    OS Installation Date/Time: 19/09/2017 -- 2:43pm
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version Installed     : Windows 10 Home x64
    [OSINF] Edition {Registry}    : Core
    [OSINF] Edition {WMIC}        : Core
    [OSINF] Build Information     : 15063.0.amd64fre.rs2_release.170317-1834
    [OSINF] Update Build Revision : 0 {Baseline Release}
    [OSINF] Edition Language/Code : en-GB / 2057 {809h}
    [OSINF] Locale                : en-GB
    [OSINF] Language Name Value   : ENG
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [90DA002]
    [MBINF] #02 CS Model Name     : [90DA002]
    [MBINF] #04 CS Vendor Name    : [LENOVO]
    [MBINF] #05 CS System Name    : [LENOVO]
    [MBINF] #06 Baseboard Name    : [LENOVO]
    [MBINF] #08 BIOS or SLIC ID   : [LENOVO]
    [MBINF] #11 MSDM Brand Name   : [Lenovo]
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Celeron{R} CPU G3900 @ 2.80GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 94 Stepping 3]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] Total Physical Memory : [8101 Mb]
    [CMINF] Available Memory      : [7522 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: HDD Detected.
     
    [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Core'.
    [CKDMI] Querying BIOS for manufacturer branding information.
    [THMOK] Lenovo [#04] manufacturer detected for automated theme/branding.
    [CHKMN] Computer Model Name: '90DA002' has been applied.
    [BRND1] -> Branding Extra Checks Section.
    [FTHNU] Force_Theme file was not detected.
    [THMMS] -> OEM Brand Transfer Management Section.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [W8XAP] -> Windows 10: User Account Picture Management Section 1.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [WXAP2] -> Windows 10: User Account Picture Management Section 2.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg.
    [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg.
    [OTFTS] -> OEM Theme Files Transfer Section.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [THMSA] Lenovo theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [CMSDM] Querying BIOS for any MSDM data.
    [CMSDM] Processing MSDM Key...
    [CMSDM] -> Show WMIC/MSDM Edition/Channel Information.
    [CMSDM] -> {WMIC} OS Edition     : 'Core'
    [CMSDM] -> {MSDM} KeyEditionID   : 'Core'
    [CMSDM] -> {MSDM} ChannelID      : 'MSDM'
    [CMSDM] Key Detection Routine Used : 1
    [CMSDM] MSDM Key Information: Win 10 Core
    [CMSDM] The detected MSDM key can be used for the Edition installed, saved and applied.
    [CMSDM] The MSDM key details have been saved in C:\MSDM-Key.txt.
    [USRAC] Windows 10 Enhanced Log-On screen has been enabled.
    [W10TB] Windows 10 TitleBar 'Grey' Colorization applied.
    [USRAC] 'User Account Picture' registry entry applied.
    [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected.
    [USRD0] Detected 'defaultuser0', removal process started.
    [RDUPM] Removal of 'defaultuser0' account was successful.
    [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type.
    [AMBPS] BIOS/Boot Mode : Legacy
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] -> Checking if Windows is activated/licensed.
    [CHKLS] License Status: Notification
    [CHKLS] Online connection required to complete MSDM activation.
    [AMUTC] UserTweaks.cmd file is present, attempting to apply.
    [AMUTC] UserTweaks completed without errors.
    [ADMAN] Add-On Manager: Completed.
    [CLNUP] MRP Clean Up Routine Processed.
     
    ================================================================================
    = Please Note: It is advisable to logout or reboot your computer when possible =
    =              to allow the User and Log-On background pictures to finalize.   =
    ================================================================================
     
    The Multi-OEM/Retail Project has completed. 

    Code:
    Multi-OEM/Retail Project Version : 170919-R65.4 - RC  [MRP/MDL]
     
    Required project files extracted successfully.
     
    DeCompile has detected a 'VMware' Virtual Machine.
     
    OEM's folder detected, structure appears OK.
     
    Enhanced Log Mode: Enabled.
     
    W10TB option enabled: Windows 10 Title Bars will be Colorized.
     
    OS Installation Date/Time: 19/09/2017 -- 3:29pm
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version Installed     : Windows 10 Pro x64
    [OSINF] Edition {Registry}    : Professional
    [OSINF] Edition {WMIC}        : Professional
    [OSINF] Build Information     : 15063.0.amd64fre.rs2_release.170317-1834
    [OSINF] Update Build Revision : 0 {Baseline Release}
    [OSINF] Edition Language/Code : en-GB / 2057 {809h}
    [OSINF] Locale                : en-GB
    [OSINF] Language Name Value   : ENG
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [VMware Virtual Platform]
    [MBINF] #02 CS Model Name     : [VMware Virtual Platform]
    [MBINF] #04 CS Vendor Name    : [VMware, Inc.]
    [MBINF] #05 CS System Name    : [VMware, Inc.]
    [MBINF] #06 Baseboard Name    : [Intel Corporation]
    [MBINF] #08 BIOS or SLIC ID   : [INTEL]
    [MBINF] #11 MSDM Brand Name   : [Invalid MSDM Table Data] 
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Core{TM} i5-6400 CPU @ 2.70GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 94 Stepping 3]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] Total Physical Memory : [2047 Mb]
    [CMINF] Available Memory      : [1612 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: HDD Detected.
     
    [CHKLF] OS drive rename option enabled, 'Local Disk' changed to 'Windows_10_Pro'.
    [CKDMI] Querying BIOS for manufacturer branding information.
    [VMDMI] A standard VMware VM detected with no SLIC or valid MSDM present.
    [THMOK] VMware [#VMware] manufacturer detected for automated theme/branding.
    [CHKMN] Computer Model Name: 'VMware Virtual Platform' has been applied.
    [BRND1] -> Branding Extra Checks Section.
    [FTHNU] Force_Theme file was not detected.
    [THMMS] -> OEM Brand Transfer Management Section.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [W8XAP] -> Windows 10: User Account Picture Management Section 1.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [WXAP2] -> Windows 10: User Account Picture Management Section 2.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg.
    [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg.
    [OTFTS] -> OEM Theme Files Transfer Section.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [THMSA] VMware theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [CMSDM] Querying BIOS for any MSDM data.
    [CMSDM] Invalid MSDM Table Detected. Unable to process.
    [USRAC] Windows 10 Enhanced Log-On screen has been enabled.
    [W10TB] Windows 10 TitleBar 'Blue' Colorization applied.
    [USRAC] 'User Account Picture' registry entry applied.
    [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected.
    [USRD0] Detected 'defaultuser0', removal process started.
    [RDUPM] Removal of 'defaultuser0' account was successful.
    [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type.
    [AMBPS] BIOS/Boot Mode : Legacy
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] -> Checking if Windows is activated/licensed.
    [CHKLS] License Status: Notification
    [CHKLS] Online connection maybe required to complete activation.
    [AMUTC] UserTweaks.cmd file is present, attempting to apply.
    [AMUTC] UserTweaks completed without errors.
    [ADMAN] Add-On Manager: Completed.
    [CLNUP] MRP Clean Up Routine Processed.
     
    ================================================================================
    = Please Note: It is advisable to logout or reboot your computer when possible =
    =              to allow the User and Log-On background pictures to finalize.   =
    ================================================================================
     
    The Multi-OEM/Retail Project has completed. 

    A few things to tidy up and change version from 65.4 RC to 66.0 Baseline.

    I am pretty confident the 'patch' is working perfectly, however it is an experimental one until a proper solution is made. It not affect anything else as the results show.

    Will post when have finalized the code and done the changelog etc, then upload the new baseline.

    Sorry it is such a short time between releases, but it needed to be patched.

    Many thanks to mad_max for pointing this out.

    This is the reason I ask for feedback, if there is a problem let me know i will do my best to sort it out as soon as is possible.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...