My logon script for cleanup which I added the call to reg file to be executed breaks the whole script. Reg entry was not entered and cleanup failed. Going to try a schtask to see if it can do it when logged on. There has to be a work around. I got everything else working. I will mess with this more this evening and tomorrow, real life calls.
Id take it easy for a few mate. 10 is just going to change again in the next update, rinse and repeat. Think its gonna be a good six months before it starts to settle down
Think I am going to take both of your advice...lets wait till next update and see if this gets corrected. If not, I will address it then. I really do feel that win10 x64 th2 has major bugs with the install. Until M$ fixes it, we will wait. The reason I say win10 x64 th2 has bugs is that the x86 versions installs correctly without any issues so it isnt M$ implementing anything new for the install but they broke it for oem branding by the system (nt authority) not having permissions to edit files and folders and reg entries. I am back to win8.1, my OS works. lol
M$ implemented win10 th2 x64 with new activation method. This new method uses legit windows past oem keys to install windows 10 th2 x64. In other words, I can use my legit windows 8.1 oem-dm key to install and activate windows 10 th2 x64. With this being said, M$ broke something having to do with nt authority having all permissions for correct oem branding. We will have to wait for this to be fixed. Win10 th2 x64 has big issues with some configurations, like my lappy. Ppl like myself are sh*t out of luck until M$ fixes this.
When you have time and if you have vmware can you test to remove these updates and try if the oem will brand normally, if it didn't brand then the next iso's will have these updates and will be fixed
Sure no problem, if I had time right now I would do it but real life calls lol I'll do it tomorrow morning.
After doing some reading from HP website I think I know what is happening for me and BALTAGY. Win10 isnt fully supporting our configurations. Even though using vmware it is still tied to your hardware. My lappy is a year old and its not really functional with win10. My Intel chipset isnt supported, my touchpad isnt supported, since chipset is issue of course my display will have issues. This is why when I went back to win8.1 everything started working again. I bet if you try Mr.X aio iso it does the same on your machine (branding issues). Its M$ not fully supporting our configurations. This is why for some the project still works and then ppl like myself and BALTAGY it doesnt work. Check your computer manufacture for more info on compatibility with windows 10. We cant even test the project out anymore on our machines with win10. I will have to depend on ppl like Mr.X to let us know if the project works with future win10 x64 versions because my configuration doesnt allow even testing with vmware, until M$ adds more support for Intel chipsets. Win10 is still very much beta if you ask me.
It will be more than 4.5GB for sure? it wont help me in work, but ty How to check my computer if it's compatible is there an app or something?
I used the HP assistant and read additional info link it provided. Thats when I seen M$ doesnt support my config that well. I have also noticed techbench removed the th2 update so changes are happening as we speak. I expect refreshed iso's soon. In my case the intel chipset isnt supported and I think that is the main reason I have issues with x64 th2. Obviously techbench agrees and put 240 back up. M$ not supporting some intel chipsets is very bad for M$!
Probably not what you want to hear mate but Ive just updated to the latest project (11.13) from the previous one and Im only getting Activated not branded! Some screenies attached, seems oobe/info isnt created. User Pic and theme get copied but the wallpaper isnt there as its meant to be in oobe/info. Nothings changed elsewhere bar overwriting the old scripts etc, a straight copy-paste job. Tried it on 8 straight after as well and its the same. No biggie mind. Its been a long weekend so I might have missed a post somewhere with all the W10 stuff going on, apologies if I have! You wouldnt happen to have a link for the previous version would you?
Since win10 th2 is update only now, no need to find a workaround for what M$ broke. Getting all the original win10 rtm th1 versions again now since I deleted the old ones with th2 release which was a mistake. lol I should have all my win10 th1 rtm iso's back again this evening.
th2 deletes the info folder auto. This is the problem along with reg entries that wont apply. M$ pulled th2 for a reason, it was broke! Complain to M$. There has been no changes in script in many months....its M$ breaking the oobe.cmd process. Ppl need to complain to them instead of me. I am not touching this project anymore until M$ fixes all this sh*t!
There has been no changes to script in many months. I am going to see if we can get this thread locked until M$ fixes what they broke. Now everything is broke? No way.