I personally know the refresh 1607 january iso's cause a few problems, but that only on the lock/logon screens, they are set but the OS ignores them and uses default ones and have not worked that puzzle out. Slip-streamed with later updates after .477 or the 'RTM' .0 version no problems. Very weird.
To what degree is that install modified? I miss one of the normal problems with win 10: Code: 12:48:51,20 The 'defaultuser0' folder was not present. That's not normal behavior. The defaultuser0 is always present, as far as i've seen.
Defaultuser0 is a odd ball, on some non English versions it is not present, Brazilian is one. Also on some editions such as Education and Enterprise ones it has to be force removed. It is also still present on the insider versions, by now you would of thought they fixed that!
Just a small bug report: the HP background wallpaper has a strip of white pixels on the left edge. I was able to find the same background sans the white pixels on google images.
Will update the oem's.7z soon. Then they will be ready for next MRP release too. Found a couple of other backgrounds that look a bit 'off' centre plus will check every wallpaper to make sure it is the correct aspect if i can, most i have set to 1920 x 1080. I did correct the Gigabyte user tile for w8.x/10 as it looked odd *edit* HP one is now correct, the one i originally downloaded was 1366x768 and i up-scaled it, have looked at the one on google images 1366x768 and i have noticed the white pixel line, i searched for a proper 1080p one and that is correct, have now added that into oem's.7z. So easy to miss. Have edited the Toshiba User810.bmp as it was way off centre, so it a bit of a boring one now lol. However you can change those as you wish.
Ok checked through the OEM's and changed the HP wallpaper to the correct one (no pixel lines). Uploaded, available on paste.co MRP-OEMs-Only.7z {OEM's.7z} only. VMWare left as it was.
It seems when you use the Administrator account and no 'normal' user created, as noticed in your autounattend.xml it does not create the defaultuser0 because the user creation oobe screen is 'hidden'. Now i can see why defaultuser0 not there. Its same when you go into Audit mode, because oobe is 'paused' and the Admin account is in use, that default user is not created - until you return to normal oobe. The main thing is the project worked, the key entry screen maybe because of the autounattend file altering something. I noticed it applied the MSDM key, so technically when online it will be activated. If the key entry appeared during the setup ie within the first few screens then it is indeed the autounattend causing some confusion, it nothing with MRP as that would not of ran until the oobe stage starts, just after the getting devices ready part, or there about.
Code: <ProductKey> <Key></Key> </ProductKey> I believe this is the part why the key screen appears as there is no key used, i think you can use the default Pro key in your case the -3V66T one, then once MRP kicks in it would insert your MSDM key (if present). I am only guessing this would be a work around. It may work lol. It will shut up Setup from asking for a key, although the 3V66T key may bork. I know there is another 'default' Pro key for W10 somewhere on MDL that could be used to get setup to continue as Pro but obviously would not activate, however the PC's MSDM key would be inserted via MRP, or a HWID activation would occur if that available on that PC. Seems like it will work in theory... Not used unattend method since XP days so memory is a bit rusty.
@enth I was close, forgot about DISM key insertion. Can see that bios440 going to be used quite a lot from now on.
Code: Multi-OEM/Retail Project Version : 170303-R54.0 - BaseLine [MRP/MDL] Required files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: 08/03/2017 23:29:41,04 Windows 10 Pro Insider Preview x86 version found. 23:29:41,29 Professional Edition/SKU installed. 23:29:41,29 Build Version: 15025.1000.x86fre.rs_prerelease.170127-1750 23:29:42,63 Edition Language/Code: fr-FR ( 1036 [40Ch] ) 23:29:42,63 OS Locale: fr-FR 23:29:42,63 OS Language Value: FRA -------------------- 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: SSD Detected. 23:29:45,13 Rename 'System Drive' flag not set, 'C:' will be left as OS default. 23:29:46,07 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 23:29:46,07 Dell [VMware] manufacture will be used for theme/branding. 23:29:46,07 Force theme text file not present. 23:29:46,18 Computer Model Name: 'VMware Virtual Platform' detected and applied. 23:29:46,18 Desktop backgrounds folder created. 23:29:46,20 OOBE.xml file deleted. 23:29:46,21 User.bmp replaced. 23:29:46,21 User.png replaced. 23:29:46,23 User-40.png replaced. 23:29:46,23 User-32.png replaced. 23:29:46,24 User-48.png replaced. 23:29:46,24 User-192.png replaced. 23:29:46,24 Lock Screen {img105.jpg} replaced. 23:29:46,38 Dell theme has been applied. 23:29:46,41 Log-In Background {img100.jpg} replaced. 23:29:46,46 System32\oobe\info folder has been created. 23:29:46,48 Required theme files transferred to 'System32\oobe\info folder'. 23:29:46,96 Branding script has completed. 0:33:58,38 Add-On Manager in progress. 0:34:09,99 Processing MSDM Key for Edition status. 0:34:13,24 MSDM Key Information: Unable to define Edition for MSDM key. 0:34:13,28 See C:\MSDM-Key.txt for your saved MSDM key details. 0:34:17,11 Advanced Log-On screen has been enabled. 0:34:17,28 Set 'User Account Picture' registry entry applied. 0:34:17,33 'Registered Owner' registry entry corrected. 0:34:17,33 Detected 'defaultuser0', attempting to remove the folder... 0:34:17,56 Removal of 'defaultuser0' folder successful. 0:34:17,92 Removal of 'defaultuser0' folder successful. 0:34:24,25 BIOS Mode: Legacy, Partition Type: MBR 0:34:24,52 HDD Controller Mode: [AHCI] 0:34:24,52 Device does not appear connected to the Internet, online license check failed. 0:34:30,49 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. = ================================================================================ The Multi-OEM/Retail Project has now completed. Licenced : using kms
MSDM Key Information: Unable to define Edition for MSDM key. This message will appear if: The MSDM key is newer than the database check. The MSDM table's checksum is incorrect. Or lastly the Key within the table is non OEM-DM. But as i see it is activated, it not matter
Code: PKeyConfig : Windows 8.1 / Server 2012 R2 Key : Key Status : Valid Product ID : 002..........6-AAOEM Extended PID : XXXXX-02522..................72017 SKU ID : c7e5dd5....................5f5794cd0 Description : Windows Server 12 R2 RTM ServerStandard OEM:SLP Edition ID : ServerStandard Sub Type : [Blue]X18-90712 License Type : OEM:SLP Channel : OEM Crypto ID : 2522 (9da) Total Keys : 20000 (4e20) Block Key Base : Not found Comment : Benchmark : 0,5 seconds