#MICROSOFT CONFIRMATION ID GENERATOR .DLL#

More than likely, not only has the key changed, but the algorithm has also changed because XP SP3 has more digits in the installation ID than XP RC1 did.ДЄs for the feasibility of breaking this. Quick check into the licdll mess: The decryption key mentioned by Licenturion/Fully Licensed in their XPdec tool for the SHA-1-based custom Feistel cipher could be confirmed present in XP RC1, but is missing from the XP SP3 licdll.dll. It also deletes winlogon.exe in dllcache but you can get that back if you just get a fresh copy of xp of the version you have installed and do sfc /scannow and it will come back again. 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.

#MICROSOFT CONFIRMATION ID GENERATOR .DLL#

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, :/

Microsoft confirmation id generator