yes it activated. the project is in the setup folder as before. This is getting frustrating... i think i have upset cortana didnt realise it was listening i swore then i got her saying i do not like profanities and shut the laptop down
Since the new win10 has hardware issues if I was you I would wait to update win10. Seriously, M$ fkd up big time and unfortunately your hardware is one it doesnt like. Give it some time and I bet the ISO's will be updated. They rushed this new version before it was ready for the public. Lack of testing it seems. I bet OEM's tech support phone lines are active since this update came out. lol I feel for them.
Thanks for putting up with me , sorry i could not fully test why the project failed. Hopefully I will get another W10 computer in for repair and help if needed then. All my computers was upgraded to windows 10 and the project works a treat, well apart from the user logo. But when looking in the C:\Users folder there is one called defaultuser0 ? along with public and the created username. I wonder if that is causing some strange effects too? At least it activates with or without the PID.txt. I will do a clean install again without the project and leave this laptop at that. Many thanks for your help today/tonight. Mx
The project correctly replaces the pictures in %ProgramData%\Microsoft\User Account Pictures\. I know that it works doing it manually but I would like to have the picture as default for all user accounts by script as it was in TH2. I used the Windows 10 Promotion on the W8 PC. I don't like upgrades from existing OS so I always install from scratch via USB thumb drive. With USB3 and SSD it takes only 10 minutes until setup is finished. If I understood you right I have put in the key I get from MS HWID activation into pid.txt and add ei.cfg (still needed if only Professional and no other version is in the Index of image?). About retail.txt - should I use it now or not?
Like I said before, comparing th2 to the new version is senseless because they are not the same. I do expect a major update to the new version iso's very soon. In your case, yes use the Retail.txt file and place with the oobe.cmd file so the script skips activation and lets the pid.txt file do the activation without any conflicts. Now we know why M$ did a free upgrade and insisted on it. lol
Got some info for everyone regarding the new win10 version and user account pictures. New default sizes for win10 new version. Looks like I need to add the new win10 sizes to the project. I dont have much time today because of doctor appt but will work on it this evening. As far as the oem theme showing unsaved, there is also a change in this but need to find it. Be patient and I will have the solution soon. Seems this was also changed for win8.x as well in an update. Will correct so images fit and hopefully stay put. lol
FYI: With legit W10 OEM PC same behavior as legit W8 OEM. For now I went back to TH2. Not only because of the project. There are lots of other bugs I discovered. However if you release new project rev I try it for sure
BALTAGY is helping with image resizing since that is not my cup of tea. He sent a example and quality is intact. Started looking in the theme to find changes but no go as of yet. Wallpaper size is the same so that isnt the problem. Has to be another setting somewhere. I will find it.
Yeah it was the oddest ram failure i have ever had! On extended memtest i did a couple of runs, because usually duff ram will show up at some point within 2 runs. All came back clear. As it was late i decided to do a mega thrash test of the ram and set it to 10 loops and left it over night. This morning, i had one single byte pop up as duff, once every third loop. So for the first two loops all appeared ok, then third loop the one single byte failed, forth and fifth run clean again, sixth run error in that byte and repeat 2 ok, 3rd failed byte! Usually its blocks of bad ram, never seen just one byte act so odd. Yet windows installed and run ok never bsod'd on me. Just the project failed to run. So put some known good ram in and the project run as intended. So if testing ram best to always run the extended test over several loops, a pain as it takes time, but in my case it showed up a lone byte that was a bit iffy. Computers eh! lol
Usually setting extended test pass to 3 or 4 is enough to show pattern in same location. This is when you know something is wrong. If it always shows in same location a couple times then red flag is set and replacement is needed. Now with that said, the ram may still work but for your case it seems that is a memory location that windows install uses thus the problems. If it wasnt for the install issue you would have never known.
Got updated images from BALTAGY after he put in over 15 hrs on all the images. Dedication and I think a lil OCD because of attention to detail. lol All "we" can say is thank you BALTAGY. I know there is a thanks button but this deservered more then points added to a member stats. Might get me a warning but its worth the thank you publicly.
Theme is fixed in win10 but need to see how it effects vista and win7. Need to focus on user pic now to see why it kicks out after a reboot. Then add the new service for telemetry in the WinTel.cmd file. Making progress but what a PITA! lol
The oem user image for login has setting backwards in registry for win10 anniversary compared to other OS's. I am tellin everyone M$ got some things backwards on this anniversary version. We can adapt the reg file used for win10 but need to add some checks for build in order for it to work on all win10 versions (example TH2 and Anniversary). This is going to take me time which today I am limited. Not to mention the testing time. Be patient but we are working on it. Thanks to BALTAGY and mxman2k for their help.
Those who use this project on warez with kms activations are in for a big surprise when it comes to penalization's such as user login picture and theme's. Will now only work with oem/retail machines for win10 anniversary. M$ got reall smart in this area. By the way, defender will pick up on kms and stop it if not turned off completely. Exceptions no longer work with kms tools. Big changes they did in this version. I know how to get around this manually but with oobe cmd not possible. Oh crap, I think I know a way of getting around this....hold on...more testing.
After thinking about this exploit to accessing group policy without actually doing it has left me with a ethical delima . This is a major security hole if ppl think about it. Win10 has some major holes they created while trying to stop piracy and they dont even know it. From a security stand point I cannot support this OS now with what I have found out. Supporting it in our project would be asking users to be vulnerable to security threats. Please feel free to express your opinion on this subject. I know users will use what OS they want to use but I have mixed feelings on the subject. Tested, I can access other group policies without actually using group policy to do it. Wow, its like swiss cheese.