PIDKey Lite by Ratiborus, MSFree Inc.

Program description
Program PIDKey Lite is intended for browsing, updating and saving in database information about MS
products keys.
It allows to change PIDKey by Ratiborus, Ultimate PID Checker by janek2012 and VAMT. Program PIDKey
Lite is assignee of PIDKey and has taken from it the best ideas. The main feature of the program is
creation SOL-database unlike PIDKey, where the database, in fact, have been kept in text files. Program
allows to add new keys in two modes (modes of adding keys would be described later) and check them
as well as find in database necessary keys, update information about them and (or) transfer them to
blocked ones.

As part of the program executable files: PIDKey Lite x64.exe, PIDKey Lite.exe and database file
pkbase.db. PIDKey Lite x64.exe checks all keys; PIDKey Lite.exe NOT check the keys x64 group
Windows XP. PIDKey Lite.exe has a special version of pidgen.dll (earlier version) for running on
Windows XP. If you delete the database file pkbase.db, the new empty database will be created when
the program starts.

Hotkeys
F2, F3, F4 - management of three major program buttons
Shift+The left mouse button on the key adding window - Forced adding keys to verify if even they are in
base
Ctrl+1 - Check all keys
Ctrl+2 - check only XP key
Ctrl+3 - check only Vista, 7, 8, 8.1, 10, servers key, Office 2010-2016
Ctrl+4 - check only the keys with N - keys are checked only for Win 8, 8.1, 10, server 2012-2016, Office
2013-2016.
Ctrl+R - database repair
Ctrl+U - rename folders group Microsoft Windows XP key.
Attention! Ctrl + 1; Ctrl + 2; Ctrl + 3; Ctrl + 4 settings saved before applying other settings. When you run
the program reflects the setting key validation.

System requirements:
OS: Windows XP / 7 / 8 / 8.1 / 10
.NET Framework: 4.0
Availability of the Internet is necessary for finding available activations of MAK keys. Program doesn’t
need installation and it is totally portable. The database already contains GVLK- keys, uncertain keys and
blocked keys from reliable sources.

Program interface langueges: Russian, English, Persian (Iran), Spanish

For choosing language of the interface executable files may be run from the command line with
parameters: /ru | /en | /ir | /es

Program startup parameters

Starting with version 1.54, the program can be started with the /unpack option. In this case, the
configs will be unpacked into the program folder in the pkconfig subfolder. Subsequent
launches of the program with uncompressed configs will occur faster.
The transition to the new version after the version upgrade.
To switch to the new version you must:
- unpack the new version from the downloaded archive into a folder with a new name;
- rename database pkbase.db file bundled with the new version, for example, pkbase_NEW.db
(this database may need to add it from the blocked and uncertain keys);
- copy the file to its base pkbase.db from the old version of the software folder to the new
version of the program;
- to launch a new version of the program (with your base) and immediately repair the database
(Crtl+R) for possible changes to the database structure.

Description of the program interface

After running file PIDKey Lite.exe (or PIDKey Lite x64.exe), you will see:

Here you immediately can see:

-amount of keys in database
-amount of blocked keys
-amount of keys in queue for checking
Description of the launch window.
1 - window for inputting keys
2 - button “Start”/”Stop” of checking of added keys
3 -button for mode of browsing key base
4 - button of selection of adding keys mode
5 - button of adding keys for checking from file (new in version 1.24)
Buttons 2, 3, 4 are controlled by a mouse and keys F2, F3, F4.
7 - "Help" button (in the figure is pressed). Help can also be accessed by pressing F1.

Adding keys for checking

For adding keys for checking you should copy keys to clipboard and click the left mouse button on the
window for inputting keys. As a result keys for checking would be added to a queue:
Pressing of button 2 - “Start” starts checking of added keys, herewith button 2 has changed:
In the checking window is written information about checked keys , and in log the time of starting of the
program and information about checked keys are written. Starting from version 1.27 while updating
information about MAK keys, information about blocked MAK keys is written in log.

You can browse Log- file right from the program by pressing button “Log”. Herewith for browsing of
Log the default OS text editing program would be called. Pressing Ctrl+Log deletes the Log file.
Attention! Starting from version 1.26 Test1: Holding the button SHIFT you can forcibly add to the queue
fro checking (re-checking) keys that are already in database
Attention! Wait for the end of checking the currnt key!

After stoppng and end of checking the currnt key you can close the program, although in the database
there are still unchecked keys in a queue (in the picture – 4 keys).
We make a new start of the program.
On the right side above button 5 has appeared. This is the button for switching modes of inputting new
keys for checking with modes.
- If button is not pressed, new keys for checking are added for those ones already in queue
- if you press button 5, the second queue would appear. It is used for urgent checking of some new keys.
We press button 5 and see, that in window 1 of inputting keys appeared the second queue of inputting
keys (was “5 keys added”- become “0 keys added”)
Now you can add keys for urgent checking (for example 5 keys added)
By pressin button “Start” we begin checking these 5 keys.

After checking is finished, you can close program or press button 5 and go to mode of checking keys in
a queue.
By checking button 2 –“Start” we begin to check keys left in a queue.
We wait for finishing of checking (or stop checking) and close the program. In case the checking is
stopped and program is closed, keys stay in a queue and can be checked on the next launching of the
program.

Adding of keys for checking from the text file

We prepare the text file with keys, for example KEY.txt. Keys in file may be located in any order with any
other text in chaos.
For adding keys for checking from the text file press button 6. The browsing window will be opened
where we point at file KEY.txt:

Keys from the text file would be added for checking (7 keys addeed):

By pressing button 2 we begin checking them:

Starting with version 1.36 in PIDKey Lite an opportunity to check Windows XP / Server 2003 keys (except
x64).
To do this in the folder \Windows\Temp\pkXXX\ xp added to the library, containing information about
these keys. If the keys are Windows XP / Server 2003, you do not need the xp folder with libraries can be
removed and then Windows XP keys / Server 2003 will get when checking in undefined.
Recommendations for verifying uncertain keys for the presence of Windows XP / Server 2003 key.
To speed up the check, remove the folder \Windows\Temp\pkXXX\$1; \Windows\Temp\pkXXX\$2;
\Windows\Temp\pkXXX\$3. Or use the keyboard shortcut in the active window: Ctrl+2 - check only XP
key. Then undefined keys will only be checked for the presence of Windows XP / Server 2003 key. It
should be borne in mind that a large number of keys uncertain, so it makes sense to verify the key
portions.

Working with key database

We launch the program. By pressing button 3 (button for browsing key database) we go to key database:
In databse you can browse, allot, copy (holding the Shift key only copied keys without descriptions),
check, move to blocked and delet keys, and also serch keys. Search looks for keys, folder names
(deskripshinah) and in the comments. Key search also works on the SKU ID.

As a result of search we have:

Starting from version 1.25 it is possible to search not only by key itself or its part, but also by description
(or part of the description) of the key:

As a result of search we have:

Double click of the right mouse button on the key allows to see all information about the key.

In database it is also possible to update information about MAK keys. To do this, you should click the
left mouse button on the key to allot it and in appeared menu choose “Update information of MAK
key”. Updating of information would be made . You can also update information about all MAK keys in
database by choosing in menu “Update information of ALL MAK keys”.
Attention! If there is a lot of MAK keys in database updating of information can take a long time. In this
case updating can be stopped by pressing button “Escape” on the switchboard.

In the loaded OS, while in the database, you can choose not blocked keys for OS and Office and install
the keys or install keys and activate the OS and Office. To do this, right click the mouse on key, and
select from the menu "Install Key" or "Install Key and Activate." Installation keys and activation of
products M$ is using the standard commands for setting keys and activation products (slmgr.vbs and
ospp.vbs).

For exit from the database press button 2:

Choosing of the adding keys mode
You can add keys from the clipboard by clicking left mouse button on the input box 1, as well as from file
by pressing button 6 and indicating the text file with key. For choosing the adding mode press button 4:

Mode on default is –“Add keys to a queue”.

You should use mode “Add keys to the blocked” carefully.

If you are sure that keys you want to add to blocked are already in database, just add these keys to
window 1 and these keys would be moved to blocked. Notice: really they are only marked as blocked,
but information about the is saved in database (for example, MAK Windows 8.1 etc). In case that among
the keys adding to blocked there are ones that are nor in the database, those keys would be checked
and determined as blocked, and if among them there are Invalid keys, those would be moved to
Invalid. If adding key is already in blocked, it will be skipped.
You should use the mode “Add keys to Invalid” carefully. You can fearlessly add invalid keys from
PIDKey database. If added key is already in Invalid, it will be skipped. Newly got keys should be checked
in ordinary way.

Starting from version 1.25 Test5 in the inset of adding keys mode appeared function “Add another key
database”. While using this function only keys missing in operating database would be added; if key
exists in operating database, it would be skipped. Status of the neewly added keays is not checked in
terms of blocking. The operating database has the priority. If key is blocked in it, let it be. As a
recommendation you can use the newest database as operating one and the other (probably your own)
plug in as a database for updating.
Starting with version 1.45:
- When you add from another database, if the key in the old one was in an undefined one, and in the
new one it is defined - it is added to the database leaving the undefined ones.
- If the new key is blocked, it is translated into blocked.
- While holding Ctrl while clicking on the yellow folder "Add another key database", all comments are
copied from the new database, even for keys that were already in the database.

Saving the database of keys

Starting from version 1.26b ther is an option of saving key database.For this you can use button “Save
Key Database”. Database is saved in program folder in format pkbase_15_01_2017-12_50_11.db
(date_month_year_hours_minutes_seconds).

Comments
Comments can be added and removed directly to the key (or multiple keys) in the key and immediately
to the list of keys. To do this, the window "Add a comment for keys" comment is entered, the keys are
copied to the clipboard, for which we want to make a comment, and click the left mouse button on the
window 1 comments added to the keys. If a comment to some keys had already been, then it is replaced
with a new one. Also, comments can be added and the validation keys, for example, "New Key".

Use when the program of one processor core

Tired of looking like jerks the cursor moves on the screen while checking the keys?
Starting with version 1.28 Test1 when checking keys can be used only one CPU core (have to tick "Use
only CPU 0"). In this case, is only one CPU core, the other nuclei remain for other processes. It works in
real time.
Attention! Setting "Use only CPU 0" is saved when you exit the program and remain so the next time the
program.

Renovation of the key database

Sometimes and each time atfter updating the program (execunig files) you should renovate key
database. For this in launched program (checking keys at this moment should not run) press buttons
CTRL+R.
Working with Files * .xrm-ms (configs)
To determine the key program uses standard files * .xrm-ms from MS.
When the program starts happening unpacking these files in \Windows\Temp\pkXXX\
$1 - There config key with the letter "N" in the body.
$2 - No "N"
$3 - If the key is not defined, the definition goes with configs from this folder. It is assumed that there
should be the most rarely used configurations.
To use the additional (new) config not included in the program next to the EXE you can create a folder
pkconfig, in which to begin to copy the folder $1, $2, $3 from the \Windows\Temp\pkXXX and can put
these additional (new) configs.
Attention! The folder is not near the EXE completes, it completely replaces the $1; $2; $3 in
\Windows\Temp\pkXXX.

Recommendations fro moving key database from PIDKey to PIDKey Lite

Attention! While moving key database please have patience. The process is rather long. Please add keys
for moving by parts.
1) Prepare text files with PIDKey keys. You can find them here: \Windows\Temp\{PIDKEY-x64-
5426425733184803}.$$$ (also may be a folder with a similar name)
Copy this folder to a special place where it would be stored until keys are moved. After copying is
finished, close PIDKey.
Go to a copied folder:
Go to folder KEYS:

2) Moving of the invalid keys database.

File KEY_NOT_DEFINED.key is a file with invalid PIDKey keys. These keys may be fearlessly moved to
PIDKey Lite. Database.
For this launch PIDKey Lite, press button 4, put Tick mark in front of “Add keys to the not defined”:
Open file KEY_NOT_DEFINED.key in any text editor, pick off all keys and copy to clopboard. From
clipboard by clicking left mouse button on input box 1 paste all keys directly to the database.
After adding invalid keys don’t forget to put Tick mark in front of “Add keys to the not defined”.
By pressing button 3 you can go to key databae and see the added invalid keys:
3) Mooving of blocked keys. Unfortunately, the same mooving as for invalid key is impossble because
in database you shoulf create not only the key itself, but also all information about it.
That’s why you should add keys all together (or by portions- depending on the quantity).
Now we have 0 blocked keys in database. Press button 4 and go to adding keys mode:
Put Tick mark “Add keys to the blocked” and in input box 1 add blocked keys (it’s better to add keys by
portions). After adding blocked keys began, button 2 changes its view and chacking of these keys
begins in order to create infromation about them in database. Besides creating information keys are
marked as blocked. Tick mark “Add keys to blocked” is in shadow, underneath is green line “Please
wait…” with a rotating sign “/”

After adding keys is finished we see:

4) Mooving CSVLK, MAK, OEM, RETAIL, Server keys (GVLK keys are alredy added to database). For this
copy keys from appropriate folders and sub-folders
to clipbord and add them for checking (all together or by porions) and check them. This operation takes
a lot of time, so have patience. The checked keys would be added to database to appropriate folders of
keys.
In all operations of adding keys you can use direct downloading of keys from file, without using
clipboard.