Open source Windows 7 product key checker

This is a small project I thought I would share with everyone since as far as I know there are no examples or open source projects that show how to do this.

I recommend using REALbasic 2007 Release 5 if you want to compile standalone executables, but be warned that the 2007 version is a little buggy and tends to crash a lot so make saves often. The 2010 (and up) versions are great but won't compile you standalone executables. However, if you are just planning to simply port the code over then use a newer edition.

** To paste in a key hold Ctrl and press V.

Removed due to a DMCA complaint.

 

The newest 2009 build won't compile you a standalone executable, although the 2009 build is much more stable.

I'm sure there will be conversions of the code done in different languages soon enough, I don't mind if anyone wants to post the converted project here too!

 

I say go for it, any code sharing of this function I encourage as there are virtually no working examples that I know of found online. So even if done in DOS the code itself would be great to share

 

@ cyclops

Ctrl + V

I wasn't joking when I said this was a quick bare-bones project, it was just some test code that I had spare. I was going to add key checking to my loader application but with it locking the UI up (even while in a thread!) it rendered it useless. Everyone elses key checker seems to lock up a bit too so I guess it's to do with the declare itself taking ages to reply back with some content.

 

Good one Daz, will this run in windows or is it for mac

Sabresite that would be cool, ive recently started using vb 2008 - can it be converted to this.

Alfa

 

@ Alfa
As the declare itself is strictly Windows based then it's one that won't run on a Mac. This should be able to be converted to .NET without any problems

 

Cool thanks Daz

 

Interesting, I'm not sure if thats normal or not but based off data tests with other keys I guess it is. I don't have a MAK key to test with but the easiest way is to debug the line "Dim PID As String" and then look at the contents of the CoreData memoryblock, if you see the edition then it's just how my code pin points the position of text.

Theres one minor fault in the source so I'm going to fix that and reupload a version. The fault is with the following:

Code:

Private Function ConfigPath() As String
  Dim OldVal As Integer
  //Disable path redirection for 64bit OS's
  Soft Declare Function Wow64DisableWow64FsRedirection Lib "Kernel32" (OldValue As Integer) As Integer
  If System.IsFunctionAvailable( "Wow64DisableWow64FsRedirection", "Kernel32" ) then
    Call Wow64DisableWow64FsRedirection(OldVal)
  End If
  Return SpecialFolder.System.AbsolutePath+"spp\tokens\pkeyconfig\pkeyconfig.xrm-ms"
  //Re-enable path redirection
  Soft Declare Function Wow64RevertWow64FsRedirection Lib "Kernel32" (OldValue As Integer) As Integer
  If System.IsFunctionAvailable( "Wow64RevertWow64FsRedirection", "Kernel32" ) Then
    Call Wow64RevertWow64FsRedirection(OldVal)
  End If
End Function

The revert function never gets called because we have already returned, the fixed code should look like this:

Code:

Private Function ConfigPath() As String
  Dim OldVal As Integer
  //Disable path redirection for 64bit OS's
  Soft Declare Function Wow64DisableWow64FsRedirection Lib "Kernel32" (OldValue As Integer) As Integer
  If System.IsFunctionAvailable( "Wow64DisableWow64FsRedirection", "Kernel32" ) then
    Call Wow64DisableWow64FsRedirection(OldVal) //64bit Fix
  End If
  Dim S As String = SpecialFolder.System.AbsolutePath+"spp\tokens\pkeyconfig\pkeyconfig.xrm-ms"
  //Re-enable path redirection
  Soft Declare Function Wow64RevertWow64FsRedirection Lib "Kernel32" (OldValue As Integer) As Integer
  If System.IsFunctionAvailable( "Wow64RevertWow64FsRedirection", "Kernel32" ) Then
    Call Wow64RevertWow64FsRedirection(OldVal) //64bit path handler
  End If
  Return S
End Function

 

The above link should list a few versions, the older 2007 version being the best to compile a single executable but it was a pretty buggy build and would randomly crash every now and then so always make saves.

If you go for a newer version then I could probably work on doing a public cr4ck as I have cr4cked the application myself.

 

Hey pkaji123,

I'm not sure how to do it on Windows XP, I think it uses pidgen.dll rather than pidgenx.dll. I will look into it when I'm next on my XP partition