How to change Visual Studio 2013 license information from MSDN to Visual Studio Professional Online?
up vote
0
down vote
favorite
My MSDN license elapsed earlier this year and I have now set up a Visual Studio Professional Online subscription.
If I install Visual Studio 2013 on a fresh computer, I get to log on to Visual Studio Online and it downloads a license that is valid for 32 days, presumably it will refresh every 30 days with a couple of extra days slack.
However, my main computer still has the MSDN license key set up, and I'm worried that it will stop working in the middle of important work and require a full reinstall.
If that's what I have to do, I would like to know this now, when I can do it during downtime, so my question is this:
Is it possible for me to "unregister" my locally installed Visual Studio 2013, so that it forgets completely that it has a license key, and allows me to download the license from Visual Studio Online?
I've tried the suggestions outlined here on Stack Overflow which involves deleting a registry key and repairing Visual Studio. After this, Visual Studio repairs it right back to having a license key applied.
visual-studio-2013
add a comment |
up vote
0
down vote
favorite
My MSDN license elapsed earlier this year and I have now set up a Visual Studio Professional Online subscription.
If I install Visual Studio 2013 on a fresh computer, I get to log on to Visual Studio Online and it downloads a license that is valid for 32 days, presumably it will refresh every 30 days with a couple of extra days slack.
However, my main computer still has the MSDN license key set up, and I'm worried that it will stop working in the middle of important work and require a full reinstall.
If that's what I have to do, I would like to know this now, when I can do it during downtime, so my question is this:
Is it possible for me to "unregister" my locally installed Visual Studio 2013, so that it forgets completely that it has a license key, and allows me to download the license from Visual Studio Online?
I've tried the suggestions outlined here on Stack Overflow which involves deleting a registry key and repairing Visual Studio. After this, Visual Studio repairs it right back to having a license key applied.
visual-studio-2013
1
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
1
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My MSDN license elapsed earlier this year and I have now set up a Visual Studio Professional Online subscription.
If I install Visual Studio 2013 on a fresh computer, I get to log on to Visual Studio Online and it downloads a license that is valid for 32 days, presumably it will refresh every 30 days with a couple of extra days slack.
However, my main computer still has the MSDN license key set up, and I'm worried that it will stop working in the middle of important work and require a full reinstall.
If that's what I have to do, I would like to know this now, when I can do it during downtime, so my question is this:
Is it possible for me to "unregister" my locally installed Visual Studio 2013, so that it forgets completely that it has a license key, and allows me to download the license from Visual Studio Online?
I've tried the suggestions outlined here on Stack Overflow which involves deleting a registry key and repairing Visual Studio. After this, Visual Studio repairs it right back to having a license key applied.
visual-studio-2013
My MSDN license elapsed earlier this year and I have now set up a Visual Studio Professional Online subscription.
If I install Visual Studio 2013 on a fresh computer, I get to log on to Visual Studio Online and it downloads a license that is valid for 32 days, presumably it will refresh every 30 days with a couple of extra days slack.
However, my main computer still has the MSDN license key set up, and I'm worried that it will stop working in the middle of important work and require a full reinstall.
If that's what I have to do, I would like to know this now, when I can do it during downtime, so my question is this:
Is it possible for me to "unregister" my locally installed Visual Studio 2013, so that it forgets completely that it has a license key, and allows me to download the license from Visual Studio Online?
I've tried the suggestions outlined here on Stack Overflow which involves deleting a registry key and repairing Visual Studio. After this, Visual Studio repairs it right back to having a license key applied.
visual-studio-2013
visual-studio-2013
edited May 23 '17 at 12:41
Community♦
1
1
asked May 6 '14 at 12:48
Lasse Vågsæther Karlsen
1,73693051
1,73693051
1
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
1
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13
add a comment |
1
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
1
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13
1
1
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
1
1
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
you can remove the license key from the registry after uninstalling VS from the machine, go to the below key in registry and rename/remove it. [HKCRLicenses77550D6B-6352-4E77-9DA3-537419DF564B4940]
You can also look for the license info in:
HKLMSOFTWAREWow6432NodeMicrosoftVisualStudio.....
add a comment |
up vote
-1
down vote
If your MSDN subscription was purchased as a retail subscription not part of any volume licensing or partner program you can continue to use the developer tools after the subscription expired but you do not get any updates or access to the MSDN subscriber downloads.
So if you did have a retail MSDN subscription it is allowed to continue using the tools.
You can read about this in the MSDN Licensing White Paper. See the section called Perpetual Use Rights for more information.
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f750341%2fhow-to-change-visual-studio-2013-license-information-from-msdn-to-visual-studio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
you can remove the license key from the registry after uninstalling VS from the machine, go to the below key in registry and rename/remove it. [HKCRLicenses77550D6B-6352-4E77-9DA3-537419DF564B4940]
You can also look for the license info in:
HKLMSOFTWAREWow6432NodeMicrosoftVisualStudio.....
add a comment |
up vote
0
down vote
you can remove the license key from the registry after uninstalling VS from the machine, go to the below key in registry and rename/remove it. [HKCRLicenses77550D6B-6352-4E77-9DA3-537419DF564B4940]
You can also look for the license info in:
HKLMSOFTWAREWow6432NodeMicrosoftVisualStudio.....
add a comment |
up vote
0
down vote
up vote
0
down vote
you can remove the license key from the registry after uninstalling VS from the machine, go to the below key in registry and rename/remove it. [HKCRLicenses77550D6B-6352-4E77-9DA3-537419DF564B4940]
You can also look for the license info in:
HKLMSOFTWAREWow6432NodeMicrosoftVisualStudio.....
you can remove the license key from the registry after uninstalling VS from the machine, go to the below key in registry and rename/remove it. [HKCRLicenses77550D6B-6352-4E77-9DA3-537419DF564B4940]
You can also look for the license info in:
HKLMSOFTWAREWow6432NodeMicrosoftVisualStudio.....
answered Dec 5 '15 at 10:49
Rami Sarieddine
1012
1012
add a comment |
add a comment |
up vote
-1
down vote
If your MSDN subscription was purchased as a retail subscription not part of any volume licensing or partner program you can continue to use the developer tools after the subscription expired but you do not get any updates or access to the MSDN subscriber downloads.
So if you did have a retail MSDN subscription it is allowed to continue using the tools.
You can read about this in the MSDN Licensing White Paper. See the section called Perpetual Use Rights for more information.
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
add a comment |
up vote
-1
down vote
If your MSDN subscription was purchased as a retail subscription not part of any volume licensing or partner program you can continue to use the developer tools after the subscription expired but you do not get any updates or access to the MSDN subscriber downloads.
So if you did have a retail MSDN subscription it is allowed to continue using the tools.
You can read about this in the MSDN Licensing White Paper. See the section called Perpetual Use Rights for more information.
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
add a comment |
up vote
-1
down vote
up vote
-1
down vote
If your MSDN subscription was purchased as a retail subscription not part of any volume licensing or partner program you can continue to use the developer tools after the subscription expired but you do not get any updates or access to the MSDN subscriber downloads.
So if you did have a retail MSDN subscription it is allowed to continue using the tools.
You can read about this in the MSDN Licensing White Paper. See the section called Perpetual Use Rights for more information.
If your MSDN subscription was purchased as a retail subscription not part of any volume licensing or partner program you can continue to use the developer tools after the subscription expired but you do not get any updates or access to the MSDN subscriber downloads.
So if you did have a retail MSDN subscription it is allowed to continue using the tools.
You can read about this in the MSDN Licensing White Paper. See the section called Perpetual Use Rights for more information.
answered Aug 28 '14 at 19:17
Per Salmi
724514
724514
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
add a comment |
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
The MSDN subscription was part of a Website Spark program. In any case I managed after cleaning up a lot of things to get it to forget the license. Since I can't pinpoint what worked, nor would I recommend yanking out the innards of Visual Studio configuration files like this, I'm not going to attempt to post an answer.
– Lasse Vågsæther Karlsen
Aug 28 '14 at 20:57
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f750341%2fhow-to-change-visual-studio-2013-license-information-from-msdn-to-visual-studio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Your MSDN license can't actually expire. You not having rights to use the license is a different question.
– Ramhound
May 6 '14 at 13:08
OK, good to know, but I would still like to fix this since my legal and valid license is not the one the software is currently using.
– Lasse Vågsæther Karlsen
May 6 '14 at 13:11
1
I believe the only way to resolve the situation is to uninstall it and installion package connected to your Visual Studio Professional Online license.
– Ramhound
May 6 '14 at 13:13