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
    2,954
    6,908
    90
    thats on VMWare itself, vmplayer not have that option (unless they added it now) :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    VMX:
    Code:
    firmware = "efi"
    uefi.secureBoot.enabled = "TRUE"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    ooh i not seen the uefi.secureboot.enabled bit before :eek:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    It's from the VM i created in VMWare Pro WS.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    im still on vmware 12 :p so it must be new to v14 :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    #2406 Enthousiast, Mar 10, 2018
    Last edited: Mar 11, 2018
    Prolly:
    Code:
    Multi-OEM/Retail Project Version : 180309-R85.0.T10 - RC  [MRP via MDL Forum ONLY]
     
    Required project files extracted successfully.
     
    DeCompile has detected a 'VMware' Virtual Machine.
     
    OEM's folder detected, structure appears OK.
     
    Detected Config File          - Checking For User Options...
    Config Creator Version Used   - v2.3
                                  - Options Pre-Check Completed.
     
    MRP Logging Mode              : Standard
    Confirm File Delete           : Disabled
    W10 TitleBar Color            : Disabled
    Show 'ThisPC' On Desktop      : Enabled
     
    OS Installation Date/Time     : 03/11/2018 {UTC} -- 01:40am
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version {SKU}         : Windows 10 Pro {48}
    [OSINF] Edition {Registry}    : Professional {48}
    [OSINF] Edition {CBS}         : Professional
    [OSINF] Architecture          : 64 Bit
    [OSINF] Build Information     : 16299.15.amd64fre.rs3_release.170928-1534
    [OSINF] Update Build Revision : 248
    [OSINF] Installation Type     : Client
    [OSINF] Edition Language/Code : en-US / 1033 {409h}
    [OSINF] Locale                : en-US
    [OSINF] Language Name Value   : ENU
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [VMware7,1]
    [MBINF] #02 CS Model Name     : [VMware7,1]
    [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 1 : [INTEL  - 6040000]
    [MBINF] #09 SLIC Information  : [No SLIC Table Present]
    [MBINF] #11 MSDM Information  : [No MSDM Table Present]
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 58 Stepping 9]
    [CMINF] CPU Architecture      : [32/64 Bit]
    [CMINF] CPU ID Code           : [1F8BFBFF000306A9]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] CPU VT Mode Enabled   : [No]
    [CMINF] Total Physical Memory : [4094 Mb]
    [CMINF] Available Memory      : [3591 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: SSD Detected.
     
    [SATOU] List user options enabled or applied...
    [PKEIC] The PID.txt file was not detected.
    [PKEIC] The ei.cfg file "D:\Sources\ei.cfg" was detected.
    [RETXT] The Retail.txt file was not detected.
    [CKDMI] Querying DMI/BIOS for any OEM manufacturer brand information.
    [VMDMI] Default DMI VMware VM detected with no valid SLIC or MSDM present to use as theme.
    [THMOK] VMware [VMware] manufacturer detected for automated theme/branding.
    [CHKMN] Model Name: Not defined in DMI/BIOS or User specified.
    [USRFT] CustomTheme option was not used.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [WX81S] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg.
    [WX81S] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [ATHBA] VMware OEM theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [USRAC] Windows 10: Enhanced Log-On screen has been enabled.
    [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 completed.
    [AMBPS] BIOS/Boot Mode  : UEFI
    [AMBPS] Partition Type  : GPT
    [AMBPS] Secure Boot     : Enabled
    [AMHDC] Controller Mode : NVMe/PCIe {SCSI Controller}
    [CHKLS] Check if Windows is activated/licensed...
    [CHKLS] License Status: Licensed, {HWID} Digital/Store License
    [OSLRC] License Status Reason Code: 0x4004F401
    [OSLRT] This computer has a valid Digital/Store License.
    [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 Windows OS installed to finalize any settings.                 =
    =                                                                                       =
    =              If you have used any tweak options within the configuration file then    =
    =              it is required to do a log out or reboot cycle to allow these options    =
    =              to take effect.                                                          =
    =========================================================================================
     
    The Multi-OEM/Retail Project has completed.
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    [AMHDC] Controller Mode : NVMe/PCIe {SCSI Controller} :g: usually it is SAS/Scsi.... it must alter something else.. :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    I set the VM to emulate the nVME ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    Shows i not play about with the options in VMWare Workstation lol :oops:

    Damn wish i checked the options in VMware i could of sped up the testing of the QT lol
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    Now i know it myself, i can test some other stuff ;) My win 7 AIO's with official nVME support :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    I know Vbox could emulate a SSD via the options. Interesting about VMware.... Think it might get some more hammer now :p
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. JanCerny

    JanCerny MDL Member

    Sep 13, 2012
    247
    149
    10
    It's NVMe, not nVME.
    grammar-nazi.jpg

    NVMe has nothing to do with nVidia. :p
     
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    Who suggested it has anything to do with nVIDIA? I prolltype nVME because of eMMC ;):p
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    There will be a update to the Query tool shortly...

    Main code is the same just a tweak to the License check area.

    It is a rare thing that a nul result is returned, it seems if the token store is corrupted it can throw a spanner into the works and no text will be shown where the part that says:

    #14 License Status - Nothing would appear here!

    Now if something is screwed up with the activation or token store:

    #14 License Status - Undefined/Corrupted Token Store

    Will be shown.

    Thanks to @Enthousiast for bringing that to my attention.

    Usually the result would be a numeric value 0 to 6 returned which is converted into a human understandable result.

    The next MRP will have this 'fix' added although i doubt it will really need it, as on a fresh install as it will be a normal 0 - 6 result - unless someone has modified the OS WIM prior to installation. Or used a Gen2 ISO that is known to screw up a few things with MRP.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    Query Tool v51.1 has been uploaded and 2nd post updated with link and password.

    Quick Summary

    + Fixed a small glitch if the License Status returns a nul or out of range result which indicates a possible Token Store corruption or other problem with the activation status. Thanks @Enthousiast for bringing that to my attention.

    + Also fixed a small bug that at times would show errors when checking the Drive Controller section under some OS's (7 usually) if the controller is not present.

    + Added {I} or {S} after the Controller Mode text to indicate if it was SCSI or IDE that returned the result.

    No other changes to code.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. JanCerny

    JanCerny MDL Member

    Sep 13, 2012
    247
    149
    10
    I was discovered new "Windows 10 1709 feature". o_O Disable Driver Searching will be ignored and reverted, if you connected to the internet during installation. Please add warning "Please disconnect LAN before installation, otherwise this settings will be reverted".
     

    Attached Files:

  18. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    #2418 mxman2k, Mar 14, 2018
    Last edited: Mar 14, 2018
    (OP)
    During install some of the later tweaks are not effective until the reboot/log-out cycle is done once the desktop appears. I think i have already mentioned that.

    Driver blocking i will add a note about it in the next Creator and in the readme's. :)

    On next Creator the tool-tip shows the note about being connected etc and the .ini has this:
    Code:
    # Windows 10 Kernels Only
    # :DisableDriverSearching - This Enables or Disables the Driver Searching within Windows.
    # This option turns off or on the Driver Searching used in Windows Update.
    # Note as this option tweaks a policy setting you will see a message about 'Some settings are managed by your organization' this is normal.
    # This does not work for Windows 10 Home/Core Editions, MRP will ignore this option on those Editions.
    # Also note that during installation of the OS to prevent drivers from being downloaded make sure the device is NOT connected to the internet.
    # Default No.
    Not everyone uses a Local account, some use online accounts, so the note will be now present for the user to decide.

    The driver blocking tweak is ran in the early stages of oobe/MRP, there is a reboot cycle that happens before the user name entry etc, the driver tweak should in theory then have been set at this point.

    It is not reverted as once that cycle been done as it is then locked in place. -- unless m$ are aware of that tweak now during Setup and totally ignore it. :g:If so nothing i or MRP can do to fix that, only to say disconnect from net during installation of the OS but you will loose the ability to use your online M$ account during user setup stage as only Local Account is available, you can switch to online account later if required.

    If you notice the project.log has a gap between the first section and the addon manager:
    [BSHCS] Branding script has completed.
    <the gap here>
    [ADMAN] Add-On Manager: Started.

    This gap indicates the reboot cycle setup does and it is within this cycle that the tweaks that have 'applied' at the end of their lines have been completed.

    Plus during that cycle on the next boot Setupcomplete.cmd, (possibly FirstLogon.cmd), is ran if either is present, after those have completed the add-on manager section is then executed and the tweaks with 'enabled' at the end of their lines are then 'applied' and shown in the log.

    This is why i made a note that if you use the setupcomplete.cmd/FirstLogon.cmd not to have a reboot cycle such as Shutdown /r (/l or /s), or remove the Scripts folder with a line of:

    RD /S /Q "%windir%\Setup\Scripts"

    - within those scripts, as then MRP's files would be deleted and the log will stop at the branding part!

    When MRP completes fully, (or there is a fatal error within the branding script that aborts the project), it will automatically remove the Scripts folder and contents to tidy things up.

    *For the next MRP release*
    I have now added a simple detection routine at the end of the branding script that if either SetupComplete and/or Firstlogxx .cmd's are present that a note is made in the log that they are there.

    So if the Project.log stops at this point then it is known that something in those scripts caused MRP to fail completion, either due to a reboot/log-out cycle or premature deletion of the Scripts folder.

    Same applies to UserTweaks and Wintel .cmd's if they are edited to have a reboot/logout cycle or deletion of the Scripts folder then MRP and the log will also stop at this point.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    24,851
    35,323
    390
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,954
    6,908
    90
    I have had that a couple of times when testing the insiders, also once on a rs3 install too :g:although that was after the latest CU (march).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...