Not sure if project will work with that version. I know the project doesnt work with server editions. Try using the pid.txt file with a install key in order to make oobe and setupcomplete available. Worth a shot. Without knowing more I would say you are facing some similar issues like others in this thread. Note: User pic on login screen will need to be applied manually after activated. No fix for that yet.
I know the project does not support server editions, not sure if the LTSB is classed as a 'server'. LTSB is one type i have not had chance to try out. Did your computer originally come with windows 8.x or 10? if so the setup may be bypassing the oobe.cmd like the oem version does. This can be verified when installing, you don't get a choice of home/pro etc. Have you tried the ei.cfg file method to tell setup to 'ignore' the MSDM key that is in the bios? The ei.cfg i use is below. {copy/paste into a notepad text file and save as ei.cfg - place in the Sources folder on the ISO} [Channel] _Default [VL] 0 Other than that i am unsure, but it sounds like that is what is happening.
There is now 5 ppl trying to help me find the setting for win10 anniversary version login screen picture. The more the better. Update: I am convinced that the login user pic is not in a reg entry.
With regards to the registry, i have searched through HK Classes, HK Current User and i am now on HK Local Machine, so far nothing that stands out (unless MS have changed the name of the 'key' - like some of the services names grr). Nosing about the registry i have found a few nice tweaks so not all a lost cause lol.
When you click on the the lock screen then the login user pic appears (i mean the default picture we are trying to find out about), the default user picture has transparency. Yet when you put a picture there manually it no longer has that. MSI pic attached has transparent background. Maybe the changes in how they re-written the lockscreen part is one reason it cant be changed via oobe stage? Sorry for screen pic quality my phone has a naff camera.
The_Guardian / mxman2k, Thanks for the inputs and suggestions. Again, PID.txt did the trick. However it took me quite sometime to find Win10 2016 LTSB PID, but it all worthy it. Thanks a lot.
Excuse the ignorance but the 'CERTIFICATES' folder is no longer needed? Congratulations on this great project!
Baltagy sent me info regarding possible cause of user pic not showing auto on win10 anniversary version. Was going to check it out tonight but football season is starting tonight so I will be channel switching. Will look into it tomorrow. Update: That method failed.
Big thanks goes out to mxman2k for the possible solution to the user pic showing on login screen for win10 anniversary version. I have a doctors appt to go to but when I get back I will definitely be trying this method out to see results. If it works we all owe mxman2k many beers.
I might need a eye test after all the searching in the registry before i can see the beers LOL. Fingers crossed this is at least the beginning of the way forward with this annoying glitch. I have tested the method on several clean installs on different computer setups (activated and not activated), and it has worked for me, however as always this will need testing by members to see if there are any side effects. If any, it will be minor and the method used can be reversed very easy and no reinstall of the OS will be needed just a simple double-click of a registry file and a restart of the computer. More details later about the reversal registry 'patch' once The_Guardian has tested the method with the main project files.
Big thanks goes out to mxman2k for his endless searching in the registry. First post updated 8-13-2016. See change log for details.
Has anyone noticed with win10 anniversary version the oem background shows for login screen background?
I have noticed that in win10 anniversary version if we use that reg entry in the local machine part of reg, users cant change user image if they want. I put the reg entry from local machine to current user and now the image can be changed from settings within windows. I am going to move the reg entry to the cleanup.cmd file with a restart command which runs after login and use current user to see results. Sorry I jumped the gun on this fix. Seems I have to tweak it a bit so settings work correctly. brb... Update: The user pic for login screen IS tied to the activation process. If I move it to the current user part of registry then it doesnt work. If I leave it in the local machine part of registry it works but assigns all users to the oem user image and also disables changing the image. After activation you can change it to current user then everyone can change user image on login screen. What a pain in the ass. Yes, I said it. lol I am going to try using kmspico to activate it then if activated move the reg file to current user and see what happens. Takes a couple mins to make changes but then takes over 30 mins to test in vmware. If this works then I will add if not activated then delete the reg entry signifying the computer isnt activated yet since this is it's purpose. I dont want to break the settings within the OS.
Well, either we use it and disable users from changing the user image in windows settings or we leave it alone and let users pic the image themselves. I dont know what else to do so leaving it up to your guys and gals. I can reup the old project date if you wish that doesnt touch the regisrty setting for user login image or we leave it like it is now and hope no one complains if trying to change user image. I leave it up to you... Update: There seem's to be no easy right solution to this issue. I will update the project to include a reversal reg file for those users that want to manually pick image from windows settings. At this point these are our only options until more can be learned...if this can be resolved.