Jump to content
Sign in to follow this  
Peter Webber

P3D Update v3.1 to v3.2, License reactivation?

Recommended Posts

Good day.

I have successfully upgraded my P3D v3.1 TO v3.2 using the client only upgrade. No problems and all went well. Checked my version and it's at v3.2 as expected with all the usual addon compatibility issues, object flow, etc.

The only odd issue I noticed was that I was not required to reactivate my P3D license. When I upgraded from v3.0 to v3.1 I was required to reactivate. I have not performed a clean install, only the client update in both cases. The only difference with this upgrade was that I kept my PC linked to the internet during the upgrade. Would this make the difference? I've always heard the license will require reactivation, but it was not the case this time around.


Peter Webber

Prepar3D v5 & MSFS / Windows 10 Home Edition / CPU i7-7700K / MSI Z270 XPower Gaming Titanium / Samsung 970 EVO PLUS M.2 500GB / Corsair Vengeance DDR4 32GB 3000MHz / MSI Geforce GTX 1080Ti Gaming X

Share this post


Link to post

It should have required activation, but hey, if it runs...just grin and bear it.


Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's

Share this post


Link to post

Hi Peter,

 

I have the same situation. Updated via the Client installer without being asked for re-activation.


Dragos

I9-13900K/ Gigabyte RTX 4090 Gaming OC/ Aorus Master Z790/ Kingston 64GB@6000Mhz DDR 5/ 2TB nvme 0.2 Samsung 980 PRO/ Deepcool LS720

Share this post


Link to post

Hi Peter,

 

I have the same situation. Updated via the Client installer without being asked for re-activation.

I believe it said in the initial release notes for 3.2 that for most users, license reactivation would happen automatically in the background during without requiring input.


Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

Share this post


Link to post
Guest JustanotherPilot

This happened to me form v3.0 to v3.1, I got away with it for a couple of uses then I was asked to reactivate. I have my installation outside of the LM default, don't know if that had anything to do with. I'm still waiting for the v3.2 rush to settle down before I commit to the update.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...