I have a strange issue with a projects that I am trying to start from Visual Studio 2017 - project's exe file is getting blocked by Bit9. And it happens only with Visual Studio 2017, and the same is working with VS 2015.
What I can see from Bit9 screen is that msvsmon.exe is trying to run MyProject.exe and it gets blocked. I guess this is some setting on visual studio side but I cannot figure out what to change.
I looked on the internet and I checked Debug tab of the project, and Use remote machine was already deselected.
I have visual studio 2012 and visual studio 2017 in one x64 PC.
I can see that i have two iisexpress folders one under program files(x86) and another under program files
the iisexpress folder under program files(x86) has no iisexpress.exe file
but iisexpress folder under program files has iisexpress.exe file
when running a dotnet core MVC project in visual studio. it complains there is no iisexpress.exe under program files(x86)
The only thing I can comment is that your IIS Express installation is broken. iisexpress.exe must present in both folders, so that you can run both 32 bit and 64 bit of the process.
You found a workaround, but the ultimate solution is probably reinstalling IIS 10 Express.
Wanted to add this question to the pool in case someone has the same problem
I was unable to update Visual Studio 2017 on Windows 7 and got the following error:
Unable to install the files to target location. Error: The folder
'c:\Program Files (x86)\Microsoft Visual Studio\Installer' or a file
within it is locked by another program. Close any applications that
might be using it and try again.
The initial solution I found was to reinstall Visual Studio but felt that it might be unnecessary. The solution I found was to close down visual studio, go to "c:\Program Files (x86)\Microsoft Visual Studio\Installer", rename the folder "Installer" to something else then run vs_installer.exe from the renamed folder.
Hope that help someone.
I just recently encountered the same error while trying to update the Visual Studio 2017 installer on Windows 10. In my case, the c:\Program Files (x86)\Microsoft Visual Studio\Installer directory was locked because of virus/malware scanning software running in the background. After stopping that, the installation of the VS 2017 installer had no more problems.
What initially misled me about the source of the problem was that the process which had a lock on the files in that directory was the special System process in Process Explorer, so I was initially going down the wrong rabbit hole.
If you have malwarebytes then you can add to the allow list C:\Program Files(x86)\Microsoft Visual Studio and it will work.
I got it working by downloading the installer separately, rebooting, and running the installer directly.
VS Installer Downloads
I encountered this when trying to update VS2019. I could not rename the Installer folder. Rebooting didn't help. I tried uninstalling everything related to Visual Studio via Control Panel, but the uninstall failed. It removed everything except a subfolder containing VSIXAutoUpdate.exe and some dlls. The installer still would not run.
This final step allowed me to delete the Installer folder and do a fresh install of Visual Studio.
Open Task Manager > Processes Tab
End Process "VSIXAutoUpdate"
Delete folder "C:\Program Files (x86)\Microsoft Visual Studio\Installer"
TL;DR
Stop the Task Scheduler service and ensure no open handles for the C:\Program Files (x86)\Microsoft Visual Studio\Installer dir
Details
I just had the same problem, and even rebooting didn't help. So, I dug in!
Process Hacker revealed there was a lock on the following file by the System process:
C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXConfigurationUpdater.exe.
If I used Process Hacker to close the handle, it just immediately reopened again :/
I thought to check Task Scheduler (since it runs as SYSTEM in svchost), and sure enough there were tasks in there that run VSIXConfigurationUpdater.exe, even though they weren't actually running at that time.
So I stopped the Task Scheduler service, then used Process Hacker to close the handle on VSIXConfigurationUpdater.exe - and this time it didn't return! After ensuring there were no open handles on anything inC:\Program Files (x86)\Microsoft Visual Studio\Installer, the Visual Studio installer was able to update.
I found the culprit for me was Malwarebytes disabled this and all worked well. Hope this helps somebody.
I tried to run through the steps #Janspeed specified, but there were a couple of language folders in the resources directory that were corrupted/locked, so just renaming wouldn't work. I managed to copy most of the file/dir structure (minus the corrupted ones) to a new directory but had to run a chkdsk /f on a restart before I could get those folders freed up and deleted. Once I had this worked out, #Janspeed's steps worked fine, including just deleting the new directory that I had copied everything into.
I ran into this issue today, turns out it was MalwareBytes Endpoint Protection that was blocking the update which is rather annoying.
Luckily I'm the admin and developer so I was able to drop my laptop from the antivirus to enable the update and then re-add it but in a larger corporate environment with red tape this isn't great at all.
I had faced the same issue while updating Visual Studio 2017 and 2019. I tried to open the Visual Studio Installer directly as admin and then it worked as expecred.
Update kept failing when using the "Check for Updates" menu item in the VS2019 IDE. When I ran the Visual Studio Installer from the Windows Start bar it immediately prompted to download the latest version of the installer. Once that was done it then offered to update VS2019.
Yesterday I uninstalled Visual Studio 2015 and then installed Visual Studio 2017 Enterprise. Now I have the following problem when I try to open a solution (existings and also if I create a completely new one):
When I open "MySolution.sln" directly per double click or pinned from Taskbar, then the solution opens very shortly but then immediately closes again and I am at the plain Visual Studio start screen.
But when I open the solution from Visual Studio via "Open Solution" dialog, everything works as expected.
Has anybody an idea why this could happen? What is the difference between these 2 opening ways?
EDIT: The problem only occurs, when the solution is in a TFS source controlled folder.
I have been using Microsoft Visual Studio 2010 for a while when one day I go to make a new project and it comes up with "Creating project 'XInput' ... project creation failed" down the bottom of my screen.
I have been scouring the internet for many days to find a solution to this with no luckso I will list what I have done.
Changed my registry file permissions
Ran as Administrator
Made a new account
Uninstalled, reinstalled and once again uninstalled Visual Studio
Installed Visual C++ 2010 Express
Deleted the registry files and recreated them
Tried saving the project not on my external hard drive but my internal
Attempted looking at and editing the config file
I am able to open existing project but I just cant open any existing ones. Any help is greatly appreciated. I am running Windows 7 Ultimate (64-bit)