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!
THe faxcool distro uses a loader developed by a person on this site. To be specific I believe it is nononsence's. I highly recommend you not use modified ISO's because you never know what has been added. Read the repository, read the safe updates sticky and I would advise you to slick your drive and get rid of that faxcool crap. I hope you didn't pay for it on an auction or something but you should never touch those modified distributions. The loader used was developed for the purpose of creating a DVD that would recognize the slic and install the appropriate OEM information or install the lo*der if necessary, very cool concept but it was never intended for people to make and distribute their own flavor of windows.
I see... Thanx! In the meantime I read the Hazar, Daz and co. thread and more about the re-arm and which Loader etc. I suppose I will have to re-check my old PC with KIS and the rest... I only wanted to test it first, on the old bucket... Others have tested it, too - nothing reported [RapidFind forum], so I presumed it's reasonable to assume it's OK... Mind you, it seems to me there was nothing else but W7 in that Faxcool version... I hope it is "kosher" and I am sure you would like to be wrong on this one but better be safe than sorry! I will download the repository version of W7 and learn more about how to safely do it [Loader 1.7.1 + anything else?], so my Acer Aspire 5920G gets a good version and all is dandy when I'm done... Cheers!
slmgr is harmless. The reason it is renamed is because the patch focuses on removing licensing. I will add syswow64 slmgr support next release
Hi, 1: I would appreciate x64 support. 2: Someone earlier said that after 3 rearms your literally f**ked up. I think thats not true. Why don't you set the reg-key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" "SkipRearm" from 1 to 0 ? Then you can rearm again. Or did I get something wrong?
This program patch some dll file from windows right? what if I run "sfc.exe /scannow" will that erase the patched dll?
HI, I just used removeWAT. After the reboot the ID under computer->properties was correctly removed. But slmgr shows me still the 30 days, so what will happen then?
thanx hazar, i tried using the latest remove wat file and now its not showing 30 days trial thing under my computer properties. but one thing, after this my sidebar gadgets are now not working properly. Now if i drag them to place it on my desktop its not comming. any help?
Someone repped me down for being frankenbuild They clearly don't understand a frankenbuild Nowadays it seems hacking yuor bootsector to include a modded grub loader to load a SLIC table is less frankenbuild that using windows commands to disable activation
It has been confirmed that the rearm is necessary I am updating now to add support for disabling syswow slmgr and have centred the UI buttons a little
Haz! watzwat! ^ Ah they have no clue! I've just run your latest RWAT 1.2 - lookin' good! Love how activation is totally removed even from visual! Ha! I remember some years ago having a copy of Office XP which I had a patch for, and activation just did not work - as if it was missing. That was the coolest! So I like this method the best - direct, does its job, and no faking OEMs etc! Awesome! Thanks again! Rep+!!
Means, that on my x64 pc i just have to restore WAT with removeWAT 1.2 and then download the new version. Then use that new version which supports syswow64. Right?