Visual Studio Repair Installation

[Amabella Batton]

Inmy scenario, I had just performed a user migration from one PC to an AWS instance and was not able to use VS 2015 Enterprise edition upon migration. I attempted to run a repair from "programs and features", run setup.exe from the ISO mounted to a drive on windows and even tried to run it from a disk and I couldn't get anything to run. What I had found was a reg key that led me to an idea of how to repair VS from an internal installer. The reg key that I found was:

which provided me with an install source for the currently installed version of visual studio. Within this registry key I found the "InstallSource" portion and followed it's location to other installers and uninstallers for Visual studio and other programs found at this location:

From here I went through each of the folders with a listing for v14.0...etc and was able to find the location for the vs_enterprisecore windows installer. From here I right-clicked the installer and ran a repair(you can choose to install, uninstall, or repair).vs_enterprisecore functions

This allowed me to repair visual studio and inevitably re-update my licensing information on visual studio. Prior to doing this I was receiving a dialog to sign in and that my license was invalid no matter how many attempts I made at logging in with my enterprise issued MSDN account. As you can see below my VS2015 is operational again with Enterprise 2015 setup and is able to check for an updated key once again! This took alot of work, spent at least 8-12 hours working on this to avoid a complete re-image! I hope this helps someone later on down the road!

You may have to remove any trace of what is left of it yourself. Even though the files of the installation are gone, the registry entries will still be lingering. You could try CCleaner to clean the registry. Typically when there isn't anything left and you try to uninstall from 'Programs and Features', Windows will ask you if you want to remove it from that list.

If you are seeing the fatal error for Built Tools x86. that's where I stuck with.First of all, remember your previous version of Visual Studio Installed in your PC. And search for online to download the build tools for the specific version of Visual Studio.Secondly, install the same and try to uninstall VS2015 with force command in an Admin privileged Cmd prompt.vs_enterprise.exe /uninstall /force

You could find the above file in my case 'vs_enterprise.exe' from the package cache under ProgramData/PackageCache and respective package version number which you need to explore online. If you couldn't find the above simply uninstall vs2015 from Program and features under Control Panel.

This has happened to me for the last 3 upgrades in Visual Studio Enterprise 2017 (now again on upgrade to 15.9.21).The fastest fix (and I'm not sure why) is simple and doesn't bomb your settings or take for ever.

If you have an offline installation like me and can't simply re-run the Visual Studio Installer you can edit devenv.isolation.ini and change the last line to read SetupFinished=true. It will detect your trickery and complain, but at least it will launch again.

Edit: I ended up getting the Visual Studio Installer to fix the issue after choosing the "Download then Install" option. Maybe I was too impatient when I initially stopped the update? My above answer is useful when you need to get work done that isn't affected by the broken features, but you will likely encounter problems later on.

just had the same problem (without any reason with) vs 2019 prof, after googling and reading on that topic, just went to vsix, looked for some individual component to install/uninstall, randomly picked cloud explorer, uninstalled it and some dependent components and VS 2019 prof started normally

For this problem, goto uninstall screen in control panel right-click visual studio and select option change, Installer page will open now, In that window without changing anything click modify. it will solve the problem. I'm using VS Professional 2017

After everything else I tried failed, I was able to correct this in VS 2022, by running the VS installer, then choosing Modify. Once there, I switched to the "Individual Components" tab and checked a component I didn't have installed (You may also be able to remove a component that you no longer need). Once that install completed, I was able to launch VS 2022 again.After the successful launch, you can remove the added component, if you don't need it.

I was able to find Visual Studio 2017 15.1 version and that worked, we saved a full download locally a few months ago. It was not obvious from the dev-essentials page where to get the earlier version.

from -us/articles/troubleshooting-fortran-integration-issues-with-visual-studio, there should be a integrate.bat for repairing/installing Fortran to Visual Studio. integrate.bat is missing from the directory for Visual Studio 2017. The article also mentions where to find the VFPackages for Visual Studio 2015. That folder on my computer does contain a integrate.bat but it looks like it is specific to 2015 but not sure.

I have tried installing older versions of VS, both community and professional (15.0) to no avail: the installer provided by MS for developers keep failing, and I cannot seem to be able to come by stand alone versions.

Unfortunately, we cannot confirm the statement that upgrading to VS2017 15.3.3 would resolve issues. In fact, we did a fresh install of VS 2017 15.3.3 and installed PSXE 2017 Update 4 after that. Already at the stage of checking the requirements, we were warned that no suitable Visual Studio IDE for the integration was found. We just went on with the installation, which went smoothly without errors, and found that the warning was correct: VS 2017 15.3.3 is working fine, but none of the PSXE compilers and tools are part of the Visual Studio IDE and cleary. there are no command line enviroments (tested on a Win7 Pro SP1 machine).

I strongly support the efforts towards Microsoft to avoid such things in the future. Personally, I tend to think that if their latest update messed things up by introducing "last minute features" as mentioned above, they should provide a remedy with their next VS update.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

According to the documentation , Visual Studio 2019 is supported for use with the ArcObjects SDK in 10.8. A 10.8 project I built in Visual Studio 2017 builds, but the add-in for the project is not created. In the past, this has been a culprit of the ESRI.ArcGIS.AddIns.targets in the XML code of the project file as documented here. I'm familiar with this and have made these changes in the past, but couldn't figure it out quickly on my new computer with fresh installs of Visual Studio and ArcMap. So, I decided to just create a new add-in project from scratch in Visual Studio 2019 to look for any differences that could be causing the problem. However, on the Create New Project screen (see screenshot), I couldn't find any ArcGIS entries as described in the documentation here.

Next, I went looking for the ESRI folder within the MSBuild folder referred to in the second link, so now I'm wondering if perhaps the SDK isn't being completely installed with Visual Studio 2019 installations. Has anyone else used Visual Studio 2019 with ArcMap and ArcObjects 10.8?

An uninstall/reinstall of the ArcObjects SDK fixed this issue for me and now the add-in is created and the templates show up when creating a new project. Performing a repair of the ArcObjects SDK on Friday did not work. I'm not sure why the initial install or repair didn't work- Visual Studio Community 2019 did appear (see screenshot) during setup and there were no errors during the install. Also, when troubleshooting the issue, I noticed it is possible to have Visual Studio 2017 and 2019 installed concurrently, recognized by the ArcObjects SDK setup program, and the SDK installed and working for both.

I think that's what I had done initially, otherwise I'm not certain the SDK would have installed, but I'm not positive at this point. If it does allow you to install the SDK without having Visual Studio installed first, then I'm guessing that's what I did initially and that was my problem. So yes, I would recommend having VS 2019 installed first, then install the SDK.

I uninstalled and reinstalled Visual Studio 2019 to try to get rid of this error and it persists, and fails to create a new . After reiinstalling Visual Studio, I started the vcvs2019_60 installer and chose the Repair option.

In an effort to remove a solution from Visual Studio yesterday, I uninstalled it and reinstalled it. Then, seeing no COBOL templates or information, I ran the vcvs2019_60 installer again and chose "Repair installation." That brought back the Micro Focus COBOL integration to Visual Studio, but I now get the Cannot talk to the license server on host "127.0.0.1", Server may not be running. error from Visual Studio so I cannot proceed with my COBOL tutorial.

3a8082e126