Hazar wiil it work for system that exceeded the 30 days trial period and run out of rearm's? IF YES, I don't think it's a good idea to do a rearm, I for myself used that machine (that exceeded the trial period) for testing, so I did not want to do a rearm..
I was not sure if MGAdiag would go genuine if it had expired and been patched without a rearm, is your Mgadiag genuine now?
You're probably passing MGAdiag cos of the rearm If it is proven it is not necessary I will remove it Just put there as a safety check
Yeah thanks, problem was the %username% variable was echoing tuvis name into the icacls command, which had unicode charachters. Solved it with a global security identifier for the admin group
Hazar I have another expired machine (that passed the trial period).. can you send me a version of 1.2 that does not do a rearm? so I will test it and report back if MGAdiag will go genuine or not.. Btw I really appreciate your efforts!! thank you for fixing the unicode problems.
OK thank you Hazar.. this is really a great alternative to loaders.. it's your idea and it's very good one! if it keep working, it will be even better than loaders.. it also very simple, tested it on windows 7 pro/home premium/ultimate editions and it's working on all of them (now also working on my windows 7 pro hebrew unicode system) I have just hope microsoft will not be able to blacklist/disable this.. I will also test v1.2 with windows update on the new windows 7 Enterprise N-1 edition. I also hope windows update will work on WGA 2.0. but first I am waiting for your v1.2 without a rearm to confirm if it will be genuine on an expired system without the need of rearm, because I don't think it's really necessary. and I don't like to do a rearm.
yea that was for you im updating it now for 64bit support (i was being lazy at first) ill give you the source and eerything i have done for it
tuvi if you want it not to rearm change slmgr from slmgr.vbs to slmgr.vbs.disabled before it runs, must be that name or the program uninstall will break. This will cause it to skip the reaem
Hazar I prefer to wait for your v1.2 without rearm version. I don't want to have some problems because I plan to test it on my main desktop pc (also will test windows update and the new wga 2.0 that will be released soon).
I found the problem. Most likely cause im on x64 I had to take ownership of \sysWOW64\slmgr.vbs and then disable it by changing the name. Now OpaTool is saying slmgr cant be found. Is that really enough though?? Doesnt seem normal to be able to thwart microsofts protections by changing a couple of file names.
A simple Q from a lay person: 1) I have an old PC that was OK with the built-in activation in W7Ult [the 32/64b OEM by Faxcool]. I simply stopped the automatic updates and won't do it but will instead protect it by other means [KIS and so on]. Will that do, please? 2) On the other hand, a new lappy [Acer 5920G] apparently isn't activated [the little black window that pops up after install and installs an SN, hey tell me, isn't working], so in that case I would need an act*vator/loader/patch. Which ones exactly for W7Ult 64b OEM, please?? If I succeed I would also kill the automatic updates and wouldn't go to M$ website to get them... Thanx!