Download Windows 2003 & XP Anti Product Activation crack




added to the siteMay-16-2009
rating8

windows2003andxpantiproductactivationcrack.zip (30323 bytes)

namesizecompressed
file.diz 807 404
readme.txt 13152 4874
WPA_Kill.exe 73728 24735

file.diz

-======================================-
          Windows 2003 & XP 
   Anti Product Activation Crack 1.6.2
-======================================-

The crack will patch some bytes in your 
winlogon.exe and totally disable the 
Windows Product Activation.
Nothing else will changed. 

Tested with winlogon.exe build:
  Windows XP  2600.0    (Retail)
  Windows 2K3 3790.0    (Retail)  
  Windows XP  2600.2180 (SP2 RTM)
  Windows XP  2600.2142 (SP2 RC1)
  Windows XP  2600.2120 (SP2 RC1)
  Windows XP  2600.2096 (SP2 Beta)
  Windows XP  2600.1106 (SP1)
    
  
  

A T T E N T I O N :
Some crackhost may have added 'extra' or 
'premium content'.
To keep your PC clean from dialer or
dialerloader only start 'WPA_Kill.exe'.


   

readme.txt

-======================================-
          Windows 2003 & XP
   Anti Product Activation Crack 1.6.2
-======================================-

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.2142 (SP2 RC1)
  Windows XP  2600.2120 (SP2 RC1)
  Windows XP  2600.2096 (SP2 Beta)
  Windows XP  2600.1106 (SP1)




==================================================
	F A Q  - Frequently Asked Questions
==================================================




??????????????????????????????????????????????????????????????????????????????????
	I got 'ERROR: Unknown Version of winlogon.exe'.
	Can you include this version in your WPA-Patcher ?
??????????????????????????????????????????????????????????????????????????????????

Well please try the offsetlocator button to patch this new Version. Since Version 1.4 I added a heuristic search for offset locator which should find the right offset by default and highlight it.
So -after you read the warning- just double click on the highlight Offset on the List to set this as new patch-Offset.

If this is not a Beta or Release Candidate Version send me your ûunpatched- Winlogon.exe by email and add if the default offset (found by the for offset locator) works.




??????????????????????????????????????????????????????????????????????????????????
	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]\i386\winlogon.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.




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

1.It modifies c:\WINDOWS\system32\Winlogon.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
  HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents\[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: Start\Execute:
        rundll32 setupapi,InstallHinfSection RESTORE_OOBE_ACTIVATE 132 syssetup.inf

Other Changes:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
"SourcePath" and "ServicePackSourcePath" will be temporary delete during the patch
and (if nothing real bad happens) restored if it's finished.




??????????????????????????????????????????????????????????????????????????????????
	I want to change my CD-Key - but msoobe.exe also says
	'Already Activated and don't show the Activation Dialog
??????????????????????????????????????????????????????????????????????????????????

Start regedit and go to
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents\[OOBETimer]
Edit this and set Last Byte to FF.
Start this -if the Activation are delete- to show the Activation dialog:
%SYSTEMROOT%\system32\oobe\msoobe.exe /A




??????????????????????????????????????????????????????????????????????????????????
	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.
      Well the crypted code parts stay crypted ûsorry :(- only the self checks
      all over the code are removed to make it possible to
      debug/modify these files.




??????????????????????????????????????????????????????????????????????????????????
	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_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
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-enable - Require a kernel debugger to be hooked up or this will be ignored!
4 = enabled, with popups disabled (default - for all Server Windows)
More about this and how to re-enable the 'SFCDisable=0xffffff9d-setting'
 -> http://www.collakesoftware.com/aboutwfp.htm
To make this more flexible here is a searchÆnÆreplace patch:
(Rename sfc_os.dll to sfc_os.OUT; copy sfc_os.OUT to sfc_os.dll)
Open sfc_os.dll in a hexeditor
Search for  : 83 f8 9D 75 08 33 C0 40
Replace with: 83 f8 9D EB 08 33 C0 40

So this is were it comes from:
           A1 D8E1C376     MOV     EAX, [SFCDisable]
Patch- > 83F8 9D         CMP     EAX, -63			; = 0xffffff9d !
Search > 75 08           JNZ     SHORT DonÆt_Set_SFCDisable_=_1
Data   > 33C0            XOR     EAX, EAX
         > 40              INC     EAX
           A3 D8E1C376     MOV     [SFCDisable], EAX
:DonÆt_Set_SFCDisable
Btw this fragment is the reason 0xffffff9d donÆt work anymore û so alternatively Nop Out (=overwrite with 0x90) that bastard



Well I found a real simple way to disable this for sure:
Rename c:\WINDOWS\system32\sfc.dll to sfc-OUT.dll to something else
After Reboot the WFP is disable.
BUT I advice to rename sfc-OUT.dll back to sfc.dll soon because I notice
That you canÆt install any new Hardware Device Driver because syssetup.dll
Statically imports sfc.dll and fail to load if sfc.dll is not found.
 so files which import
 Sfc.dll will start again



?????????????????????????????????????????????????????????????????????????????????????????????
	How you access/modify the winlogon.exe file while the winlogon process is running ?
	I only saw you are using standart API calls but I must have missed something...
?????????????????????????????????????????????????????????????????????????????????????????????

How to modify an File (like winlogon.exe) while it is in use:

1.Rename winlogon.exe -> winlogon.bak
  That's the most important thing about that. You can't delete or
  modify a file that's in use, but you can RENAME it! (under Win9x
  this don't work. But there you can rename the dir the file is in...)

2.Copy winlogon.bak -> winlogon.exe

3.Now you can edit winlogon.exe. Of course you can't delete (or
  modify) winlogon.bak as long as it is in use.
  But you surely want to keep an backup of it, don't you?

Oh i almost forgot to mention an other annoy thing:
>The Windows system File Protection (WFP) <
When renaming/modifying winlogon.exe as described above the WFP will immediately restore the original file without any warning(There will just be an entry in the eventlogger - but how cares about this).
To avoid this:
* Delete all files in C:\windows\system32\dllcache\*.*
* Rename the path were installed your last Servicepack or the path to
the windows installationfile to something else like
'D:\installs\WinXP_SP2' -> 'D:\installs\WinXP_SP2.out'
So the WFP won't file them to restore

Well the WPA-Patch don't remane your Windowsinstallationpath it deletes temporary the path to this in you registry and restores it after the patch (actually after you clicked on the OK button of the messagebox).
These Registrypaths are:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
"SourcePath"= "D:\installs\WinXP_CD"
"ServicePackSourcePath" ="D:\installs\WinXP_SP2"

----------------------------------------------------------
Just an hint to see if the patch worked without to Reboot:

1.Apply the patch
2.Logon as an other user
(But don't log of - choose change/disconnect user)
3.When you login just see if the patch works...
... or if not this damn
'You haven't activated your Windows yet...' message

(4.If you logoff the first user now 'winlogo.bak' is no long in use
and you can delete/modify it)

Ah and to get an better overview about the processes which are running on your machine use this: http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
And next time you can't delete a files use 'search handle' and enter the filename then close the handle(=file) or kill the process...




??????????????????????????????????????????????????????????????????????????????????
PREVIOUS VERSIONS:
	The patch don't work - if i click on the 'Activate Windows' link in the
	startmenu, it says Windows isn't activated and that there are only xx days left.
??????????????????????????????????????????????????????????????????????????????????

This patch didn't stop the trialcounter nor it will 'Activate' your Windows.

The WPA-Patch fixes the condition jump which decides whether windows was started in safe mode
and the activion check should be skipped or if it was started in normal mode and it should be done.
So in short it will make winlogon.exe to skip the is-Windows-activated check when you logon.

To see if the patch work wait about one minute after you logon -
if the Activationreminder ballon in the traybar DON'T pop up - the patch IS working.
Some other things to see that it works
The messagebox that reminders you to active if there are only 5 days left and
The messagebox that says your not allowed to logon until you active will be away.

So patching msobmain.dll just to make it say it's activated is only additional overheat and
also may cause some problems. Maybe if you want to change your CDKey and you don't reach the CDKEY change dialog because it says already activated...
Ok what i need to do is to include some FAQ-info text in the next version about that issue.
Maybe i will add a "Let's Activate Windows" force true patch if there is such a big need for this
I mean if this will make someone sleeps better at night - is enough for a good reason.





------------------------------------
Histroy

1.6.2 Sep'04
  Added MSOOBE Actiation Fix
  Added Readme.txt

1.6 Aug'04
  Added support for WinXP SP2 2180

1.5 Jul'04
  BugFix: Changes set by offsetlocator were not written to disk

1.4 Jun'04
  Added support for WinXP SP2 RC1 2142
  Added heuristic search for offset locator

1.3 Jun'04
  Added support for WinXP SP2 RC1 2120
  smaller changes

1.2 Apr'04
  Patch recoded in Visual Basic 6
  Added generic checkblock disabler
  Added offset locator to support unknow versions
  Added support for WinXP SP2 Beta and Win2K3
  Improved Windows File Protection support

1.1 Nov'03
  BugFix: SP1 crashed when returning from standby
  Improved Windows File Protection support

1.0 Sep'03
  First release using the apatch-engine