Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS2019 Updating License Issue #11

Open
georgekustanza opened this issue Dec 21, 2020 · 7 comments
Open

VS2019 Updating License Issue #11

georgekustanza opened this issue Dec 21, 2020 · 7 comments

Comments

@georgekustanza
Copy link

I'm trying to update the license of my VS2019 in a standalone PC. It "successfully" updates the license when I run Set-VSCELicenseExpirationDate and shows the "updated" license correctly when I run Get-VSCELicenseExpirationDate, but whenever I start Visual Studio, the "license gone sale" popup message immediately pops.

Any help would be appreciated

@Biswa96
Copy link

Biswa96 commented Dec 21, 2020

No issue in my case. What is the version of Visual Studio? When did you install it?

@georgekustanza
Copy link
Author

georgekustanza commented Dec 21, 2020

No issue in my case. What is the version of Visual Studio? When did you install it?

Thanks for answering,
Version 16.1.6 with .NET Framework Version 4.8.03761
Visual Studio Community 2019

@Biswa96
Copy link

Biswa96 commented Jan 1, 2021

This project works fine in my clean VS setup. I am using Microsoft Visual Studio Community 2019 Version 16.8.3 with .NET Framework Version 4.8.04161.

@beatcracker
Copy link
Owner

I'm not sure why this could happen, but as a last resort I'd suggest removing VS 2019 licensing registry key and repairing installation.

  1. Remove this registry key
    HKEY_CLASSES_ROOT\Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA\09278
    
  2. Run Repair here
    Repair

@MeatyCheesy
Copy link

I'm encountering the same thing. I've tried the deleted registry key and repair also and still no luck. I'm on Visual Studio 2019 Community 16.7.10. Build is 16.0.30816.78 D16.7.

@aaronrsiphone
Copy link

aaronrsiphone commented Aug 23, 2022

I am on VS2019 v16.0.3 and as OP described the tool is successful at updating the registry but it appears the older versions of v16/2019 look for the date in \09262 instead of \09278.

So updating the LicenseMap at the top of VSCELicense.psm1 to be
'2019' = 'Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA\09262'
instead of
'2019' = 'Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA\09278'
worked for me.

Found via trial an error.

@uwydoc
Copy link

uwydoc commented Sep 9, 2022

correct. maybe the scripts should iterate through all sub folders in the registry path, and choose the maximum one with all digits (instead of hex chars, there exists an folder named 0bcad for all supported vs versions, 2013, 2015, 2017, 2019)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants