Replaced bios442 with 440 and now it works, i didn't install home but branding worked and msdm was found: Code: Multi-OEM/Retail Project Version : 170312-R54.1 - BaseLine [MRP/MDL] Required files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: zo 19-03-2017 0:50:45,65 Windows 10 Pro x64 version found. 0:50:45,78 Professional Edition/SKU installed. 0:50:45,78 Build Version: 15061.0.amd64fre.rs2_release.170315-1424 0:50:52,36 Edition Language/Code: nl-NL ( 1043 [413h] ) 0:50:52,36 OS Locale: nl-NL 0:50:52,36 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 : [DELL] INFO: Standard HDD Detected. 0:50:56,28 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 0:50:56,76 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 0:50:56,76 Dell [VMware] manufacture will be used for theme/branding. 0:50:56,76 Force theme text file not present. 0:50:57,45 Computer Model Name: 'VMware Virtual Platform' detected and applied. 0:50:57,45 Desktop backgrounds folder created. 0:50:57,47 OOBE.xml file deleted. 0:50:57,47 User.bmp replaced. 0:50:57,59 User.png replaced. 0:50:57,62 User-40.png replaced. 0:50:57,65 User-32.png replaced. 0:50:57,65 User-48.png replaced. 0:50:57,65 User-192.png replaced. 0:50:57,67 Lock Screen {img105.jpg} replaced. 0:50:57,97 Dell theme has been applied. 0:50:58,11 Log-In Background {img100.jpg} replaced. 0:50:58,14 System32\oobe\info folder has been created. 0:50:58,15 Required theme files transferred to 'System32\oobe\info' folder. 0:50:58,44 Branding script has completed. 0:54:43,48 Add-On Manager in progress. 0:54:54,82 Processing MSDM Key for Edition status. 0:54:58,17 MSDM Key Information: Win 8 RTM Core OEM-DM 0:54:58,18 Your MSDM Key is not for the installed Edition, saved but not applied. 0:54:59,04 See C:\MSDM-Key.txt for your saved MSDM key details. 0:55:04,15 Advanced Log-On screen has been enabled. 0:55:04,92 Set 'User Account Picture' registry entry applied. 0:55:06,21 'Registered Owner' registry entry corrected. 0:55:06,21 Detected 'defaultuser0', attempting to remove the folder... 0:55:07,23 Removal of 'defaultuser0' folder successful. 0:55:15,16 BIOS Mode: Legacy, Partition Type: MBR 0:55:15,51 HDD Controller Mode: [AHCI] 0:55:21,35 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. Maybe i have done something wrong with bios442? I've added the bios442.rom file to the vm dir and this line to .vmx: "bios442.filename = "bios442.rom" (without quotes).
Was thinking it either a 'bios' glitch, VMware software change or m$ changing something in the latest CU like they did in the Rs1 refresh although that was just the lock/login screens not 'taking'. bios440.filename = "bios443.rom" is the one i'm using on the VM player. So your line is almost correct.
My line was: bios442.filename = "bios442.rom" instead of bios440.filename = "bios442.rom" (testing bios440.filename = "bios442.rom" now) Now it skips the key question at inital setup, test runs.
Easily done, the times i make mistakes in the project is unreal lol. With Vbox if i make any mistake in the config file it will not run as it checks the file before you get to even click start vm. Looks like VMware is a bit more tolerant on some settings.
This starts to be really weird, no project.log but the scripts folder contains the project files (before and after reboot), no branding, no mentioning msdm key. It's getting late, will do more testing tomorrow.
That's a registry you can add to OOBE.cmd to disable File Explorer ads in RS2 Spoiler [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ShowSyncProviderNotifications"=dword:00000000
@Enth, very weird! Just hoping it VMWare's changes that have caused the problem and not a change in the latest CU update or RS2. @BALTAGY, sadly that not work in the oobe.cmd as the user registry hive is not created at that point. It could be used within UserTweaks.cmd or via setupcomplete.cmd using: Code: Reg add "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v "ShowSyncProviderNotifications" /t REG_DWORD /d "0" /f >nul Or via oobe.cmd as: Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v "ShowSyncProviderNotifications" /t REG_DWORD /d "0" /f >nul Using HKLM should set for all users. I am out most of the day so won't be about until later this evening (GMT).
After Enthousiasts experiments seemed to fail, i tested today with VMware WS 12.5.4 build-5192485 and latest 15061 using Win 10 Pro MSDM. 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: Sun 03/19/2017 12:32:36.62 Windows 10 Pro x64 version found. 12:32:36.82 Professional Edition/SKU installed. 12:32:36.82 Build Version: 15061.0.amd64fre.rs2_release.170315-1424 12:32:42.37 Edition Language/Code: en-US ( 1033 [409h] ) 12:32:42.37 OS Locale: en-US 12:32:42.37 OS Language Value: ENU -------------------- 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. 12:32:46.22 Rename 'System Drive' flag not set, 'C:' will be left as OS default. 12:32:46.68 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 12:32:46.68 Dell [VMware] manufacture will be used for theme/branding. 12:32:46.68 Force theme text file not present. 12:32:47.26 Computer Model Name: 'VMware Virtual Platform' detected and applied. 12:32:47.28 Desktop backgrounds folder created. 12:32:47.31 OOBE.xml file deleted. 12:32:47.31 User.bmp replaced. 12:32:47.39 User.png replaced. 12:32:47.42 User-40.png replaced. 12:32:47.45 User-32.png replaced. 12:32:47.45 User-48.png replaced. 12:32:47.45 User-192.png replaced. 12:32:47.45 Lock Screen {img105.jpg} replaced. 12:32:47.67 Dell theme has been applied. 12:32:47.76 Log-In Background {img100.jpg} replaced. 12:32:47.82 System32\oobe\info folder has been created. 12:32:47.85 Required theme files transferred to 'System32\oobe\info folder'. 12:32:48.12 Branding script has completed. 12:37:40,30 Add-On Manager in progress. 12:37:52,60 Processing MSDM Key for Edition status. 12:37:55,22 MSDM Key Information: Win 10 RTM Professional OEM;DM 12:38:04,21 Your MSDM key is for the Edition installed and has been applied. 12:38:04,74 See C:\MSDM-Key.txt for your saved MSDM key details. 12:38:08,32 Advanced Log-On screen has been enabled. 12:38:08,49 Set 'User Account Picture' registry entry applied. 12:38:08,61 'Registered Owner' registry entry corrected. 12:38:08,63 Detected 'defaultuser0', attempting to remove the folder... 12:38:08,77 Removal of 'defaultuser0' folder successful. 12:38:13,22 BIOS Mode: Legacy, Partition Type: MBR 12:38:13,44 HDD Controller Mode: [AHCI] 12:38:13,46 Device does not appear connected to the Internet, online license check failed. 12:38:20,80 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.
What line did you use in .vmx? bios440.rom works, bios442.rom with the pro msdm not, in my tests (VM 12.5.4 build-5192485).
Second test with Ent build of 15061 also succeeded. Not sure what Enth did . 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: Sun 03/19/2017 13:11:26.85 Windows 10 Enterprise x64 version found. 13:11:27.26 Enterprise Edition/SKU installed. 13:11:27.26 Build Version: 15061.0.amd64fre.rs2_release.170315-1424 13:11:39.85 Edition Language/Code: en-US ( 1033 [409h] ) 13:11:39.85 OS Locale: en-US 13:11:39.85 OS Language Value: ENU -------------------- 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. 13:11:43.18 Rename 'System Drive' flag not set, 'C:' will be left as OS default. 13:11:43.63 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 13:11:43.63 Dell [VMware] manufacture will be used for theme/branding. 13:11:43.63 Force theme text file not present. 13:11:44.12 Computer Model Name: 'VMware Virtual Platform' detected and applied. 13:11:44.12 Desktop backgrounds folder created. 13:11:44.13 OOBE.xml file deleted. 13:11:44.13 User.bmp replaced. 13:11:44.20 User.png replaced. 13:11:44.21 User-40.png replaced. 13:11:44.23 User-32.png replaced. 13:11:44.23 User-48.png replaced. 13:11:44.24 User-192.png replaced. 13:11:44.24 Lock Screen {img105.jpg} replaced. 13:11:44.43 Dell theme has been applied. 13:11:44.51 Log-In Background {img100.jpg} replaced. 13:11:44.52 System32\oobe\info folder has been created. 13:11:44.55 Required theme files transferred to 'System32\oobe\info folder'. 13:11:44.85 Branding script has completed. 13:16:14,30 Add-On Manager in progress. 13:16:25,96 Processing MSDM Key for Edition status. 13:16:29,14 MSDM Key Information: Win 10 RTM Enterprise OEM;DM 13:16:38,18 Your MSDM key is for the Edition installed and has been applied. 13:16:38,69 See C:\MSDM-Key.txt for your saved MSDM key details. 13:16:42,83 Advanced Log-On screen has been enabled. 13:16:42,96 Set 'User Account Picture' registry entry applied. 13:16:42,99 'Registered Owner' registry entry corrected. 13:16:42,99 Detected 'defaultuser0', attempting to remove the folder... 13:16:43,17 Removal of 'defaultuser0' folder successful. 13:16:48,21 BIOS Mode: Legacy, Partition Type: MBR 13:16:48,43 HDD Controller Mode: [AHCI] 13:16:48,44 Device does not appear connected to the Internet, online license check failed. 13:16:56,38 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.
I have 26 VM's installed, will cleanup and retest, after W10UI is finished with my dutch 10 AiO (10 indexes)
@Enth, 26 Vm's I get confused just six. (3 on Vmware Player and the other 3 on Vbox). Fingers crossed you can sort out the VM's. Back early, wiring a new light fitting with live electrics is a bit scary. As it was a factory the office lighting circuit is all interconnected with the main factory, which i thought was odd then was informed the office block was 'added' later and they just connected into the same circuit. Personally i would of had a separate breaker system , mentioned it and i might get the job to do that.