One queston...Why? You have installed Daz's Windows Loader so you should totally ignore RemoveWat (No need to have them both)
for curiosity i want to know more as possible of these cracks and maybe i will choose this removewat in future if something will go wrong with win7loader
Yeah, secr9tos is OBVIOUSLY a kid, that's why he is a respected developer who made the oem driver and helped with various aspects of RemoveWAT and made lots of it possible. Oh wait, is he still a kid? Your logic, to be frank, is stupid. I'm pretty sure he knows a LOT more about assembly, cracking and reverse engineering than you ever will. His post count doesn't mean everything, he's ALSO a talented member.
I'm very sure Hazar has not included anything nasty in his app. I'm also sure it's the Virus Scan Companies doing a little favour for M$ as well, just as they did when they detected the XP Keygen as something nasty which was written in standard Visual Studio 6.0 MFC and was perfectly safe. We'll have to wait until Hazar reports back if he thinks anyone has tampered with his app.
Are you kidding? My post-count has nothing to do with my point of view. I don't underestimate you but to me it seems like you are a sort of "attention w*ore" or troll. Choose what you like best. I've written three Windows 7 & Windows Server 2008 R2 activators, I'm part of Chew7 project, working together with other ppl on other projects, etc... AND YOU call me a "kid" or "script kiddy"?? What are you doing? Coding viruses with batch? This is my last comment on this issue... coz otherwise I'll get p*ssed.
LOL,even a child can do that better take up some courses..and he calls himself as a developer, i bet u s-irl.
Hopefully someone can help answer. The RemoveWAT resources contains 32-bit and 64-bit files. My problem is since this application was compiled under 32-bit, the assumptions where the 64-bit files were deployed is in question. Code: this.ProgressBar1.PerformStep(); if (File.Exists(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll.bak")))) { if (File.Exists(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll")))) { this.Takeown(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll")); File.Delete(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll"))); } this.Takeown(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll.bak")); MyProject.Computer.FileSystem.RenameFile(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\System32\slwga.dll.bak")), "slwga.dll"); } this.ProgressBar1.PerformStep(); if (File.Exists(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll.bak")))) { if (File.Exists(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll")))) { this.Takeown(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll")); File.Delete(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll"))); } this.Takeown(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll.bak")); MyProject.Computer.FileSystem.RenameFile(Conversions.ToString(Operators.ConcatenateObject(this.windir, @"\SysWOW64\slwga.dll.bak")), "slwga.dll"); } this.ProgressBar1.Value = Conversions.ToInteger("100"); Hazar any idea? I'm just trying to verify that things are put in place where they should be. Too lazy to crack anything these days. Thanks
Uhm... It's compiled to run as 32bit on a 32bit machine and 64bit on a 64bit machine. If you run it on a 64bit machine it'll appear as a native 64bit process but if you run it on a 32bit machine it will still work. So no idea what you mean, sorry. It's possible an old version is floating about with the compiler settings wrong, though.
Do you have a 64-bit compilation version of RemoveWAT.exe? I dumped the PE where it shows 32-bit addressing. The same .exe cannot be used on both systems unless you take care of NTDLL's system path redirection problem. The NT DLL will screw with your path once it detects 32 bits.
hello there, this is a very interesting tool and i can say it cause i am using it now also a big thanks for the developers of it. what i wanted to ask is if ANY windows update can possibly "find" and disable this application or even worse "lock" windows from even being able to log in. i am asking this so i can know if installing ANY windows update can do something of the ones mentioned above to my windows 7 x64 machine! so am i safe to install all windows updates? should i install only some of them? (if thats the case what is the category of them? for example i shouldnt install the security ones?)
Install any update with this tool. Windows doesn't usually lock when "caught" it just gives warning maybe couple hr use then restarts.
you mean that if it gets "caught" then it will restart its self every time after that in a couple of hours? can this get fixed?
Hey Hazar i must say hats off to you on the the removewat.... I have been usen it for a couple of months but now im getting the popups to validate and or my version is not genuine .. Do i not have the right removewat or?? Thanks