Upgrading to latest version

Use Help/Check for updates menu option to check for latest updates.

The latest build is always the most stable and compatible version. History of all changes is listed in whatsnew.txt document which is included in distribution package and displayed during installation. Same information is also available in our online activation center (build history) and can be reviewed there as well. Information about new builds is sent to clients subscribed to our newsletter as soon as they are released. Only the latest build can be delivered on request. Old builds are not available for download.

New builds are not always 100% compatible with previous releases. Be sure to review all changes since the version you are using before upgrading to latest build.
We are compiling unique copy for each customer and because of this we are not keeping backup copies of builds delivered to customers. Be sure to backup your copy!

Upgrading from old V5 versions to latest V6 version

All PC Guard V6 family products share the same project format and can load project generated by V5 family products. They also can generate valid activation codes for both V5 and V6 protected applications.

However, V6 and V5 PC Guard family products are not fully compatible and this is mainly due to changes in license file format, locking system and site/mid code changes (they are now project dependent) which were introduced in V6. More information about this is included in whatsnew.txt document which is included in each full featured version of PC Guard. If you are upgrading from V5, please be sure to fully read this document before starting with upgrading process.

If Detect existing V5 license option is selected, protected application will try to detect and use existing active license of application protected with PC Guard Win32 V5 or PC Guard for .NET V5 and with same project settings (same Application signature and Program ID values).

This option is useful in case license reactivation should be avoided for free application updates for applications originally protected with V5 family products.

If you were using custom license filename for V5 protected applications you need to set appropriate V5 custom license filename in V6 project options. Custom license filename value (if defined) has to be different from this value.
Check for existing V5 license is done only once during the first run of protected application on remote machine. As soon as v6 license data for this project is created on remote machine (and this is done after first run of V6 protected application) V5 license check will no longer be made!

If existing V6 license is detected on remote machine application protected with this option enabled will not check for V5 license at all. If V5 license is detected but not active (application is in demo mode or in locked state) it will be ignored.

If active V5 license is detected, protected application will automatically activate itself. No further V5 licenses checks will be done on remote machine after this.

V5 license will stay intact and independent from V6 license. This means that end user will be able to continue using both V5 and V6 licensed products on same machine. All future V6 license changes will not affect V5 license on same machine and vice-versa.