Multi OEM/Retail Project

The Install.cmd is internal so users cannot break it and then complain to me. End users have no need to edit the internals of this project thus why it is internal. If upgrade done on windows 10 then it isnt really using a key but hardware id's instead for activation. I used this project on my own computer which was upgraded and I did a fresh clean install and it activated once online (no need for a generic key).

 

First post updated Nov 7, 2015.

 

If you are wanting to show home and pro editions choices when installing then yes, it is still needed.

 

Obviously, it doesnt do it when not online. Once you get through the install process of setting up your internet connection I would say that would be one of the first things it does, check activation status.

 

What a pain in the *** M$ has become with win10. I did the update yesterday and I noticed when it was done my HP theme and info is gone except for my user display image. I am testing the new win10 th2 iso's now to make sure script works on fresh install. I do not know if Alphawaves system brand changer still works on this new build. Looks like it is testing time again. I hope furture win10 updates are not going to be like this last one (th2).

The only way to avoid this from happening in the future might be to lock it down but then end user wont be able to change it if they want so that isnt really a solution.

Update: The project still works on fresh install so that is good but I wonder if M$ will be insisting removing oem info in the future or is this just a fluke? Seems as if they locked down their .etl file from the desktop. WinTel.cmd works from install but not on desktop anymore because M$ locked it down.

 

If you read right about your post you will see where I have tested this project on the th2 iso's and it works, even the optional WinTel.cmd. Now, if M$ updates again in the future the images and windows telemetry will be turned back on and locked down. From a fresh clean install, everything still works.

 

Actually, the WinTel.cmd had some issues with the new build version (th2) but I have corrected it now with some changes plus added error handling for querying sch tasks. I will be uploading later today after more testing but it does seem to be resolved now.

 

Updated first post 11-13-2015.

If end users wish to run the WinTel.cmd file from desktop instead of in project, change the end of script so it exits instead of self deletes (EXIT command at the end).