How to change Visual Studio 2012,2013 or 2015 License Key?

Question

I have a Copy of Visual Studio 2012 Pro on my machine with a Serial key that i'm no longer suppose to use because i have to use another one. My problem is i keep Uninstalling Visual studio but the Registration information is still there after re-install and i cannot figure out which registry path i have to delete (i deleted a few) with no luck.

Is there a easy way to remove tha reg info or swap my keys?

Thanks

score 64 · Answer 1 · edited Dec 08 '16 at 14:34

64

I had the same problem and wanted to change the product key to another. Unfortunate it's not as easy as it was on VS2010.

The following steps work:

Remove the registry key containing the license information: HKEY_CLASSES_ROOT\Licenses\77550D6B-6352-4E77-9DA3-537419DF564B
If you can't find the key, use sysinternals ProcessMonitor to check the registry access of VS2012 to locate the correct key which is always in HKEY_CLASSES_ROOT\Licenses
After you remove this key, VS2012 will tell you that it's license information is incorrect. Go to "Programs and features" and repair VS2012.
After the repair, VS2012 is reverted to a 30 day trial and you can enter a new product key. This could also be used to stay in a trial version loop and never enter a producy key.

edited Dec 08 '16 at 14:34

arunjos007

4,105
1
28
43

answered Feb 11 '13 at 10:51

Nico

740
6
9

3

VisualStudio install/repair takes sooooo long :D I wonder what the system is doing all the time. No CPU, no Disk, no progress... – mschmoock Jun 17 '13 at 14:40
4

To be precise, i needed to remove the following subkey (04938): HKEY_CLASSES_ROOT\Licenses\77550D6B-6352-4E77-9DA3-537419DF564B\04938 – mschmoock Jun 17 '13 at 14:49
2

Works fine . For VS15 "HKEY_CLASSES_ROOT\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F" – Nihar Sarkar Feb 02 '18 at 15:47

score 54 · Answer 2 · answered Sep 09 '15 at 14:28

54

For those who will need to remove product key from Visual Studio 2015:

remove registry key HKCR\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F
repair Visual Studio installation

That's it, now you can change the product key if necessary.

answered Sep 09 '15 at 14:28

Oleks

31,955
11
77
132

2

I've done these steps for VS2015 and they worked. It does take a fair while (~1 hour) to go through the whole repair and re-setup process – Niall Connaughton Nov 09 '15 at 03:28
1

@ParthAkbari: my best guess is _yes_, but I don't have a confirmation of this – Oleks Dec 24 '15 at 10:04
1

Working fine for me – Jainish Jariwala Oct 16 '16 at 04:11
@ParthAkbari it was for mine and I have the newest VS 2015 Community running on Server 2016 Essentials. – Edward Jan 07 '17 at 01:45
I would not use this method, I used it earlier today and ever since then the moment I access the file open dialog in VS2015 (and only VS2015, SMSS works fine) I get a BSOD – Peter Nimmo Mar 21 '19 at 17:11
@PeterNimmo I used this method on several laptops for both 2015 and 2017 and never saw a BSOD – Oleks Mar 27 '19 at 18:14
Lucky you, I've not been so lucky. I've now tracked it down to it having broken Junctions – Peter Nimmo Mar 29 '19 at 14:35
I keep getting the crash every time I use a different application that happened to remember a subfolder whose parent happens to be a junctioned folder – Peter Nimmo Mar 29 '19 at 14:35
For me that key has 19 subfolders, do i delete it with all of them? – StackTrace Jun 01 '21 at 12:13

score 32 · Answer 3 · answered Mar 07 '14 at 18:38

For me, with Visual Studio 2013, it wasn't enough to remove the license key and perform a repair (the repair restored the license key instead of reverting to a trial, and running it without the repair (after deleting the key) claimed the license had expired but wouldn't let me enter a new key).

I had to:

Discover what license key Visual Studio was looking for in the registry with Process Monitor (it was HKCR\Licenses\E79B3F9C-6543-4897-BBA5-5BFB0A02BB5C)
Completely uninstall Visual Studio 2013 (save CurrentSettings.vssettings first)
Delete the license key from the registry by hand in regedit
Install Visual Studio using the publicly available web installer (which doesn't have any baked-in license key -- it installs a 30-day trial)
Enter my new license key
(Re-)install updates (Update 1 at this time)
Restore settings by importing the backup I made of CurrentSettings.vssettings

Thanks for this. you should make another question with this as the answer for VS2013 — Hades, Sep 14 '14 at 14:35
This is exactly what worked for me on VS2012 professional. I used the publicly downloadable ISO for re-installing. Thanks — mishal153, Jan 05 '16 at 10:18

score 12 · Answer 4 · answered Jun 20 '17 at 09:34

For those of you using Visual Studio 2017 Professional, the registry key is:

HKCR\Licenses\5C505A59-E312-4B89-9508-E162F8150517

I also recommend you first export the registry key, before you delete it, so you'll have a backup if you accidentally delete the wrong key.

score 10 · Answer 5 · edited May 23 '17 at 12:10

To see what's inside these HKCR\Licenses use API Monitor v2

API-Filter find 

    RegQueryValueExW 
        ^-Enable all from Advapi32.dll

    CryptUnprotectData
        ^- Enable all from Crypt32.dll
         + Breakpoint / after Call

sample data that'll come out from CryptUnprotectData:

HKEY_CLASSES_ROOT\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F\07078  [length 0x1C6 (0454.) ]
    00322-20000-00000-AA450                 <- PID2
    7d3cbcbb-90b1-411f-9981-6e28039a9b82    <- Ver
    7C3WXN74-VRMXH-J8X3H-M8F7W-CPQB8        <- PID3

HKEY_CLASSES_ROOT\Licenses\4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F\0bcad  [length 0xbcad (0534.) ]

    0000  00000025 ffffffff 7fffffff   07064. 00000007   07078. 00000007 ffffffff
    0020  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    0040  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    0060  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    0080  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    00a0  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    00c0  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    00e0  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    0100  7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff 7fffffff ffffffff
    0120  7fffffff ffffffff 7fffffff 10.2015. c2a6 11.
    0134                             ^installation date^

Useful here is maybe the Installation timestamp (11.10.2015 here ) Change this would required to call 'CryptProtectData'. Doing so needs some efforts like written a small program OR stop with ollydebug at this place and manually 'crafting' a CryptProtectData call ...

Note: In this example I'm using Microsoft® Visual Studio 2015

-> For a quick'n'dirty sneak into an expired VS I recommend to read this post. However that's just good for occasional use, till you get all the sign up and login crap properly done again ;)

Okay the real meat is here:
%LOCALAPPDATA%\Microsoft\VisualStudio\14.0\Licenses\ ^- This path comes from HKCU\Software\Microsoft\VisualStudio\14.0\Licenses\715f10eb-9e99-11d2-bfc2-00c04f990235\1

1_3jdh3uyw**.crtok**

-after some Base64 decoding:

<ClientRightsContainer 
    xmlns="http://schemas.datacontract.org/2004/07/Microsoft.VisualStudio.Services.Licensing" 
    xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
    <CertificateBytes>
        00000000   30 82 06 41 30 82 04 29  A0 03 02 01 02 02 13 5A   0‚ A0‚ )       Z
        00000010   00 00 BC CB 23 AC 52 9C  E8 93 F9 0A 00 01 00 00     ¼Ë#¬Rœè“ù     
        00000020   BC CB 30 0D 06 09 2A 86  48 86 F7 0D 01 01 0B 05   ¼Ë0   *†H†÷     
        00000030   00 30 81 8B 31 0B 30 09  06 03 55 04 06 13 02 55    0 ‹1 0   U    U
        00000040   53 31 13 30 11 06 03 55  04 08 13 0A 57 61 73 68   S1 0   U    Wash
        00000050   69 6E 67 74 6F 6E 31 10  30 0E 06 03 55 04 07 13   ington1 0   U   
        00000060   07 52 65 64 6D 6F 6E 64  31 1E 30 1C 06 03 55 04    Redmond1 0   U 
        00000070   0A 13 15 4D 69 63 72 6F  73 6F 66 74 20 43 6F 72      Microsoft Cor
        00000080   70 6F 72 61 74 69 6F 6E  31 15 30 13 06 03 55 04   poration1 0   U 
        00000090   0B 13 0C 4D 69 63 72 6F  73 6F 66 74 20 49 54 31      Microsoft IT1
        000000A0   1E 30 1C 06 03 55 04 03  13 15 4D 69 63 72 6F 73    0   U    Micros
        000000B0   6F 66 74 20 49 54 20 53  53 4C 20 53 48 41 32 30   oft IT SSL SHA20
        000000C0   1E 17 0D 31 35 30 33 30  35 32 31 32 39 35 36 5A      150305212956Z
        000000D0   17 0D 31 37 30 33 30 34  32 31 32 39 35 36 5A 30     170304212956Z0
        000000E0   25 31 23 30 21 06 03 55  04 03 13 1A 61 70 70 2E   %1#0!  U    app.
        000000F0   76 73 73 70 73 2E 76 69  73 75 61 6C 73 74 75 64   vssps.visualstud
        00000100   69 6F 2E 63 6F 6D 30 82  01 22 30 0D 06 09 2A 86   io.com0‚ "0   *†
        ...
        000002B0   6E 86 36 68 74 74 70 3A  2F 2F 6D 73 63 72 6C 2E   n†6http://mscrl.
        000002C0   6D 69 63 72 6F 73 6F 66  74 2E 63 6F 6D 2F 70 6B   microsoft.com/pk
        000002D0   69 2F 6D 73 63 6F 72 70  2F 63 72 6C 2F 6D 73 69   i/mscorp/crl/msi
        000002E0   74 77 77 77 32 2E 63 72  6C 86 34 68 74 74 70 3A   twww2.crl†4http:
        000002F0   2F 2F 63 72 6C 2E 6D 69  63 72 6F 73 6F 66 74 2E   //crl.microsoft.
        00000300   63 6F 6D 2F 70 6B 69 2F  6D 73 63 6F 72 70 2F 63   com/pki/mscorp/c
        00000310   72 6C 2F 6D 73 69 74 77  77 77 32 2E 63 72 6C 30   rl/msitwww2.crl0
        00000320   70 06 08 2B 06 01 05 05  07 01 01 04 64 30 62 30   p  +        d0b0
        00000330   3C 06 08 2B 06 01 05 05  07 30 02 86 30 68 74 74   <  +     0 †0htt
        00000340   70 3A 2F 2F 77 77 77 2E  6D 69 63 72 6F 73 6F 66   p://www.microsof
        00000350   74 2E 63 6F 6D 2F 70 6B  69 2F 6D 73 63 6F 72 70   t.com/pki/mscorp
        00000360   2F 6D 73 69 74 77 77 77  32 2E 63 72 74 30 22 06   /msitwww2.crt0" 
        00000370   08 2B 06 01 05 05 07 30  01 86 16 68 74 74 70 3A    +     0 † http:
        00000380   2F 2F 6F 63 73 70 2E 6D  73 6F 63 73 70 2E 63 6F   //ocsp.msocsp.co
        00000390   6D 30 4E 06 03 55 1D 20  04 47 30 45 30 43 06 09   m0N  U   G0E0C  
        000003A0   2B 06 01 04 01 82 37 2A  01 30 36 30 34 06 08 2B   +    ‚7* 0604  +
        000003B0   06 01 05 05 07 02 01 16  28 68 74 74 70 3A 2F 2F           (http://
        000003C0   77 77 77 2E 6D 69 63 72  6F 73 6F 66 74 2E 63 6F   www.microsoft.co
        000003D0   6D 2F 70 6B 69 2F 6D 73  63 6F 72 70 2F 63 70 73   m/pki/mscorp/cps
        000003E0   00 30 27 06 09 2B 06 01  04 01 82 37 15 0A 04 1A    0'  +    ‚7    
        000003F0   30 18 30 0A 06 08 2B 06  01 05 05 07 03 01 30 0A   0 0   +       0 
        00000400   06 08 2B 06 01 05 05 07  03 02 30 25 06 03 55 1D     +       0%  U 
        00000410   11 04 1E 30 1C 82 1A 61  70 70 2E 76 73 73 70 73      0 ‚ app.vssps
        00000420   2E 76 69 73 75 61 6C 73  74 75 64 69 6F 2E 63 6F   .visualstudio.co
        00000430   6D 30 0D 06 09 2A 86 48  86 F7 0D 01 01 0B 05 00   m0   *†H†÷      
        ...                                                U
    </CertificateBytes>
    <Token>
    {
        "typ":"JWT",
        "alg":"RS256",
        "x5t":"i7qX-NUrehXBYdQC5PSH-TdvzXA"
    }
    </Token>
</ClientRightsContainer>

Seems M$ is using JSON Web Token (JWT) to wrap in license data. I guess inside CertificateBytes will be somehow the payload - you're email and other details.

So far for the rough overview what's the data inside.

For more wishes get ILSpy + Reflexil (<- to changes/correct little things!) and then 'browser&correct' files like c:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE**Microsoft.VisualStudio.Licensing.dll** or check out 'Microsoft.VisualStudio.Services.WebApi.dll'

recommends a YouTube video. Amazing! – Andre Mesquita Jun 10 '16 at 19:15 — Andre Mesquita, Jun 10 '16 at 19:15

Haider · Answer 6 · 2018-04-06T17:25:15.503

See my UPDATE at the end, before reading the following answer.

I have windows 8 and another pc with windows 8.1

I had License error saying "Prerelease software. License expired".

The only solution that I found which is inspired by the above solutions (Thanks!) was to run process monitor and see the exact registry keys that are accessed when I start the VS2013 which were:

HKCR\Licenses\E79B3F9C-6543-4897-BBA5-5BFB0A02BB5C

like what are mentioned in the previous posts. However the process monitor said that this registry is access denied.

So I opened regedit and found that registry key and I could not open it. It says I have no permission to see it.

SO I had to change its permission:

Right click on the "HKCR\Licenses\E79B3F9C-6543-4897-BBA5-5BFB0A02BB5C" key
Permissions
Add
In "Enter object names to select" I have added my windows user name. Ok.
check on Full control
Advanced
Owner click on "Change"
In "Enter object names to select" I have added my windows user name. Ok.
Ok. Ok. Ok.

I found that this registry key has several sub keys, however you have to restart regedit to see them.

By seeing which other registry keys are access denied in process monitor , I knew that VS2013 will specifically deal with these subkeys which are ACCESS DENIED also: 06181 0bcad

and these subkeys should be changed their permissions as well like above.

After making these permission changes everything worked well.

The same thing has been done to Microsoft visual studio 2010 because an error in the license as well and the solution worked well.

UPDATE : It turned out that starting visual studio as administrator solved this issue without this registry massage. Seems that this happened to my pc after changing the 'required password to login' removed in the user settings. (I wanted to let the pc start running without any password after restart from a crash or anything else). This made a lot of programs not able to write into some folders like temp folders unless I start the application as admin. Even printing from excel would not work, if excel is not started as admin.

score 1 · Answer 7 · answered Oct 20 '12 at 06:22

1

The ISO is probably pre-pidded. You'll need to delete the key from the setup files. It should then ask you for a key during installation.

answered Oct 20 '12 at 06:22

Monstieur

7,992
10
51
77

Where is that information? I have the MSDN VLK discs and it never asked for a CD key during installation and my licence manager never decremented a seat and it seems there is no way to see which key was actually used, easily for one of my engineers. – Jon Weinraub Feb 12 '14 at 20:18
Visual Studio VLK ISOs from MSDN used to be pre-pidded. The old MSDN interface used to say which of your downloads were pre-pidded. There is no license check at all for a VS VLK key. The MSDN discs use a universal VLK for everyone. The key is in a file on the disc itself. – Monstieur Feb 13 '14 at 04:19
I don't see any setup.sdb on my disc. It wasn't an ISO, its the yellow msdn disc. Disc #5093/November 2012. I would use the registry if that is a safe method, but I didn't see any repair options that would allow me to change the key and not too sure as to why the VLK was prebaked but my licence manager website did not decrement and I am concerned about possible audits. – Jon Weinraub Feb 14 '14 at 15:33
If the original disk did not require you to enter a key then thats all you need to care about. It's a non-activation VLK key. Install it on a new PC to confirm if you think it's using an old key from the registry. All my MSDN Visual Studio disks did not require a key (the key was in one of those setup files if you browsed the disk). Visual Studio will not work without a key coming from somewhere. The MSDN Visual Studio embedded keys are "global" for all users. It is not specific to you. The license is just on paper. You must not install more copies than you're allowed. – Monstieur Feb 15 '14 at 04:53
Okay thanks, that is what I had thought. We bought the 2013 seat that came with 2012 downgrade option, and the programmer wanted 2012. So I have it in all of my records, and I think last time I had an issue was for 2010. But thanks for the help (especially when I butted into someones question.. – Jon Weinraub Feb 18 '14 at 13:40

score 1 · Answer 8 · answered Jan 31 '14 at 06:56

1

The solution with removing the license information from the registry also works with Visual Studio 2013, but as described in the answer above, it is important to execute a "repair" on Visual Studio.

answered Jan 31 '14 at 06:56

Marcel

11
1

score 0 · Answer 9 · answered Sep 27 '21 at 12:20

0

For those of you using Visual Studio 2019 Professional, the registry key is:

HKCR\Licenses\41717607-F34E-432C-A138-A3CFD7E25CDA

Execute a "Repair" on Visual Studio afterwards.

answered Sep 27 '21 at 12:20

dontbyteme

1,221
1
11
23

score 0 · Answer 10 · answered Sep 30 '22 at 07:54

Depending on which Visual Studio version you use first remove the following registry key located in HKCR\Licenses\

Visual Studio 2013 Professional      E79B3F9C-6543-4897-BBA5-5BFB0A02BB5C\06177
Visual Studio 2015 Enterprise        4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F\07060
Visual Studio 2015 Professional      4D8CFBCB-2F6A-4AD2-BABF-10E28F6F2C8F\07062
Visual Studio 2017 Enterprise        5C505A59-E312-4B89-9508-E162F8150517\08860
Visual Studio 2017 Professional      5C505A59-E312-4B89-9508-E162F8150517\08862
Visual Studio 2017 Test Professional 5C505A59-E312-4B89-9508-E162F8150517\08866
Visual Studio 2019 Enterprise        41717607-F34E-432C-A138-A3CFD7E25CDA\09260
Visual Studio 2019 Professional      41717607-F34E-432C-A138-A3CFD7E25CDA\09262
Visual Studio 2022 Enterprise        1299B4B9-DFCC-476D-98F0-F65A2B46C96D\09660
Visual Studio 2022 Professional      1299B4B9-DFCC-476D-98F0-F65A2B46C96D\09662

see VSKeyExtractor for other versions.

Then do a repair install.

How to change Visual Studio 2012,2013 or 2015 License Key?

10 Answers10

Linked

Related