Note about old/new Extended License keys (starting from FORScan v2.3.22)

Any issues related to FORScan application
Post Reply
FORScan
Site Admin
Posts: 2616
Joined: Fri Jun 13, 2014 2:21 am

Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by FORScan » Sat May 11, 2019 5:06 am

Extended License was added in FORScan v2.3.0 and available since that time. Extended License protection system is 3rd party development licensed by us. Unfortunately, in some very rare cases (app. once per 500 installations) it didn't work for unknown reason: even although Extended License key is valid and installed properly, it doesn't unlock the Extended License. So we had to upgrade/replace the protection system in order to fix the problem. So now we have old Extended License keys (generated and used in FORScan v2.3.0..v2.3.21) and new Extended License keys (generated and used starting from FORScan v.2.3.22). It must be noted that Extended License functionality is identical for both new and old keys.

Unfortunately, it is not technically possible to provide full compatibility between old and new keys. Extended License keys are now forward compatible: old keys work only in FORScan versions prior to v2.3.21 (inclusively). New keys work in both new (v2.3.22+) and old (v2.3.21-) versions. So now we need all existing users to change their license keys. To provide a smooth process, we have dediced to make a transition period. During this period that is planned to be 3-6 months or so, we will release 2 versions of FORScan for Windows: version that supports old keys and version that supports new keys. If user installs the version with old keys, it doesn't need to do anything with the license key and everything will work as before. Version with new keys will require new keys to be generated and installed. Users who have free 2 months license will need to generate, download and install new license keys. Users who have paid license will just need to retry the activation with their activation code.

After transition period only version with new Extended License keys will be available.

Airborne_Ape
Posts: 24
Joined: Thu Sep 08, 2016 11:18 pm
Vehicle: Ford, 3.5 Ecoboost, 2016

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by Airborne_Ape » Sat May 11, 2019 8:24 pm

Are you saying there is no way for users who bought a lifetime licence (for old versions up to 2.3.21) to transition their old purchased key to a new key?

lenko
Posts: 219
Joined: Sat Dec 24, 2016 6:40 pm
Vehicle: 2015 Lincoln MKC, 2.0 Ecoboost

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by lenko » Sat May 11, 2019 10:13 pm

Have lifetime license and downloaded for old keys, updated and it works.

ford18
Posts: 4
Joined: Sun Mar 31, 2019 4:39 pm
Vehicle: Tourneo Courier Ecoboost 1.0 2018

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by ford18 » Mon May 13, 2019 8:52 am

Users who have paid license will just need to retry the activation with their activation code.

mtech
Posts: 3
Joined: Sun Jul 31, 2016 4:47 pm
Vehicle: 2010 Ford F-150 4.6 3V

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by mtech » Thu May 16, 2019 2:05 am

How do users with an old key transition to a new key?

omar302
Posts: 100
Joined: Sat Apr 16, 2016 4:50 am
Vehicle: Ford Edge, Gasoline 2.7L/335hp, 2016

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by omar302 » Fri May 17, 2019 4:32 am

I have a lifelong licence. I installed the version with new license key and used the same activation key I received when I purchased the lifelong licence and it worked. Very simple.

danielmazda
Posts: 2
Joined: Tue Dec 19, 2017 6:19 pm
Vehicle: JM7CR10F780305090
Contact:

Re: Note about old/new Extended License keys (starting from FORScan v2.3.22)

Post by danielmazda » Tue Oct 15, 2019 6:02 pm

Hi admin, pls approve my new registed Id who is “fordmazda" and I had sent email to you,
The email address is sosongan @gmail.com,
Please, please.

Post Reply