Hi @Pierre-Alan,

Studio updates (SR's and CU's) are not linked to an actual license-(as these are always free)only upgrades will require a license check.

Therefore if you dont own a license (loaned by Universities/Clients etc.) its always possible to keep your Styudio up to date.

Therefore just open Studio - Go to HELP  and Check for Updates

Unknown said:

Studio updates (SR's and CU's) are not linked to an actual license-(as these are always free)

Not entirely correct... E.g. update to Studio 2017 SR1 asks for logging into SDL account... and if you DO NOT have own SDL account with assigned license, you cannot download the update this way. See screenshots below.

This is new process for 2017 SR1... for example 2015 SR3 was downloaded and installed the usual way directly via update dialog.

Hi Evzen Polenka 

Sorry Evzen I could/should have been much clearer.

Indeed if the release is an SR (service release)- then you will generally need account access- as this will reflect a new Studio install.

However if this is a simple CU (cumulative update) you do not need to be logged into an account - Simply run 'Check for Updates'.

Kr

Unknown said:

Indeed if the release is an SR (service release)- then you will generally need account access- as this will reflect a new Studio install.

The question is, why such obstacles, effectively preventing certain type of users from installing the update.
Especially if that worked just fine so far - all 2015 SRs (or SPs in Studio 2014) were installed just fine directly using the standard update dialog, even if these were also full installs.

Unknown said:

The question is, why such obstacles, effectively preventing certain type of users from installing the update.
Especially if that worked just fine so far - all 2015 SRs (or SPs in Studio 2014) were installed just fine directly using the standard update dialog, even if these were also full installs.

Hi Evzen,

If the SP or SR requires a full install and not just a patch then it has always been released through the account.  You only have to look at the latest installer in your account for these versions to see that.

I guess it's only an obstacle for a user who has been given a licence by the company they work for and don't have it in their own account... but then many companies want this control over the use to prevent inconsistencies and people upgrading when they may have a specific reason why not.  So it's probably six of one and half a dozen of the other.

Regards

Paul

Unknown said:

The question is, why such obstacles, effectively preventing certain type of users from installing the update.
Especially if that worked just fine so far - all 2015 SRs (or SPs in Studio 2014) were installed just fine directly using the standard update dialog, even if these were also full installs.

Hi Evzen,

If the SP or SR requires a full install and not just a patch then it has always been released through the account.  You only have to look at the latest installer in your account for these versions to see that.

I guess it's only an obstacle for a user who has been given a licence by the company they work for and don't have it in their own account... but then many companies want this control over the use to prevent inconsistencies and people upgrading when they may have a specific reason why not.  So it's probably six of one and half a dozen of the other.

Regards

Paul