I removed the variable I was trying and just wrote the code in whole to avoid this taking all day to test. lol I am doing my final install now to make sure user pic shows on login screen correctly. This is the only thing to check now.
There's a problem with KMS and Vmware sometimes it happen with me also just reset the guest and setup will do the "Just a Moment" again
The cleanup.cmd is broken and its over 20 lines long so I will have to test the creation one line at a time so I am done for today. I am not spending my whole day doing this. I need some play time. Take care, I am outie. See everyone tomorrow.
Everything is done except for the user pic on login screen. Had to get the cleanup.cmd working first so I can use that to do the reg entry.
No since in disabling defender when kms solutions make exceptions that dont work and turn defender on. This is a kms issue so not bothering with it. Still have issues with kms and user pic. I wonder if it works on legit oem or is this a problem all around with this new version? I rather focus on oem/retail like the thread title says personally. Seems kms is going to have some issues on unlocking customizations if oem/retails works. Just saying...
I don't see Microsoft Toolkit making any exclusion in Defender, let's see when you test retails if Defender will be disabled
Ok, here is your answer about the user pics....oh boy here we go. Lets make this simple and I wont get into the registry...User Account Pictures is changed once unlocked by activation and you manually change pic, the directory changes to Default Account Pictures and adds many reg entries. Now for the big question, can we change the directory name to make OS thinks it unlocked from oobe? Also, is this the same on legit oem machines? I need to have a computer repair store in order to test this properly. My win8.1 does the same once a pic is choosen for user picture. So this is something that been around but was not affecting the project until win10. Guys and gals this is going to be fun and very very time consuming. Update: It doesnt change the name of directory, only goes back to original.
First post updated 8-8-2016. See change log for details. FYI: This does not include a fix for the user login screen picture as of yet.
@The_Guardian Will PM you all the results & observations once all the systems have been installed. *Used latest project: Multi_OEM_Project_08.08.2016 But a quick result on a W10 RS1 install: MSI board (MSI SLIC) No LAN connected (as LAN port shafted - plus it never been upgraded to W10 so no Digital Entitlement/Licence). All looks ok, Theme set as MSI and not 'unsaved' as before. info: During setup, chose Pro, advanced - deleted all partitions, on Get going fast, i chose Customize and turned 'off' ALL switches on the 3 screens of options, Cortana set to Not Now. Log: Spoiler 09/08/2016 9:55:59.11 Project Version Date: 06-29-2016. ---Hardware incompatibility and slipsteaming has been known to cause branding failures--- 09/08/2016 9:55:59.31 Files present and extracted successfully. 09/08/2016 9:56:02.11 OEMs folder found successfully. 09/08/2016 9:56:03.71 Defined Windows 10 Pro x64 version Professional editon found. 09/08/2016 9:56:18.12 Defined MSI manufacture found for branding and possible activation. 09/08/2016 9:56:20.45 Error, no OEM-DM key present. 09/08/2016 9:56:24.86 License Status: Error, not licensed. 09/08/2016 9:56:24.86 Force theme text file not present. 09/08/2016 9:56:25.78 Syspdt not defined. 09/08/2016 9:56:25.78 Backgrounds folder created successfully. 09/08/2016 9:56:25.80 Deletion of OOBE.xml file successful. 09/08/2016 9:56:25.80 User.bmp backed-up and replaced successfully. 09/08/2016 9:56:25.99 User.png backed-up and replaced successfully. 09/08/2016 9:56:26.07 User-40.png backed-up and replaced successfully. 09/08/2016 9:56:26.16 User-32.png backed-up and replaced successfully. 09/08/2016 9:56:26.18 User-48.png backed-up and replaced successfully. 09/08/2016 9:56:26.22 User-192.png backed-up and replaced successfully. 09/08/2016 9:56:26.24 Theme backed-up and replaced successfully. 09/08/2016 9:56:26.58 Img100.jpg backed-up and replaced successfully. 09/08/2016 9:56:34.22 Advanced logon screen for win 10 enabled successfully. 09/08/2016 9:56:34.23 Info folder created successfully. 09/08/2016 9:56:34.31 Files moved to System32\oobe\Info folder successfully. 09/08/2016 9:56:43.17 RunOnce reg entry added successfully. 09/08/2016 9:56:43.17 Script has completed successfully. More results later via PM
Changes I will do today, obviously update build version date in log (I fogot) and move activation status to cleanup.cmd to ensure all activations can be logged whether oem/retail or upgrade to win10 activation status. I rather do updates in steps so I dont get confused and forget some things. I was so focused on user pic in win10 that I forgot some things. Sorry about that. As far as the user pic for new windows 10, not yet resolved but working on it in spare time, plus others are helping as well to try and find the issue. Testing changes now...had to do some changes...blame my OCD. lol Final testing now...done.
Hello, sorry for my english A small error in the script Wintel.cmd. The name of the service CDPUserSvc_xxxx is randomly generated at startup
No offense but maybe you should try it first before posting. Worked in vmware and on my wifes lappy which has win10. Both had different random numbers but with wildcard, it worked. Checked task manager and admin tools/services and it had stopped. SC Query might not accept it but command prompt does.
Hi all, Just download Win10 LTSB 1607 aka RS1. Somehow the OEM branding does not work. I can't even find the Project.txt under C:\ Does the LTSB support OEM branding? TIA