I know that perhaps any or some of you despise antiwpa because it modifies system files but it clearly does the job and it works perfectly fine, it only modifies 1 file and that is just winlogon.exe, whats wrong with it? If you have xp 32bit, you should use wpakill 2.3.0 from may 2009 instead because it works completely fine, and is much more recent than the latest version of wpakill which is from late 2006. Click to expand.i've just tested it days ago and it works fine but kinda like s**t sometimes, i suggest you use wpakill 2.3.0 instead of this 'dll hooker', because windows product activation is not completely gone as it claims especially when you use it and then boot to safe mode with networking, you will have wpa whining at you to boot normally so it can 'activate' and then it resets the value in oobetimer, temporary fix for this is just to reregister the dll with this command 'rundll32 antiwpa.dll, DllRegisterServer' so that it puts the value back to what it was.īut anything else? it works just fine, theres no wpakill 2.3.0 for 64bit and ia64 versions of xp though, :/
