Cannot load Q# language extension
up vote
1
down vote
favorite
I installed the quantum development kit from the microsoft site:
https://www.microsoft.com/en-us/quantum/development-kit
But when I try to open one of the projects or create a Q# I get the message:
There was an error activating the remote language server, Q# Language Extension. For more details, please run devenv /log and examine ....ActivityLog.xml file.
I ran it and found:
ERROR
System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule) at System.IO.Pipes.PipeSecurity.AddAccessRule(PipeAccessRule rule) at Microsoft.Quantum.QsLanguageExtensionVS.QsLanguageClient.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__49.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.ThreadingTools.d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__47.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Q# Language Extension
So I have no intellisense and the *.qs files are not as Q# recognized.
Visual Studio 2017 15.9
Windows 10 1809
Any idea about this?
visual-studio visual-studio-2017 quantum-computing q#
edited Nov 15 at 18:55
JJJ
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
add a comment |
up vote
1
down vote
favorite
I installed the quantum development kit from the microsoft site:
https://www.microsoft.com/en-us/quantum/development-kit
But when I try to open one of the projects or create a Q# I get the message:
There was an error activating the remote language server, Q# Language Extension. For more details, please run devenv /log and examine ....ActivityLog.xml file.
I ran it and found:
ERROR
System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule) at System.IO.Pipes.PipeSecurity.AddAccessRule(PipeAccessRule rule) at Microsoft.Quantum.QsLanguageExtensionVS.QsLanguageClient.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__49.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.ThreadingTools.d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__47.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Q# Language Extension
So I have no intellisense and the *.qs files are not as Q# recognized.
Visual Studio 2017 15.9
Windows 10 1809
Any idea about this?
visual-studio visual-studio-2017 quantum-computing q#
edited Nov 15 at 18:55
JJJ
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I installed the quantum development kit from the microsoft site:
https://www.microsoft.com/en-us/quantum/development-kit
But when I try to open one of the projects or create a Q# I get the message:
There was an error activating the remote language server, Q# Language Extension. For more details, please run devenv /log and examine ....ActivityLog.xml file.
I ran it and found:
ERROR
System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule) at System.IO.Pipes.PipeSecurity.AddAccessRule(PipeAccessRule rule) at Microsoft.Quantum.QsLanguageExtensionVS.QsLanguageClient.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__49.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.ThreadingTools.d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__47.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Q# Language Extension
So I have no intellisense and the *.qs files are not as Q# recognized.
Visual Studio 2017 15.9
Windows 10 1809
Any idea about this?
visual-studio visual-studio-2017 quantum-computing q#
edited Nov 15 at 18:55
JJJ
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
I installed the quantum development kit from the microsoft site:
https://www.microsoft.com/en-us/quantum/development-kit
But when I try to open one of the projects or create a Q# I get the message:
There was an error activating the remote language server, Q# Language Extension. For more details, please run devenv /log and examine ....ActivityLog.xml file.
I ran it and found:
ERROR
System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule) at System.IO.Pipes.PipeSecurity.AddAccessRule(PipeAccessRule rule) at Microsoft.Quantum.QsLanguageExtensionVS.QsLanguageClient.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__49.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.ThreadingTools.d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageServiceBroker.RemoteLanguageClientInstance.d__47.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Q# Language Extension
So I have no intellisense and the *.qs files are not as Q# recognized.
Visual Studio 2017 15.9
Windows 10 1809
Any idea about this?
visual-studio visual-studio-2017 quantum-computing q#
visual-studio visual-studio-2017 quantum-computing q#
edited Nov 15 at 18:55
JJJ
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
edited Nov 15 at 18:55
JJJ
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
edited Nov 15 at 18:55
JJJ
29k147591
edited Nov 15 at 18:55
JJJ
29k147591
edited Nov 15 at 18:55
JJJ
29k147591
29k147591
asked Nov 15 at 10:35
blfuentes
1,57622544
asked Nov 15 at 10:35
blfuentes
1,57622544
asked Nov 15 at 10:35
blfuentes
1,57622544
1,57622544
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54
add a comment |
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
We have posted a new version of the Visual Studio extension (0.3.1811.1501) which we believe should fix the problem. Do you mind updating the extension and giving it a try?
answered Nov 21 at 22:30
El capi
1162
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53317490%2fcannot-load-q-language-extension%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
We have posted a new version of the Visual Studio extension (0.3.1811.1501) which we believe should fix the problem. Do you mind updating the extension and giving it a try?
answered Nov 21 at 22:30
El capi
1162
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
add a comment |
up vote
1
down vote
accepted
We have posted a new version of the Visual Studio extension (0.3.1811.1501) which we believe should fix the problem. Do you mind updating the extension and giving it a try?
answered Nov 21 at 22:30
El capi
1162
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
We have posted a new version of the Visual Studio extension (0.3.1811.1501) which we believe should fix the problem. Do you mind updating the extension and giving it a try?
answered Nov 21 at 22:30
El capi
1162
We have posted a new version of the Visual Studio extension (0.3.1811.1501) which we believe should fix the problem. Do you mind updating the extension and giving it a try?
answered Nov 21 at 22:30
El capi
1162
answered Nov 21 at 22:30
El capi
1162
answered Nov 21 at 22:30
El capi
1162
answered Nov 21 at 22:30
El capi
1162
1162
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
add a comment |
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
Thanks, I will try as soon as possible, I think in two days when I have access to all the environment and will let you know
– blfuentes
Nov 22 at 21:20
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
I can confirm the new version fixed this problem. I get intellisense, tooltips and file icons. Thanks for the quick update.
– blfuentes
Nov 25 at 17:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
great to hear and thanks for reporting!
– El capi
Nov 26 at 19:03
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53317490%2fcannot-load-q-language-extension%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
What language is your Windows installation in? We've never seen this error before, but we have a possible theory.
– Alan Geller
Nov 15 at 19:08
@AlanGeller I have 3 environments: Working: Windows 10 English. VS 2017 15.9 English - Not Working: Windows 10 German base but with English Language pack. VS 2017 15.9 English. Windows 10 Spanish. VS 2017 15.9 English . So the two machines were it is not working have a SO base in non english language.
– blfuentes
Nov 15 at 19:16
Ah -- that's consistent with our theory. I'll post here when we're able to publish a potential fix. Sorry about this!
– Alan Geller
Nov 15 at 23:58
@AlanGeller Thanks!. In the meantime I can continue using VS Code.
– blfuentes
Nov 16 at 5:54