Multi-OEM/Retail Project {MRP} - Mk3

R53s Beta...

Spoiler

Code:

Multi-OEM/Retail Project Version : 170205-R53s-BETA  [MRP/MDL] 
 
Files present and extracted successfully. 
 
NOTE: This is a BETA release, MRP may not function as expected.  
 
Enhanced Log Mode: Activated. 
 
> Checking OEM's Folder Structure.
OEM's folder detected, structure appears OK. 
 
OS Installation Date: 05/02/2017 
 
13:12:19.31 > Checking installed OS name. 
13:12:19.45 Windows 7 Professional x64 version found. 
13:12:19.46 > Checking installed OS Edition/SKU. 
13:12:19.90 Professional Edition/SKU installed. 
13:12:19.90 Build Version: 7601.19135.amd64fre.win7sp1_gdr.160121-1718 
13:12:21.40 Edition Language/Code: en-US ( 1033 [409h] ) 
13:12:21.40 OS Locale:             en-GB 
13:12:21.40 OS Country:            United Kingdom 
13:12:21.40 OS Language Value:     ENG 
 
-------------------- 
DMI BIOS Information 
-------------------- 
#1 CS Product Name   : [Aspire X1301] 
#2 CS Model Name     : [Aspire X1301] 
#4 CS Vendor Name    : [Acer] 
#5 CS System Name    : [Acer] 
#6 Baseboard Name    : [Acer] 
#8 BIOS ID           : [ACRSYS] 
 
> Detecting if a Solid State or Standard Hard Drive is present. 
INFO: Standard HDD Detected. 
 
13:12:24.19 > Checking if 'LblDrv' flag is enabled. 
13:12:24.25 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_7_Pro'. 
13:12:24.25 > Checking DMI for manufacture information. 
13:12:24.67 > Checking for SLIC [SK2S] information. 
13:12:24.81 Acer [#8] manufacture found for possible Vista/Win7 activation. 
13:12:24.81 Acer [#4] manufacture will be used for theme/branding. 
13:12:24.81 > Checking for OEM-SLP Product Key. 
13:12:24.99 Acer OEM-SLP Product Key found and applied. 
13:12:24.99 > OEM XRM-MS Certificate Management. 
13:12:26.73 Acer XRM-MS OEM Certificate present.  
13:12:26.73 Windows 7 OEM activation subroutine created.
13:12:26.73 > Attempting activation via detected SLIC. 
13:12:45.61 > Branding Section Part 1. 
13:12:45.61 Force theme text file not present. 
13:12:45.76 x64 Theme registry patch file applied.
13:12:45.78 > Checking DMI for Model Name. 
13:12:45.80 Model Name: 'Aspire X1301' detected and applied.
13:12:45.80 > Branding Section Part 2. 
13:12:45.80 Desktop backgrounds folder created. 
13:12:45.81 > Theme Management Section 2. 
13:12:45.81 User.bmp replaced. 
13:12:45.83 Acer theme has been applied.  
13:12:45.84 > Transfer Theme Files Section. 
13:12:45.84 System32\oobe\Info folder has been created. 
13:12:45.86 Required theme files transferred to 'System32\oobe\Info folder'. 
13:12:45.87 > Deletion of obsolete files. 
13:12:46.14 Branding script has completed.
13:13:37.19 > Add-On Module #1 in progress. 
13:13:37.63 > Checking if device is a 'default' Virtual Machine. 
13:13:37.69 > Checking BIOS's mode and System drive's partition type. 
13:14:07.22 BIOS Mode: Legacy, Partition Type: MBR 
13:14:07.22 > Checking Hard Drive Controller Mode. 
13:14:07.63 HDD Controller Mode: [IDE] 
13:14:09.16 > Checking if Device is activated/licensed. 
13:14:09.46 License Status: Licensed.  
13:14:09.46 > Checking if 'UserTweaks.cmd' present. 
13:14:09.46 'UserTweaks.cmd' present, attempting to apply. 
13:14:09.46 UserTweaks.cmd has completed. 
 
Enhanced Log Mode: Deactivated. 
 
Thank you for using the project, MRP has now completed. 
 

The bold/highlighted part has been adjusted, the first part is the Build/Edition's primary language, the parts below will show if the locale/keyboard language was changed in the first Windows Setup stage/window. In my test the W7 iso was en-US, and changed to United Kingdom for the locale/keyboard.

Also altered the code for checking online as for some reason Vista/7 would do a check which was not really needed. This will now only show for W8.x/10.

Just doing a test on W10 Home/Pro (January Refresh?) that have just downloaded to see if the Language/Locale bit works as that is a en-US version, it should do but want to make sure before I upload the beta.

 

Tested Primary Language/Locale - OK with W10.

Just noticed something different with the RS1 refresh (January), the lock/sign on screen(s) are default? Even after a few restarts.

Nothing has been altered in the project regarding branding etc.

Windows was not activated at first so i went online and activated Windows thinking it needed to be activated before it would set the picture. Still no lock/login screen change. Went into settings and the lockscreen was set correctly to picture (Acer in my test). Yet on signout/even a reboot -- still default!

Not sure if one of the integrated updates in this RS1 refresh has altered something. But if i go into Settings, change lockscreen, browse to the system32\Oobe\info folder and manually select the wallpaper.jpg it sets the lock/logon picture correctly.

It could just be my system playing up. Yet the first RS1, (14393.0.amd64fre.rs1_release.160715-1616), without the update refresh worked ok.

As can be seen from the Project.log, no failures to set the background images are present!

Spoiler

Code:

Multi-OEM/Retail Project Version : 170205-R53s-BETA  [MRP/MDL] 
 
Files present and extracted successfully. 
 
NOTE: This is a BETA release, MRP may not function as expected.  
 
Enhanced Log Mode: Activated. 
 
> Checking OEM's Folder Structure.
OEM's folder detected, structure appears OK. 
 
OS Installation Date: 05/02/2017 
 
14:01:16.30 > Checking installed OS name. 
14:01:16.42 Windows 10 Pro x64 version found. 
14:01:16.45 > Checking installed OS Edition/SKU. 
14:01:17.06 Professional Edition/SKU installed. 
14:01:17.06 Build Version: 14393.447.amd64fre.rs1_release_inmarket.161102-0100 
14:01:18.88 Edition Language/Code: en-US ( 1033 [409h] ) 
14:01:18.88 OS Locale:             en-GB 
14:01:18.88 OS Country:            United Kingdom 
14:01:18.88 OS Language Value:     ENG 
 
-------------------- 
DMI BIOS Information 
-------------------- 
#1 CS Product Name   : [Aspire X1301] 
#2 CS Model Name     : [Aspire X1301] 
#4 CS Vendor Name    : [Acer] 
#5 CS System Name    : [Acer] 
#6 Baseboard Name    : [Acer] 
#8 BIOS ID           : [ACRSYS] 
 
> Detecting if a Solid State or Standard Hard Drive is present. 
INFO: Standard HDD Detected. 
 
14:01:21.20 > Checking if 'LblDrv' flag is enabled. 
14:01:21.25 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 
14:01:21.25 > Checking DMI for manufacture information. 
14:01:21.88 Acer [#4] manufacture will be used for theme/branding. 
14:01:21.88 > Checking BIOS for MSDM Key. 
14:01:22.38 No MSDM key detected in BIOS. 
14:01:22.38 > Branding Section Part 1. 
14:01:22.38 Force theme text file not present. 
14:01:22.66 > Checking DMI for Model Name. 
14:01:22.69 Model Name: 'Aspire X1301' detected and applied.
14:01:22.69 > Branding Section Part 2. 
14:01:22.69 Desktop backgrounds folder created. 
14:01:22.70 > Windows 8.x/10/Server 2016 User Account Picture Management Section 1. 
14:01:22.70 OOBE.xml file deleted.  
14:01:22.72 User.bmp replaced.  
14:01:22.75 User.png replaced.  
14:01:22.75 User-40.png replaced.  
14:01:22.75 > Windows 10/Server 2016 User Account Picture Management Section 2. 
14:01:22.75 User-32.png replaced.  
14:01:22.77 User-48.png replaced.  
14:01:22.77 User-192.png replaced. 
14:01:22.77 {Background #1} img105.jpg replaced. 
14:01:22.88 > Theme Management Section. 
14:01:22.89 Acer theme has been applied. 
14:01:22.92 {Background #2} img100.jpg replaced. 
14:01:22.97 > Transfer Theme Files Section. 
14:01:22.97 System32\oobe\Info folder has been created. 
14:01:22.99 Required theme files transferred to 'System32\oobe\Info folder'. 
14:01:22.99 > Deletion of obsolete files. 
14:01:23.30 Branding script has completed.
14:04:17.32 > Add-On Module #1 in progress. 
14:04:18.34 > Checking if device is a 'default' Virtual Machine. 
14:04:19.20 Advanced Log-On screen has been enabled.
14:04:19.48 User Account Pictures registry entry applied. 
14:04:19.54 'Registered Owner' registry entry corrected. 
14:04:19.54 Detected 'defaultuser0', attempting to remove the folder... 
14:04:19.73 Removal of 'defaultuser0' folder successful. 
14:04:19.87 > Checking BIOS's mode and System drive's partition type. 
14:05:00.21 BIOS Mode: Legacy, Partition Type: MBR 
14:05:00.21 > Checking Hard Drive Controller Mode. 
14:05:00.67 HDD Controller Mode: [IDE] 
14:05:00.67 > Checking Online Status. 
14:05:00.67 Device does not appear connected to the Internet, online license check failed. 
14:05:04.14 > Checking if Device is activated/licensed. 
14:05:06.17 License Status: Not licensed. 
14:05:06.17 > Checking if 'UserTweaks.cmd' present. 
14:05:06.17 'UserTweaks.cmd' present, attempting to apply. 
14:05:06.18 UserTweaks.cmd has completed. 
 
============================================================================  
Please Note: It is advisable to logout or reboot your computer when possible  
             to allow the User and Log-On background pictures to finalize.    
============================================================================  
 
Enhanced Log Mode: Deactivated. 
 
Thank you for using the project, MRP has now completed. 

Anyone else noticed this?

 

That's normal, when you do a logout/reboot it cleans all that up. Its because windows 'locks' them in use, if i try to force remove it causes odd things to happen, so I clear the left overs on next logout/reboot.

The scripts folder is sometimes there until the cleanup runonce is run on the logout/reboot cycle. The invisible.vbs is to run some addon's without dos windows popping up.

Audit mode yes that will be there until MRP has completed the oobe stage as some addon's may require it.

 

I will make a few changes in 53s-beta and see if i can remove the files another way BEFORE a logout/reboot.

It is safe to remove the files - if windows has released control over them.

I know 53s-beta does after the logout or reboot cycle.

Just going to test if the forced removal will work aka the same way the defaultuser0 folder is removed.

 

The only folder MRP cannot force remove will be the Scripts folder, this will however be removed on the next logout/reboot cycle. Forced removal of that folder will probably cause an unstable system which i not want to happen.

Have made adjustments to 53s-beta's tidy up section to try and force remove the Setup\Invisible.vbs file. It will be removed anyway on the logout/reboot cycle if it cannot be done.

Think i found the glitch in 52s's tidy/clean up, there is a missing quote mark ( " ) after the "location to file" string. Have corrected that now.

Once this install test has completed I will check if anything left, there should only be the empty 'Scripts' folder, which will be cleaned up on the next logout/reboot cycle. Anything else left over will also be removed - hopefully!

Will upload the 53s-Beta once this test complete and it has removed any left over files.

Not uploaded the beta before as i was puzzled why the lock/login screen not working, but it may be down to my test pc or one of my personal tweaks being the cause. It may even be M$ changing something in the January RS1 refresh?

*edit* Test completed. Only thing left now is the empty Scripts folder. This will be removed on the next logout/reboot cycle.

 

You need to login to view this posts content.

 

@Enthousiast, No idea why it still not removing . Have done a normal DEL /F /Q on the file, then if it still exists a takeown of it and tried a forced removal.

 

Methods used...

Normal removal:

Code:

IF EXIST "%WinDir%\Setup\invisible.vbs" DEL /F /Q "%WinDir%\Setup\invisible.vbs" >NUL

Forced retry:

Code:

IF EXIST "%WinDir%\Setup\invisible.vbs" (
TAKEOWN /F "%WinDir%\Setup\invisible.vbs" >NUL 2>&1
ICACLS "%WinDir%\Setup\invisible.vbs" /GRANT *S-1-1-0:F >NUL 2>&1
DEL /F /Q "%WinDir%\Setup\invisible.vbs" >NUL 2>&1
        )

Unless i have the takeown part incorrect?

 

The country bit with ???? is a puzzler as MRP just queries the registry. As it not important i can remove that line on the next beta.

 

@Enth, very odd, as your setupcomplete.cmd should not affect the cleanup on reboot unless the runonce entry for MRPCleanUpOS.cmd is erased, which as the name states cleans up everything on the logout/reboot cycle.

The only time setupcomplete.cmd gets touched in MRP is if using Vista, but then it only adds the activation bit and re-adds anything that was there before.