Sadly the VirtualBox add MSDM table experiment failed. Tried different ways for over 4 hours, gave up as was very late. Almost 3.30am It installs so far then 'hangs' on the spinning dots, does a couple of restarts, devices ready etc, reboots then sits there and never continues. Must have the checksum wrong still or something. May have another attempt at some stage. At least the W10 Lenovo I have still works, even with a bodged PSU so testing can still be done.
After much messing about getting the MSDM table to be checksum correct... You can use a MSDM table with VirtualBox! but NOT SLIC at same time its either/or. Spoiler Code: Multi-OEM/Retail Project Version : 170225-R53.7s-Internal-Testing [MRP/MDL] Files present and extracted successfully. NOTE: This is a Internal Testing release, functional, features may change before BaseLine. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: 27/02/2017 14:58:02.05 > Checking installed OS name. 14:58:02.29 Windows 10 Pro x64 version found. 14:58:02.30 > Checking installed OS Edition/SKU. 14:58:02.44 Professional Edition/SKU installed. 14:58:02.44 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 14:58:13.48 Edition Language/Code: en-GB ( 2057 [809h] ) 14:58:13.48 OS Locale: en-GB 14:58:13.49 OS Language Value: ENG -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [Desktop] #2 CS Model Name : [Desktop] #4 CS Vendor Name : [MSI-PC] #5 CS System Name : [MSI-PC] #6 Baseboard Name : [value] #8 BIOS ID : [TOSCPL] > Detecting if a Solid State or Standard Hard Drive is present. INFO: Standard HDD Detected. 14:58:17.15 > Checking if 'LblDrv' flag is enabled. 14:58:17.40 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 14:58:17.40 > Checking DMI for manufacture information. 14:58:17.78 Msi [#4] manufacture will be used for theme/branding. 14:58:17.78 > Branding Section Part 1. 14:58:17.78 Force theme text file not present. 14:58:18.69 > Checking DMI for Model Name. 14:58:18.72 Model Name: Not detected. 14:58:18.72 > Branding Section Part 2. 14:58:18.72 Desktop backgrounds folder created. 14:58:18.77 > Windows 8.x/10/Server 2016 User Account Picture Management Section 1. 14:58:18.77 OOBE.xml file deleted. 14:58:18.77 User.bmp replaced. 14:58:18.97 User.png replaced. 14:58:19.03 User-40.png replaced. 14:58:19.13 > Windows 10/Server 2016 User Account Picture Management Section 2. 14:58:19.14 User-32.png replaced. 14:58:19.19 User-48.png replaced. 14:58:19.20 User-192.png replaced. 14:58:19.22 Lock Screen {img105.jpg} replaced. 14:58:19.55 > Theme Management Section. 14:58:19.56 Msi theme has been applied. 14:58:19.67 Log-In Background {img100.jpg} replaced. 14:58:19.70 > Transfer Theme Files Section. 14:58:19.70 System32\oobe\Info folder has been created. 14:58:19.72 Required theme files transferred to 'System32\oobe\Info folder'. 14:58:19.72 > Deletion of obsolete files. 14:58:20.19 Branding script has completed. 15:03:22.34 > Add-On Manager in progress. 15:03:22.66 > Detecting if Visual C 2012 DLL's are present. 15:03:25.15 > Visual C 2012 DLL's have been temporarily installed. 15:03:25.17 > Checking BIOS for MSDM Key. 15:03:45.65 > Processing MSDM Key for Edition status. 15:03:48.18 > Show MSDM Key Information. 15:03:48.18 MSDM Key Information: Win 8.1 RTM CoreConnected OEM;DM 15:03:48.18 MSDM Key is not for the installed Edition, saved but NOT applied. 15:03:48.19 See C:\MSDM-Key.txt for your saved MSDM key details. 15:03:48.19 > Temporary Visual C 2012 DLL's used have been uninstalled. 15:03:48.71 > Checking if computer is a 'default' Virtual Machine. 15:03:49.18 Advanced Log-On screen has been enabled. 15:03:50.02 User Account Pictures registry entry applied. 15:03:50.06 'Registered Owner' registry entry corrected. 15:03:50.08 Detected 'defaultuser0', attempting to remove the folder... 15:03:50.21 Removal of 'defaultuser0' folder successful. 15:03:50.31 > Checking BIOS's mode and System drive's partition type. 15:04:13.34 BIOS Mode: Legacy, Partition Type: MBR 15:04:13.34 > Checking Hard Drive Controller Mode. 15:04:16.44 HDD Controller Mode: [AHCI] 15:04:16.44 > Checking Online Status. 15:04:16.44 Device does not appear connected to the Internet, online license check failed. 15:04:22.17 > Checking if Windows is activated/licensed. 15:04:24.93 License Status: Not licensed. 15:04:24.93 > Checking if 'UserTweaks.cmd' present. 15:04:24.93 'UserTweaks.cmd' present, attempting to apply. 15:04:24.93 UserTweaks.cmd has completed. 15:05:33.13 > Checking if 'WinTel.cmd' present. ================================================================================ = 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. Used the MSDM key from a shafted Windows 8.1 laptop bios that's why it says TOSCPL in the bios ID. Not attempted to activate online as i was just testing if V'Box would actually accept the table.
Code: Multi-OEM/Retail Project Version : 170207-R53s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: wo 01-03-2017 7:03:54,39 Windows 10 Home Insider Preview x86 version found. 7:03:54,48 Core Edition/SKU installed. 7:03:54,48 Build Version: 15046.0.x86fre.rs2_release.170224-1700 7:04:02,40 Edition Language/Code: nl-NL ( 1043 [413h] ) 7:04:02,40 OS Locale: nl-NL 7:04:02,40 OS Language Value: NLD -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [INTEL] INFO: Standard HDD Detected. 7:04:05,23 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Core'. 7:04:05,76 VMware [VMware] manufacture will be used for theme/branding. 7:04:06,65 No MSDM key detected in BIOS. 7:04:06,65 Force theme text file not present. 7:04:06,87 Model Name: 'VMware Virtual Platform' detected and applied. 7:04:06,87 Desktop backgrounds folder created. 7:04:06,90 OOBE.xml file deleted. 7:04:06,92 User.bmp replaced. 7:04:07,00 User.png replaced. 7:04:07,03 User-40.png replaced. 7:04:07,03 User-32.png replaced. 7:04:07,05 User-48.png replaced. 7:04:07,05 User-192.png replaced. 7:04:07,05 Lock Screen {img105.jpg} replaced. 7:04:07,36 VMware theme has been applied. 7:04:07,42 Log-In Background {img100.jpg} replaced. 7:04:07,47 System32\oobe\Info folder has been created. 7:04:07,48 Required theme files transferred to 'System32\oobe\Info folder'. 7:04:07,80 Branding script has completed.
I just see now the script didn't report finishing, only branding was finished. Used it combined with abbodi1406's KMS_VL_ALL v12, will test without it.
15046 m$ have made a few insider versions since i last saw! Hmm... I saw it stopped at branding. I wonder what they have changed (again). I think the kms script has a EXIT command and it causes a few glitches. When i was trying Education edition with KMS it borked the project.
I've added the rmdir line (i showed you earlier) in abbodi1406's oem setupcomplete.cmd (discussed it a while ago with abbodi1406, where to add it).
Using only MRP project files: Code: OEM's folder detected, structure appears OK. OS Installation Date: wo 01-03-2017 10:02:46,05 Windows 10 Home Insider Preview x86 version found. 10:02:46,19 Core Edition/SKU installed. 10:02:46,19 Build Version: 15046.0.x86fre.rs2_release.170224-1700 10:02:50,66 Edition Language/Code: nl-NL ( 1043 [413h] ) 10:02:50,66 OS Locale: nl-NL 10:02:50,66 OS Language Value: NLD -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [INTEL] INFO: Standard HDD Detected. 10:02:53,30 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Core'. 10:02:53,77 VMware [VMware] manufacture will be used for theme/branding. 10:02:54,74 No MSDM key detected in BIOS. 10:02:54,74 Force theme text file not present. 10:02:54,99 Model Name: 'VMware Virtual Platform' detected and applied. 10:02:54,99 Desktop backgrounds folder created. 10:02:55,00 OOBE.xml file deleted. 10:02:55,02 User.bmp replaced. 10:02:55,16 User.png replaced. 10:02:55,19 User-40.png replaced. 10:02:55,19 User-32.png replaced. 10:02:55,21 User-48.png replaced. 10:02:55,21 User-192.png replaced. 10:02:55,21 Lock Screen {img105.jpg} replaced. 10:02:55,55 VMware theme has been applied. 10:02:55,62 Log-In Background {img100.jpg} replaced. 10:02:55,64 System32\oobe\Info folder has been created. 10:02:55,66 Required theme files transferred to 'System32\oobe\Info folder'. 10:02:55,92 Branding script has completed. 10:05:25,16 Advanced Log-On screen has been enabled. 10:05:25,47 User Account Pictures registry entry applied. 10:05:25,50 'Registered Owner' registry entry corrected. 10:05:25,50 Detected 'defaultuser0', attempting to remove the folder... 10:05:25,67 Removal of 'defaultuser0' folder successful. 10:05:32,19 BIOS Mode: Legacy, Partition Type: MBR 10:05:33,21 HDD Controller Mode: [AHCI] 10:05:39,67 License Status: Not licensed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-On background pictures to finalize. ============================================================================ Thank you for using the project, MRP has now completed. I never used it combined, always seperate indexes for MRP and KMS, I was just curious and wanted to test.
Yeah the Exit command causes the project to abort due to it stops the add-on module from working because it 'clears' a flag or something.
this is where i placed the rmdir command, will test with original script combined with MRP. Code: schtasks /create /tn "\Microsoft\Windows\SoftwareProtectionPlatform\SvcTrigger" /xml "%~dp0Win32\SvcTrigger.xml" /f >nul 2>&1 cd %~dp0 attrib -R -A -S -H *.* cd\ RMDIR /S /Q "C:\Windows\Setup\Scripts" exit /b
Last public reply about this topic, without my rmdir modifications it works but it leaves abbodi1406's project files in "c:\windows\setup\scripts". Code: Multi-OEM/Retail Project Version : 170207-R53s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: wo 01-03-2017 10:30:46,11 Windows 10 Home Insider Preview x86 version found. 10:30:46,46 Core Edition/SKU installed. 10:30:46,46 Build Version: 15046.0.x86fre.rs2_release.170224-1700 10:30:53,86 Edition Language/Code: nl-NL ( 1043 [413h] ) 10:30:53,86 OS Locale: nl-NL 10:30:53,86 OS Language Value: NLD -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [INTEL] INFO: Standard HDD Detected. 10:30:56,32 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Core'. 10:30:56,79 VMware [VMware] manufacture will be used for theme/branding. 10:30:57,91 No MSDM key detected in BIOS. 10:30:57,93 Force theme text file not present. 10:30:58,18 Model Name: 'VMware Virtual Platform' detected and applied. 10:30:58,18 Desktop backgrounds folder created. 10:30:58,19 OOBE.xml file deleted. 10:30:58,19 User.bmp replaced. 10:30:58,27 User.png replaced. 10:30:58,29 User-40.png replaced. 10:30:58,30 User-32.png replaced. 10:30:58,30 User-48.png replaced. 10:30:58,30 User-192.png replaced. 10:30:58,32 Lock Screen {img105.jpg} replaced. 10:30:58,54 VMware theme has been applied. 10:30:58,66 Log-In Background {img100.jpg} replaced. 10:30:58,69 System32\oobe\Info folder has been created. 10:30:58,71 Required theme files transferred to 'System32\oobe\Info folder'. 10:30:59,05 Branding script has completed. 10:43:42,18 Advanced Log-On screen has been enabled. 10:43:42,50 User Account Pictures registry entry applied. 10:43:42,53 'Registered Owner' registry entry corrected. 10:43:42,53 Detected 'defaultuser0', attempting to remove the folder... 10:43:42,72 Removal of 'defaultuser0' folder successful. 10:43:50,19 BIOS Mode: Legacy, Partition Type: MBR 10:43:50,46 HDD Controller Mode: [AHCI] 10:43:56,24 License Status: Licensed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-On background pictures to finalize. ============================================================================ Thank you for using the project, MRP has now completed.
As MRP has completed fully it 'should' auto purge the Scripts folder and remove anything left over on a logout/reboot as the cleanup script hopefully was created and then run when the reboot/logout cycle was completed. *edit* Have found a rare glitch that sometimes bits are left over, this has now been addressed and the next release ie Beta will have the correction in place. R54 Beta will have the enhanced MSDM info, (for those with MSDM table computers), also a few other changes have been done - more information later... Beta will start very soon, just awaiting feedback on a test or two.
Done a Beta 2 as there was a slight glitch on deleting some files when finished with, nothing major as it all cleaned up on a reboot/logout cycle anyway, was just making sure nothing is hanging about prior to the cycle. well apart from the Scripts folder itself but you cant delete something that is in use. Hence the requirement to logout/reboot cleanup part. Sorry i am a perfectionist it has to be right or it bugs me forever. Updated post #2 with new version. It seems other than that little tweak the project is working perfectly. Just need more feedback with those with MSDM tables so i know it works on all languages. Hint-Hint!!
OK, doggie is testing his new monitor setup ...4 are quite comfortable, now VMware has it's own . German Win 10 x64 Core $OEM$ install is running on Win 8 Core MSDM VM, stay tuned.
I'm confident it will all work, just want to make sure in case i need to alter any code before baseline. It is a copy of the Query Tool script i used, with a few extra parts to make it compliant with MRP's log output and the saved MSDMkey.txt file. Four monitors lucky devil I have one on main pc and the other is on the test pc with a KVM switch so i can use other PC's to hammer tests with.
On the system drive, plus if there was a MSDM table you will get a MSDMkey.txt with the msdm key in plus other info like how to insert it if something went wrong etc. Not require that txt file as it hold the personal key. Moved it from the project.log ages ago so it made it safer to post any project.log files and not need to edit anything out.
Code: Multi-OEM/Retail Project Version : 170303-R54.b2 - BETA [MRP/MDL] Required files present and extracted successfully. NOTE: This is a BETA release, MRP may not function as expected. OEM's folder detected, structure appears OK. OS Installation Date: 03.03.2017 19:53:22,24 Windows 10 Home x64 version found. 19:53:22,52 Core Edition/SKU installed. 19:53:22,52 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 19:53:26,94 Edition Language/Code: de-DE ( 1031 [407h] ) 19:53:26,94 OS Locale: de-DE 19:53:26,94 OS Language Value: DEU -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [DELL] INFO: Standard HDD Detected. 19:53:30,16 Rename 'System Drive' flag not set, 'C:' will be left as OS default. 19:53:30,69 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 19:53:30,69 Dell [VMware] manufacture will be used for theme/branding. 19:53:30,69 Force theme text file not present. 19:53:31,09 Computer Model Name: 'VMware Virtual Platform' detected and applied. 19:53:31,09 Desktop backgrounds folder created. 19:53:31,16 OOBE.xml file deleted. 19:53:31,16 User.bmp replaced. 19:53:31,23 User.png replaced. 19:53:31,26 User-40.png replaced. 19:53:31,27 User-32.png replaced. 19:53:31,27 User-48.png replaced. 19:53:31,27 User-192.png replaced. 19:53:31,29 Lock Screen {img105.jpg} replaced. 19:53:31,51 Dell theme has been applied. 19:53:31,55 Log-In Background {img100.jpg} replaced. 19:53:31,59 System32\oobe\info folder has been created. 19:53:31,59 Required theme files transferred to 'System32\oobe\info folder'. 19:53:31,79 Branding script has completed. 19:56:20,33 Add-On Manager in progress. 19:56:36,68 Processing MSDM Key for Edition status. 19:56:39,15 MSDM Key Information: Win 8 RTM Core OEM;DM 19:56:55,22 Your MSDM key is for the Edition installed and has been applied. 19:56:55,27 See C:\MSDM-Key.txt for your saved MSDM key details. 19:56:59,16 Advanced Log-On screen has been enabled. 19:56:59,32 Set 'User Account Picture' registry entry applied. 19:56:59,38 'Registered Owner' registry entry corrected. 19:56:59,38 Detected 'defaultuser0', attempting to remove the folder... 19:56:59,52 Removal of 'defaultuser0' folder successful. 19:57:06,18 BIOS Mode: Legacy, Partition Type: MBR 19:57:06,58 HDD Controller Mode: [AHCI] 19:57:06,58 Device does not appear connected to the Internet, online license check failed. 19:57:12,69 License Status: Not Licensed. ================================================================================ = 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 now completed.