Visual Studio Remote Debugger Failed to Start
I recently installed Visual Studio 2017 on my laptop (running Windows 10). I have a C++ project using the OpenCV and Eigen libraries, and it seems to compile correctly, but when I try to run the Local Windows Debugger, I get an error message that says:
Visual Studio Remote Debugger (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel
I ran the Repair tool it suggested, with no luck. I also checked for a solution online, and came across a support page (Link). I tried turning off my anti-virus and firewall as per the suggestions on the support page, but that didn't get rid of the error message. My laptop is brand new, and I just installed Visual Studio and the Remote Debugger, so I don't think it would be the case that the version of the Remote Debugger doesn't match with that of Visual Studio. All of the other suggestions are for people doing remote debugging, but I'm doing a local debug.
Any help/suggestions on resolving this issue would be appreciated.
visual-studio visual-studio-2017
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
add a comment |
I recently installed Visual Studio 2017 on my laptop (running Windows 10). I have a C++ project using the OpenCV and Eigen libraries, and it seems to compile correctly, but when I try to run the Local Windows Debugger, I get an error message that says:
Visual Studio Remote Debugger (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel
I ran the Repair tool it suggested, with no luck. I also checked for a solution online, and came across a support page (Link). I tried turning off my anti-virus and firewall as per the suggestions on the support page, but that didn't get rid of the error message. My laptop is brand new, and I just installed Visual Studio and the Remote Debugger, so I don't think it would be the case that the version of the Remote Debugger doesn't match with that of Visual Studio. All of the other suggestions are for people doing remote debugging, but I'm doing a local debug.
Any help/suggestions on resolving this issue would be appreciated.
visual-studio visual-studio-2017
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25
add a comment |
I recently installed Visual Studio 2017 on my laptop (running Windows 10). I have a C++ project using the OpenCV and Eigen libraries, and it seems to compile correctly, but when I try to run the Local Windows Debugger, I get an error message that says:
Visual Studio Remote Debugger (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel
I ran the Repair tool it suggested, with no luck. I also checked for a solution online, and came across a support page (Link). I tried turning off my anti-virus and firewall as per the suggestions on the support page, but that didn't get rid of the error message. My laptop is brand new, and I just installed Visual Studio and the Remote Debugger, so I don't think it would be the case that the version of the Remote Debugger doesn't match with that of Visual Studio. All of the other suggestions are for people doing remote debugging, but I'm doing a local debug.
Any help/suggestions on resolving this issue would be appreciated.
visual-studio visual-studio-2017
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
I recently installed Visual Studio 2017 on my laptop (running Windows 10). I have a C++ project using the OpenCV and Eigen libraries, and it seems to compile correctly, but when I try to run the Local Windows Debugger, I get an error message that says:
Visual Studio Remote Debugger (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel
I ran the Repair tool it suggested, with no luck. I also checked for a solution online, and came across a support page (Link). I tried turning off my anti-virus and firewall as per the suggestions on the support page, but that didn't get rid of the error message. My laptop is brand new, and I just installed Visual Studio and the Remote Debugger, so I don't think it would be the case that the version of the Remote Debugger doesn't match with that of Visual Studio. All of the other suggestions are for people doing remote debugging, but I'm doing a local debug.
Any help/suggestions on resolving this issue would be appreciated.
visual-studio visual-studio-2017
visual-studio visual-studio-2017
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
edited Aug 11 '17 at 14:20
Error - Syntactical Remorse
6081721
6081721
asked Aug 11 '17 at 14:10
Benjamin
12
asked Aug 11 '17 at 14:10
Benjamin
12
asked Aug 11 '17 at 14:10
Benjamin
12
12
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25
add a comment |
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25
add a comment |
1 Answer
1
active
oldest
votes
Firstly close the Visual Studio.
Goto AppDataLocalMicrosoftVisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
edited Nov 11 at 15:36
Zoe
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
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',
autoActivateHeartbeat: false,
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%2f45637290%2fvisual-studio-remote-debugger-failed-to-start%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
Firstly close the Visual Studio.
Goto AppDataLocalMicrosoftVisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
edited Nov 11 at 15:36
Zoe
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
add a comment |
Firstly close the Visual Studio.
Goto AppDataLocalMicrosoftVisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
edited Nov 11 at 15:36
Zoe
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
add a comment |
Firstly close the Visual Studio.
Goto AppDataLocalMicrosoftVisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
edited Nov 11 at 15:36
Zoe
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
Firstly close the Visual Studio.
Goto AppDataLocalMicrosoftVisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
edited Nov 11 at 15:36
Zoe
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
edited Nov 11 at 15:36
Zoe
11k73675
edited Nov 11 at 15:36
Zoe
11k73675
edited Nov 11 at 15:36
Zoe
11k73675
11k73675
answered Nov 11 at 15:34
shalitha senanayaka
1
answered Nov 11 at 15:34
shalitha senanayaka
1
answered Nov 11 at 15:34
shalitha senanayaka
1
1
add a comment |
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%2f45637290%2fvisual-studio-remote-debugger-failed-to-start%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
Also check the system and application event logs for any clue.
– Richard Critten
Aug 11 '17 at 14:11
In the application event log, there are four SideBySide errors, with the message "Activation context generation failed for "C:Program Files (x86)Windows Kits10bin10.0.15063.0armsigntool.exe.Manifest". Dependent Assembly Microsoft.Windows.Build.Signing.wintrust.dll,version="0.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis." There doesn't seem to be anything strange/recent in the system event log.
– Benjamin
Aug 11 '17 at 14:25