Visual studio 2017 installer opens in taskbar but does not show
I am trying to install Visual Studio 2017 Community edition on my Dell laptop running Windows 10 64-bit. I download the community web installer and run the .exe file. The program shows it's extracting some files, then asks for admin permission, which I give yes, and then I only get an icon on the taskbar as shown in the picture below. It does not seem to run or anything. Even opening a second instance comes to the same dead end.
I have also tried offline installation by downloading the files via command prompt. But again after one stage, the process opens this installer.exe file and comes to the same dead end.
I am not sure if I am missing any other installations, or any other supporting libraries are corrupted. I have searched in other forums where they suggest the problem occurring due to multiple display setup or dual graphics adapter, but my setup is nothing like that. I have only Intel HD graphics running on my laptop monitor.
I need VS 2017 badly and any help is greatly appreciated. Thanks in advance.
Edit
I was able to run the visual studio installer somehow by changing the setup.exe to run in Windows 8 compatible setting. Now, after installing, if I run the VS 2017 application, I am getting the same kind of problem. I only get an icon on the taskbar, I dont get any VS 2017 Window.
After googling, I found a way to get the log file when the application starts. The xml document indicates 4 errors on startup. Looks like some components are unable to be loaded. I have no idea why. I am attaching the screenshot here of the log file showing the 4 errors. The entire log file - VS 2017 log file
windows visual-studio-2017 windows-installer
|
show 2 more comments
I am trying to install Visual Studio 2017 Community edition on my Dell laptop running Windows 10 64-bit. I download the community web installer and run the .exe file. The program shows it's extracting some files, then asks for admin permission, which I give yes, and then I only get an icon on the taskbar as shown in the picture below. It does not seem to run or anything. Even opening a second instance comes to the same dead end.
I have also tried offline installation by downloading the files via command prompt. But again after one stage, the process opens this installer.exe file and comes to the same dead end.
I am not sure if I am missing any other installations, or any other supporting libraries are corrupted. I have searched in other forums where they suggest the problem occurring due to multiple display setup or dual graphics adapter, but my setup is nothing like that. I have only Intel HD graphics running on my laptop monitor.
I need VS 2017 badly and any help is greatly appreciated. Thanks in advance.
Edit
I was able to run the visual studio installer somehow by changing the setup.exe to run in Windows 8 compatible setting. Now, after installing, if I run the VS 2017 application, I am getting the same kind of problem. I only get an icon on the taskbar, I dont get any VS 2017 Window.
After googling, I found a way to get the log file when the application starts. The xml document indicates 4 errors on startup. Looks like some components are unable to be loaded. I have no idea why. I am attaching the screenshot here of the log file showing the 4 errors. The entire log file - VS 2017 log file
windows visual-studio-2017 windows-installer
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32
|
show 2 more comments
I am trying to install Visual Studio 2017 Community edition on my Dell laptop running Windows 10 64-bit. I download the community web installer and run the .exe file. The program shows it's extracting some files, then asks for admin permission, which I give yes, and then I only get an icon on the taskbar as shown in the picture below. It does not seem to run or anything. Even opening a second instance comes to the same dead end.
I have also tried offline installation by downloading the files via command prompt. But again after one stage, the process opens this installer.exe file and comes to the same dead end.
I am not sure if I am missing any other installations, or any other supporting libraries are corrupted. I have searched in other forums where they suggest the problem occurring due to multiple display setup or dual graphics adapter, but my setup is nothing like that. I have only Intel HD graphics running on my laptop monitor.
I need VS 2017 badly and any help is greatly appreciated. Thanks in advance.
Edit
I was able to run the visual studio installer somehow by changing the setup.exe to run in Windows 8 compatible setting. Now, after installing, if I run the VS 2017 application, I am getting the same kind of problem. I only get an icon on the taskbar, I dont get any VS 2017 Window.
After googling, I found a way to get the log file when the application starts. The xml document indicates 4 errors on startup. Looks like some components are unable to be loaded. I have no idea why. I am attaching the screenshot here of the log file showing the 4 errors. The entire log file - VS 2017 log file
windows visual-studio-2017 windows-installer
I am trying to install Visual Studio 2017 Community edition on my Dell laptop running Windows 10 64-bit. I download the community web installer and run the .exe file. The program shows it's extracting some files, then asks for admin permission, which I give yes, and then I only get an icon on the taskbar as shown in the picture below. It does not seem to run or anything. Even opening a second instance comes to the same dead end.
I have also tried offline installation by downloading the files via command prompt. But again after one stage, the process opens this installer.exe file and comes to the same dead end.
I am not sure if I am missing any other installations, or any other supporting libraries are corrupted. I have searched in other forums where they suggest the problem occurring due to multiple display setup or dual graphics adapter, but my setup is nothing like that. I have only Intel HD graphics running on my laptop monitor.
I need VS 2017 badly and any help is greatly appreciated. Thanks in advance.
Edit
I was able to run the visual studio installer somehow by changing the setup.exe to run in Windows 8 compatible setting. Now, after installing, if I run the VS 2017 application, I am getting the same kind of problem. I only get an icon on the taskbar, I dont get any VS 2017 Window.
After googling, I found a way to get the log file when the application starts. The xml document indicates 4 errors on startup. Looks like some components are unable to be loaded. I have no idea why. I am attaching the screenshot here of the log file showing the 4 errors. The entire log file - VS 2017 log file
windows visual-studio-2017 windows-installer
windows visual-studio-2017 windows-installer
edited Jan 2 at 7:20
Shankar S
asked Dec 31 '18 at 12:49
Shankar SShankar S
801211
801211
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32
|
show 2 more comments
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32
|
show 2 more comments
1 Answer
1
active
oldest
votes
I solved this problem of mine by re-installing the windows. I don't know what was the root cause of the problem earlier but I had other features like VPN not working properly in my OS so I figured that its high time I do it.
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
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%2f53987725%2fvisual-studio-2017-installer-opens-in-taskbar-but-does-not-show%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
I solved this problem of mine by re-installing the windows. I don't know what was the root cause of the problem earlier but I had other features like VPN not working properly in my OS so I figured that its high time I do it.
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
add a comment |
I solved this problem of mine by re-installing the windows. I don't know what was the root cause of the problem earlier but I had other features like VPN not working properly in my OS so I figured that its high time I do it.
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
add a comment |
I solved this problem of mine by re-installing the windows. I don't know what was the root cause of the problem earlier but I had other features like VPN not working properly in my OS so I figured that its high time I do it.
I solved this problem of mine by re-installing the windows. I don't know what was the root cause of the problem earlier but I had other features like VPN not working properly in my OS so I figured that its high time I do it.
answered Jan 4 at 14:11
Shankar SShankar S
801211
801211
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
add a comment |
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
Great call, I think you solved a lot of problems like that (and got a few new ones that are manageable). As the saying goes: for minor problems reboot, for major problems rebuild. A problem removed are sometimes 10 problems solved. For now :-) - (been around for a while). Windows should offer a "revert to pristine" option so we could rebuild Windows without touching any data, but that is an entirely different matter.
– Stein Åsmul
Jan 4 at 21:13
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.
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%2f53987725%2fvisual-studio-2017-installer-opens-in-taskbar-but-does-not-show%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
Are you behind a proxy server?
– Stein Åsmul
Dec 31 '18 at 19:14
@SteinÅsmul, no. I am only using a direct connection.
– Shankar S
Jan 1 at 6:09
Did you check the VS2017 troubleshooting guide? I would have a look in the event log. Assembling all the log files would be the first thing I would do. Are you sure your account is an admin account by the way? With rights to elevate to "real" admin rights?
– Stein Åsmul
Jan 1 at 20:45
@SteinÅsmul, Yes, I am running on an admin account. As for the log files, I have edited the problem now that I was able to run setup, but stuck in opening the application. I have attached the errors snap above and also the log file when opening VS 2017.
– Shankar S
Jan 2 at 6:08
Don't have time to look at this. Let me lob some suggestions? Might not be very helpful, but here goes: I would try another computer if you can, even a virtual. Install minimally if so - just get a heartbeat first. You can also try installing as a different admin user on the box, but in your case that will almost certainly not work (can sort out profile-related issues and other nuisances). Any other people with Visual Studio in the office? Did you call support and ask about what .NET policies are in effect on the systems?
– Stein Åsmul
Jan 3 at 2:32