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
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 just download visual studio community to my pc. When i opened the vs-2015 and create new Console application project. i can't find it any where under the c# we installed templates or any templates.
Thinking about to uninstall and install again but this not the first time i uninstall and install this, i did installed and uninstall few time but still can't find the web Console Application template.
Thank you.
I had the same problem and found the solution on another site. Here are the steps that need to be performed:
Open a Visual Studio command window with admin privileges. This can be done from Windows search after clicking on the Windows button (or Start button - depending on the OS) located in the lower left corner. Make sure that you don't have any Visual Studio project open before proceeding.
Type in prompt in the search box and select "Developer Command Prompt". Right click on this and select run with admin privileges.
In the command window Enter:
cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
In the command window then enter:
devenv /installvstemplates
This worked for me and I was able to create a new console project after this.
With my version of VS 2015 community edition, upon install there was a Console Application (Package) template available, which I mistakenly thought was a Console Application template. This is not the case. It is a web console application project and I only discovered this after trying to access the File and Directory classes in System.IO from my code. The compiler kept on complaining:
Error CS0234 The type or namespace name 'Directory' does not exist in the namespace 'System.IO' (are you missing an assembly reference?)
MyProject.DNX Core 5.0 ...
It still complained after putting in a reference to System.IO and even after changing the offending line of code to:
string DataPath = System.IO.Directory.GetCurrentDirectory();
A big clue here is the reference to DNX Core 5.0, which is an optimized run-time for ASP apps. It was at that point that I discovered that the Console Application (Package) template was also listed under the New Project window Templates / Visual C# / Web.
So, For others that may happen to find this post and think you are using a standard Console Application template, but have errors like "CS0234 The type or namespace "name" does not exist in the namespace..." then you could be using a Console Application (Package) template - which is probably not what you want and should be replaced by a regular Console Application. If you don't see it in the New Project window under Templates / Visual C#, then you should follow the steps above to install it.
EDIT
This is what my New Project window looks like after I performed the steps above:
Comparing this window with yours above, it appears to be somewhat different. Notice that "New Project" on my window is centered and for yours it is not. Also, at the bottom of the window yours has only Name, Location and Solution name, while my window adds a fourth item called Solution.
So, first thing, try clicking on Visual C# located in the left pane of your New Project window to see the templates available. Post that snapshot here. This can be done by selecting edit.
If you still don't see the Console Application template, then perhaps you downloaded a different version of Visual Studio 2015 than I did. So, here is the screen that pops up after selecting Help / About Microsoft Visual Studio on my system:
Compare this screen with yours and post a snapshot of your screen here. Also, what operating system are you using?
Thanks again Bob for your time to explained it to me, i am really appreciate that, I uninstalled and installed again from this link enter link description here, On my machine i have Visual Studio 2015(this one works) and Blend for Visual Studio 2015 is still missing template but i don't care it anymore if it work or not because i will use the one that works which is the Visual Studio 2015.
visual studio express 2013 for web is already installed on my windows 8.1 laptop.
Now i am trying to install visual studio express 2013 for widows with update 2.
It works fine until last step , but in last step "Configuring Your System, this may take a white" . it just goes like infinite loop. it just showing installing and progress
it has takes more than 3 hours and still same progress.
after i have decided to cancel the setup, but same problem in cancelling , just goes on and on.
after that i have killed the process from task manager. and then restarted the Laptop.
but after Restart the setup is started from where it left. and still the same issue.
Please Someone help.
either i want to cancel the setup, or to install successful. but nothing works its just goes like infinite loop.
any idea how can i do this?
I had the same problem today trying to install Visual Studio 2013 Update 3 from the 6.9 GB iso file I downloaded from MSDN. A few things:
1) First I stopped then disabled the Windows Search process since it seemed to be in a fight for the disk during the install. Note, disabling the service is not enough since something keeps turning back on. You have to right click on the service entry in the Task Manager Services tab and then choose Open Services option since trying to end the task directly from the tab will fail. From the Open Services option you can stop the Windows Search service and then change it's run status to disabled. Don't forget to turn it back on later when you're done with the install.
2) I looked in my Task List and I noticed there were some entries for the installer for Visual Studio 2013 RC 2. I had uninstalled that version because the design editor was crashing continuously. The uninstall was only partially successful. I wonder if it got launched in an attempt to clean up the previous uninstall. In either case, I ended the task for RC 2.
3) I also saw entries for the Windows Phone 8.1 emulator installers. I ended those tasks too.
The instant I did steps #2 and #3 the main Visual Studio installer perked up and said Setup Completed. My guess is that either the RC 2 installer or the Windows Phone 8.1 emulator installer got stuck and the main installer was waiting for it to return. I then clicked LAUNCH and Visual Studio 2013 Update 3 started properly. The good news is that the update worked fine.
The moral of the story is if you get the problem reported by the original poster, check for stuck sub-installers in your task list and get rid of them, but do not stop the main installer.
I've got similar issue. I solve it by going to process manager and killing all visual studio application process (i.e. emulator, visual studio 32b, visual studio for web...) without main process of instalation. After 5 minutes installation end.
I had the same problem with Visual Studio 2014 Update 3 hanging for hours at the very end of the install. The very second I ended the process described by Robert Oscler at (3) above "I also saw entries for the Windows Phone 8.1 emulator installers. I ended those tasks too." the install finished and I was ready to launch. This really worked thanks. If your not familiar with Task Manager here's what to do. To do it you press CTRL ALT DELETE together and pick Task Manager. If there is nothing showing press More Details bottom right. On the processes page scroll down until you see an entry that has Windows Phone 8.1 emulator (or similar) as a description. Click on any of these and just press the button that says end task on the bottom right. You need to be careful what processes that you end in general but it's fine to end Windows Phone 8.1 emulator in this case. Hope this fixes the problem for you and thanks again to Robert
I had Visual Studio 2013 Ultimate on my laptop and downloaded and installed VS 2013 with Update 2 on the same machine.
I got to that last step "Configuring Your System, this may take a while" and it took like forever. About 2 hours for me.
My take is that you wait for it to complete, maybe leave it finishing up overnight.
Another suggestion, assuming you installed "over" the original VS 2013 is to first uninstall it and the install VS 2013 with Update 2.
I have created a Windows Store 8.1 app and I'm trying to deploy on the local machine. The project builds correctly, but it is not deployed. Visual Studio 2013 looks like it is working but on the Output window I see following lines, and the deployments gets stuck there:
1>Creating a new clean layout...
1>Copying files: Total <1 mb to layout...
1>Registering the application to run from layout...
It doesn't show any errors.
I have tried by rebuilding the project and restarting VS, but I'm still not able to deploy the project.
Any ideas?
Renew your developer's license, then restart the computer.
Steps
Open any Windows Store apps project and go to the "Project" menu.
Select Store > "Acquire Developer License..."
In the Window, click "I Agree" (after reading all of the terms, conditions, and privacy statement, right?)
Sign in with your developer account.
If everything works, your developer license should be renewed.
Restart your computer.
Windows 10, VS 2013, VS 2015:
1.) Restart your computer
2.) check that under settings/update&security/for developer/'Developer mode' is enabled
3.) open elevated powershell (as administrator)
4.) enter: Get-WindowsDeveloperLicense
5.) enter: shutdown /r /t 0 (this will reboot your computer) and wait
6.) start VS, create a new project, built and run on local machine
also you might want to take a look at this link at MSDN
Yes, I know... I could set up a virtual machine running XP. Unfortunately our build environment is such that we need to be running VC2003, 2005 and 2008 concurrently and it would be much more convenient if I could run 2003 natively on Windows 7 for the few projects we have that require it.
I realize some things may not be available in the IDE, but I was able to run 2003 under windows Vista and if I could get the same base level of functionality under Windows 7 I would be extremely happy.
Right now I get an error opening the *.pdb file when I compile after switching vc2003 to run as Administrator under compatibility mode for XP SP 2.
Thanks!
Give XP Mode a try if you can't get it to run natively.
http://www.microsoft.com/windows/virtual-pc/download.aspx
I wrote a blog entry about this a while back that you can check out - http://technikhil.wordpress.com/2010/01/12/visual-studio-2003-and-windows-7-can-get-along-really/
The only thing I am stuck on right now is the global search functionality of VS 2003 - it hangs the application. My workaround is to use windows 7 search :-). Other than that - so far so good...
Update: I got the search to work as well by disabling the Aero functionality - I have updated my blog post with the details...
(Much of this repeats what's already been written above.)
I need to run VS2003 as adminstrator under Win7 64-bit, to support legacy projects (e.g. those that run on the original Xbox). The old XDK requires VS2003, so upgrading is not an option. I could run WinXP but I prefer Win7.
VS2003 is not officially supported under Win7 and trying to do so creates a couple of fairly annoying problems:
Find-in-files causes VS2003 to hang.
Linking fails due to a PDB file handle leak.
The Find-in-files hang is solved by using "Disable visual themes". Navigate to the VS2003 shortcut (Start-->Microsoft Visual Studio .NET 2003), right-click to get context menu, select Compatibility tab, Settings pane, and check "Disable visual themes".
The linker failure (LNK1201) happens when you run the program through the debugger, stop it, modify a file and build. The error is that a Visual Studio hold a handle to the PDB file, while the linker tries to write to that file. You can stop and restart VS2003 to bypass the issue. Works but is annoying.
You can also use the Microsoft SysInternals "handle.exe" utility to find, then close handles held by a process on a particular file. Write a script to call handle.exe and set up the VS2003 project to run that script as a Pre-Build Event. (See this thread.) But handle.exe requires running as admin.
You could hypothetically change handle.exe to run as admin using the usual steps (e.g. as a compatibility setting) but then handle.exe (apparently) runs in a nested shell, and then the stdout text does not get to the calling script.
You can make VS2003 run as admin, in which case the Pre-Build script also runs as admin, hence does handle.exe, and that works.
The remaining trick is to get VS2003 SLN files to open properly. If you simply make VS2003 run as admin automatically then the VS version selector fails to run VS2003. I don't know why, but it is the case.
You could associate SLN files to open using VS2003 devenv.exe instead of VSLauncher.exe. That works but then all new SLN files (2005, 2008, 2010, 2012, ...) fail to open.
So the final step then is to make VSLauncher.exe run as admin. This fails as of KB2492386 as this thread indicates. Uninstalling that update was the final step in this saga, to get everything to work.
PATCH NOW AVAILABLE
After some reverse-engineering, I found the incorrectly refcounted COM object responsible for the leak (it was off by 1) and developed a stable patch and corresponding article describing the fix. This addresses problems encountered while using Windows 7 thru Windows 10. Details and download available at:
http://bytepointer.com/articles/vs7.1_2003_on_win7_pdb_handle_leak_bug_unofficial_fix.htm
If you want to perform the patch manually, those details are also included.
NOTE: The SysInternals Handle tool workaround did not work for files on a network-share. The .PDB was not completely unlocked although the Handle tool claimed it was closed. My fix eliminates the problem once and for all and avoids any side effects.
Run this install. You need to run it from the setup directory, the setup.exe on the root of the cd will not work.
D:\setup\SetUp.exe /NO_BSLN_CHECK
Solution i found on the web which helped: For your visual studio, use application compatibility = windows vista SP2, and NOT WinXP SP3
I have a really dirty and pathetic workaround for the pdb problem.
Download and run Sysinternals-ProceXP, press CTRL-F enter the name of pdb(smt like ($ProjectName).pdb) that can't be created while linking. Double click when it is found.(if it can't be found run procexp with administrator priviliges)
Then you will see that the .pdb file is highlighted in the lower pane of the main screen. Right click it and select Close Handle. When you retry building your solution it wont raise an error.
I dont know if this solution can be scripted but it is at least better than restarting visual studio.
I've been using Visual studio 2003 on win7 since the very first RC edition was released :S
why do people have issues?
I have attempted to install VS2003 on Windows 7 64-bit using the Virtual Windows XP feature. I'm reasonably certain that this will be successful. The issue I ran into is that the installer wants IIS installed, and the XP installation provided by the Virtual XP doesn't have that enabled by default.
If you go to Add/Remove components, and try to add it, it will ask for the disc, which I didn't have on hand. Once I get my hands on the disc, I'm pretty sure that it will run fine.
If you haven't tried it for other apps, the Virtual XP feature is really neat...
I am experiencing the same issue; devenv.exe is leaving pdb files open after running the project. I have made a batch file to work around it, it closes all .pdb files open by devenv.exe:
handle.exe .pdb | awk "/devenv.exe/ { split($4, fd, \":\"); system(\"handle.exe -c \" fd[1] \" -y -p \" $3)}"
You will need to have handle.exe by sysinternals and awk by gnu in your path to make it work.
Use at your own risk. Closing handles can cause application or system instability.
In windows 7, there is the compatabiliy mode in the executable properties.
open:C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\
then right click on the devenv.exe and select properties. In the compatability tab, select the "Run in compatability mode" and select "Windows XP" in the dropdown.
Try that, I am not sure if it works, but it is worth a shot.
I am having no problems with Visual Studio 2003 on Windows 7 64-bit.
Navigate to VS2003 devenv.exe (probably C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe)
Right-click and select Properties
In the Compatibility tab, check "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 3)"
Check "Run this program as administrator"
I got Visual Studio .NET 2003 Working just fine on my HP EliteBook Workstation 8760W with an I7 processor and 12GB of RAM running Windows 7 Professional 64 bit by doing some advanced steps.
They go as follows:
Install FrontPage 2002 Server Extensions for IIS 7.0.
Install Visual Studio .Net 2003. Just skip when the installer command you to configure Frontpage 2002 Server Extensions.
Install .Net Framework 1.1 Service Pack 1 (download here).
Go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Highlight your machine, then double-click on ISAPI and CGI Restrictions. Change setting for ASP .NET v1.1.4322 to Allowed.
Then it will always show an alert with the following message
This program has compatibility issues...
just ignore that. Also, don't put it in compatibility mode in the properties of the IDE.
I did managed to install VS2003 on Windows 7 32 bit. However I had to do some IIS tricks in order to be able to run my ASP.NET project. When you install VS2003 Web Development component can't be selected. Basically you have to drop your VS2003 ASP.NET v1.1 into C:\inetpub\wwwroot\project_name and make it working on it's own as a standalone web portal first. Here is the steps I did.
Install IIS on Windows 7
Copy your VS2003 project to C:\inetpub\wwwroot\project_name. Right click on your project_name and Convert to application.
Following was my custom issue that didn't work until I enabled Windows Authentication even if I had no related settings in my web.config. Select your project_name > Authentication > enable both Anonymous and Windows Authentications.
Enable ASP.NET 1.1 in ISAPI and CGI Restrictions and make sure ASP.NET is added under ISAPI filters
Once I'm able to fire up my ASP.NET project in a browser go ahead and open project from your project location in my case is C:\inetpub\wwwroot\MHSScoreOrg\MHSScoreOrg.sln. I was able to run my project only when it was fully integrated on IIS.
I'm sorry, your build environment requires you to have VC 2003, 2005, AND 2008 running concurrently? I would really bet that your efforts would be better spent simply consolidating your build environment to just one environment.
Have you considered upgrading your solutions to vs2005, using MSBEE to target .net 1.1?