Visual studio 2015 professional key Archives

3. Remove traces of your submission

If you are a high-risk source and the computer you prepared your submission on, or uploaded it from, could subsequently be audited in an investigation, we recommend that you format and dispose of the computer hard drive and any other storage media you used.

In particular, hard drives retain data after formatting which may be visible to a digital forensics team and flash media (USB sticks, memory cards and SSD drives) retain data even after a secure erasure. If you used flash media to store sensitive data, it is important to destroy the media.

If you do this and are a high-risk source you should make sure there are no traces of the clean-up, since such traces themselves may draw suspicion.

Heath

Administrators and developers who need to detect whether Visual Studio 2015 is installed can use similar registry keys as with past releases. This time around, though, we’ve made some changes to the lineup of products but the registry scheme remains the same.

Most of the detection keys are found in the 32-bit registry hive – the ones you’ll typically want to detect, anyway.

• Core: HKLM\Software\Microsoft\DevDiv\<Family>\Servicing\<Version>\<Edition>
• Language pack: HKLM\Software\Microsoft\DevDiv\<Family>\Servicing\<Version>\<Edition>\<LCID>

Following is a table of the products we’ve announced.

The biggest change to the detection keys is that Enterprise replaces Premium and Ultimate. Community is also a subset of Professional which is a subset of Enterprise, so if you you have some dependency on a feature in Community, for example (like the ability to add extensions), you can detect all three “VS” family products by checking for Community like so:

HKLM\Software\Microsoft\DevDiv\VS\Servicing\14.0\Community

The registry values we store in either key are as follows.

These changes go into effect with Visual Studio 2015 RC. I’ll update this page should we make any further changes for RTM.

Hi Adam Gustafsson,

Welcome to MSDN forum.

I recommand you could take the following steps to change the product Key:

1.Discover what license key Visual Studio was looking for in the registry with Process Monitor.

2.Completely uninstall Visual Studio 2015 (save CurrentSettings.vssettings first), use /uninstall /force to uninstall it.

3.Delete the license key from the registry by hand in regedit.

4. Install Visual Studio using the publicly available web installer (which doesn't have any baked-in license key -- it installs a 30-day trial).

5. Enter the new product key.

6. Restore settings by importing the backup which is made of CurrentSettings.vssettings.

You could download Process Monitor from http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

You can verify this by searching the “Licenses” or “License” keywords from the output. If you find such key, you can back up the registry key first and then delete it.

For license issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there.

Best regards,

Joyce

Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.