Windows 2003 & XP & LH Anti Product Activation Crack v2.1.5.0.0

The crack will patch some bytes in your

winlogon.exe and totally disable the

Windows Product Activation Check.



Tested with winlogon.exe build:

Windows XP 2600.0 (Retail)

Windows 2K3 3790.0 (Retail)

Windows XP 2600.2180 (SP2 RTM)

Windows XP 2600.1106 (SP1)

Windows 2K3 3790.1218 (8.7.2004)

Windows Longhorn 4008 or 4015(not tested by myself)



This version uses a generic patch engine

which supports all current version of Windows

and hopefully all future ones. :)





The Options

===========



1. Read all about the options.

2. Don't change anything you without a reason.





* Apply OOBE Fix

This applies the Out Of Box Experience ->OOBE Patch

which removes the 'Activate Windows' link from the

start menu and makes the Activating Windows Dialog

saying 'Already Activated'



Note: This is more a cosmetically fix and really not

needed for the patch to work properly.





* Apply WPA Fix

This removes the WPA-Check in Winlogon.exe.

If you want to get rid of the Windows Activation

this MUST be Enabled !

Disable this if you just want to undo the OOBE-Fix.



Note: However you can use this program also to

decrypt and unprotect other MS-Files

like DPCDLL.dll or LICDLL.DLL. So if you

do so disable this option.



* Replace Msoobe.exe with AntiWPA

Replaces the "Let's Activate" program with the AntiWPA.

So incase you installed some servicepack which removes

the patch and you are force to activate now simply click

'Yes' and instead of the activation program the patch is

started...

Incase you click on the "Activate Windows"-Link in the

start menu both the patcher and the normal 'normal'

activation program will be started.

<<< End Of 'Normal' user options !



* Remove selfcheck blocks

Note by pressing the 'Apply' button the self checks are ALWAYS

disable via 'correcting' the pointer.



This option will additionally overwrite the self check block

calls in the program code with the value 90 (NOP=No OPeration)

and will improve the readability of disassembly.



'NopOut completely' filles entired block with 0x90 Nop

If your disassembler has the option to hide 'fillcode' like nop

this is the best choice



'Add short Jmp at the beginning to jump over the Nop's'

If you like it simple choose this



'Fill with 'long' asmcodes with don't take that much

lines in the disassembling than the nop's '

The nop's will be relaced with the 10 Byte command

mov [ffffffff],ffffffff. Of course these command are not

executed and skipped with a short jump at the beginning.





Note: This option is absolutely not necessary for the patch to work.





* Remove crypt blocks

This will decrypt the crypted program parts of the input file and

write them back to into the exe and do some other fixes to keep the

File executable. If you want to disassemble the file enable this one.



Note: This option is absolutely not necessary for the patch to work.

Currently this option is unreliable so keep in mind that in some

causes it will corrupt/crash the exe.

(After using this my winlogon need the about 4 manually crashfixes.)





* Debug: Save decrypted code to *.bin

Writes each decrypted program parts into a file with the

address as filename looking like this: 2C18D.bin, 3678B.bin...





* Debug: Save decrypted code to exe

Writes each decrypted program parts back into the file.

If the option 'Remove crypt blocks' is not check just the decrypted

RAW-Output is written into the exe. (After you enable this you

have to right click on 'Apply/Browse' and open the file you want

to decrypt)



Note: This option is dangerous!

Without having 'Remove crypt blocks' option enabled this will

make crash the input file crash for sure.

This option is absolutely not necessary for the patch to work.





* Debug: Verbose Output

Output Debug information

This may be helpful to identify some problems.





The Buttons

===========



[Apply/Browse]



Left click applied the selected Tasks in options.

Note: The selfchecks of winlogon.exe are always disabled

even if no options are selected.



Right click to change the path to winlogon.

Good for to apply the patch other network

to some other OS or for preparing a winlogon.exe

before creating a windows Setup CD





[Restore]

Undo the selected tasks in options.

So if you want to undo only the 'MSOOBE-Fix'

uncheck all other options expect 'MSOOBE-Fix'

and then press the restore button





==================================================

F A Q - Frequently Asked Questions

==================================================





????????????????????????????????????????????????????????????????????????????????

After I have installed a Service pack the Activation Reminder

counting down the days is show again.

????????????????????????????????????????????????????????????????????????????????



You must reapply the patch every time after you installed a servicepack and

everything will be fine :)



Note: The Patch don抰 慳ctivated?Windows it only removes the check in

winlogon.exe

which test if windows is activated or if it抯 still in the evaluation period

and force you to logoff if something is wrong.



When you install a servicepack winlogon.exe is normally overwritten by a new

Not patched Version. So you need reapply the patch.

Usually the servicepack reset the trial counter so it will restart at 30 days.





????????????????????????????????????????????????????????????????????????????????

I can抰 start patch because my evaluation period expired and

Now I抦 unable to login.

????????????????????????????????????????????????????????????????????????????????



You can still login in safe mode even if your evaluation period expired.

Press F8 right after the Bios boot screen and select Safe Mode

(Without Network support) menu now windows should boot in safe mode and you can

Login and apply the Anti-WPA-Patch.



Note: Since no Network support is available in safe mode no Internet or Network

Is available so it抯 good to have the patch somewhere on the hard disk or on a

floppy disk?

If you select Safe Mode (with Network support) you are unable to login due to

Activation is necessary.





????????????????????????????????????????????????????????????????????????????????

Well windows says that it was activated but when i restarted my pc,

a pop up message appears and says that i have only 25 days to activate windows.

????????????????????????????????????????????????????????????????????????????????

This means the patch is not active.

Or only the oobe-fix was applied but not there was an error applying

the real patch -> see FAQ: know problem asian system



After you applied the patch start it again -now it should say 'Already applied'.

If not start it again and check is there are any errors in the log output.

If there are no errors, but you still don't get 'Patch already applied' disable the windows systemfile protection manually.



Background:

Everytime you login the activation is done and the days remaining are written to

HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWPAEvents[OOBETimer].

(Note: they're only written not read from there so changing this has absolutely

no effect on activation.) Also a special value means Activation done.(->xp-wpa-crack.txt). msoobe.exe and msinfo32.exe only use this value to determinate whether Windows is activated or not. So right after the Patch everything looks fine the Activation Dialog shows 'Already Activated'. But if you login the OOBETimer value is 'updated' -since the real check is still active- and trial countdown continues...







????????????????????????????????????????????????????????????????????????????????

I want to change my CD-Key - but msoobe.exe also says

'Already Activated and don't show the Activation Dialog

????????????????????????????????????????????????????????????????????????????????



Enable option 'Apply OOBE Fix' and

Disable option 'Apply &WPA Fix' -to keep the WPA-Patch active-

then click on the 'Restore Backup' Button



PREVIOUS VERSIONS:

Start regedit and go to

HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWPAEvents[OOBETimer]

Edit this and set Last Byte to FF.

Start this -if the Activation are delete- to show the Activation dialog:

%SYSTEMROOT%system32oobemsoobe.exe /A







????????????????????????????????????????????????????????????????????????????????

Is it possible to integrate WPA_KILL.EXE in the WinXP setup-routine?

I have a WinXP pro setup CD (sp2 integrated).

????????????????????????????????????????????????????????????????????????????????



Integrating the AntiWPA Patch in the Windows Setup:



1. Extract [WindowsSetupDir]i386winlogon.ex_ to a temporary Dir.

(Winrar or winace will do the job - or rename it to winlogon.cab and

double-click on it - to use the build-in WindowsCabExtract)



2. Apply the WPA Crack to the file.

Right click on 'Apply/Browse' and choose the file.

(To unlock all buttons of the WPA-Patch right click on 'Quit')



3. Repack winlogon.exe an put it back in the installation folder

Use Winace (and choose MS-Cab as compression method) and name

the packed cab-file winlogon.ex_.

Or use the makecab.exe(included in Windows XP) start cmd.exe in the dir

winlogon.exe is in and Enter:



makecab winlogon.exe



After that you will get winlogon.ex_ as output.



PREVIOUS VERSIONS:

In previous versions the PE Checksum of the file wasn't updated by the patch.

This caused setup to reject winlogon.exe during installation.

But this has been fixed in this version.





Manually OOBE_Fix for WindowsSetup

----------------------------------

Since I see people integrating the patched winlogon.exe into windows setup are

perfectionist here's a hint how to may you get rid of the activationlinks in

the startmenu (-untested-):

Ok unpack and edit syssetup.inf



1. search for

[StartMenuCommon]

and delete this to avoid the activate link in START

%oobe_desc% = oobemsoobe.exe,"%%SYSTEMROOT%%system32oobemsoobe.exe

/A",,0,"@%SystemRoot%system32oobemsoobe.exe,-2001","%SystemRoot%system32oob

emsoobe.exe",2000

(btw you can also delete this unless %windowscatalog% link section if you

like)



2. In SystemTools it's the same

[SystemTools]

%oobe_desc% = oobemsoobe.ex...



Just for better understanding the inf-file format at the end is defined what the

variable "oobe_desc" is:

oobe_desc = "Windows aktivieren"

This was were I first stepped when I searched for "Windows aktivieren" in

C:windows

The second was to look for oobe_desc...



No-CDKey-Patch for WindowsSetup

-------------------------------

- Since I got some positiv feedback about this I decided to publish this.

But so far I'ven't test it myself-



This will make the WindowsSetup to accept any -even a blank- CDKey

Get "http://antiwpa.tk/Other/cracked pidgen for setup.rar"

Pack it pidgen.dll with cab-pack to pidgen.dl_ as decribed above

and put it in the I386 setupdir.

That's it.







????????????????????????????????????????????????????????????????????????????????

What changes does this patch to my System and how to undo it?

????????????????????????????????????????????????????????????????????????????????



1. It modifies c:WINDOWSsystem32Winlogon.exe and creates a

backup named Winlogon.bak

UNDO: Rename Winlogon.exe -> Winlogon.OUT

Rename Winlogon.bak -> Winlogon.exe

After Reboot you will be able to delete Winlogon.OUT if you like





2. The RegistryValue

HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWPAEvents[OOBETimer]

is set to a fixed value as it is activated.

UNDO: Edit this with Regedit and set Last Byte to FF.

This will 'DeActivate' Windows



Note: Normally this value is written (not read!) by winlogon.exe on

every start up just as information for MSOOBE.

This value has no effect on the real Activation.





3. The 'Activate Windows' Link from the Startmenu is remove

UNDO: StartExecute:

rundll32 setupapi,InstallHinfSection RESTORE_OOBE_ACTIVATE 132 syssetup.inf





4. 'Replace Msoobe.exe with AntiWPA' renames your original msoobe.exe

to msoobe.com and copies it self to system32oobemsoobe.exe





Other Changes:

HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetup

"SourcePath" and "ServicePackSourcePath" will be temporary delete during the

patch

and (if nothing really bad happens) restored if it's finished.







????????????????????????????????????????????????????????????????????????????????

How to set another path to Winlogon.exe?

????????????????????????????????????????????????????????????????????????????????



Right click on the 'Apply/Browse' button.

If the Patch is already and the 'Apply/Browse' button is greyed out

Right click on the 'Quit' button to force unlock all buttons.



Note: You can also use the Windows Anti WPA Patch to de-protect

(Remove SelfCheckBlock SCB) from other protected

Microsoft exe and dll's:

For ex: licdll.dll, DPCDLL.dll or Windows PLUS! Pack Executables

Of course the WPA-Patch is skipped in this case.





????????????????????????????????????????????????????????????????????????????????

The Patch doesn't work after I rebooted, the WPA Reminder pops up again.

Also during the Patch the Windows Systemfile Protection Dialogbox didn't

come up.

????????????????????????????????????????????????????????????????????????????????



Maybe the Patch was undone by the Windows File Protection.

To check if the patch is still active start the Windows Anti WPA Patch again and

check if it says 'Patch already applied'.







????????????????????????????????????????????????????????????????????????????????

How to disable this damn Windows File Protection(WFP)?

????????????????????????????????????????????????????????????????????????????????



There is no really official way to disable this



This is an undocumented setting worked for recent windows versions:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

SFCDisable=0xffffff9d



BUT: It was removed in Windows 2000 Service Pack 2 and in Windows XP!

When you restart your computer, the System event log will contain Event ID

64032, "Windows File Protection is not active on this system."



SFCDisable (REG_DWORD)

0 = enabled (default - WinXP Professional)

1 = disabled, prompt at boot to re-enable - Require a kernel debugger to be

hooked up or this will be ignored!

2 = disabled at next boot only, no prompt to re-