During update Visual Studio 2019 to latest version (16.9), setup failed. Stupidly I closed installer window without read the error.
When I retryed the update, the Installer crashes few seconds after start.
I have uninstalled wholly Visual Studio, but Installer still crash.
I think something is left dirty after first update fail, I tried to search in log files recoverd by collect.exe tools, but I can't found usefull information in that bilions of messages.
Reinstalling Windows must be the last choice, there is a way to take crash error for undertand the problem and search for a solution?
EDIT
Also InstallCleanup.exe don't solve the problem
Visual Studio Installer version 2.9.3349 has problems with culture "it-IT". If that's your case (as it is mine), there is a workaround here:
https://developercommunity.visualstudio.com/t/Visual-Studio-Installer-crashes-after-up/1356122
The workaround is to force a working locale: ./vs_installer.exe --locale en-US
If you think your install and/or installer is corrupted, run the installation cleaner tool available at the URL below and then re-download the latest installer, from which you can get 16.9.
https://learn.microsoft.com/en-us/visualstudio/install/remove-visual-studio?view=vs-2019
Additionally there is a step you can try in Troubleshooting Installation Issues, specifically Step 4 (The advice above the break is actually Step 6 in this process)
Step 4 - Delete the Visual Studio Installer directory to fix upgrade problems
The Visual Studio Installer bootstrapper is a minimal light-weight executable that installs the rest of the Visual Studio Installer. Deleting Visual Studio Installer files and then rerunning the bootstrapper might solve some update failures.
Note
Performing the following actions reinstalls the Visual Studio Installer files and resets the installation metadata.
Close the Visual Studio Installer.
Delete the Visual Studio Installer directory. Typically, the directory is C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Run the Visual Studio Installer bootstrapper. You might find the bootstrapper in your Downloads folder with a file name that follows a vs_[Visual Studio edition]__*.exe pattern. If you don't find that application, you can download the bootstrapper by going to the Visual Studio downloads page and clicking Download for your edition of Visual Studio. Then, run the executable to reset your installation metadata.
Try to install or update Visual Studio again. If the Installer continues to fail, go to the next step.
You have to download the installer again for the offline installation eg.vs_enterprise.exe then run vs_enterprise.exe --layout "folder where you have the offline installation". The new installer needs to download a different new configuration file vs_installer.version.json
https://learn.microsoft.com/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio?view=vs-2019
This morning I faced a problem while opening my Visual Studio solution, and when I tried to run it, it said:
No exports were found that match the constraint contract name
How can I fix this problem?
I solved this problem by clearing Visual Studio Component Model Cache.
Just delete or rename this folder:
%LocalAppData%\Microsoft\VisualStudio\11.0\ComponentModelCache
or
%LocalAppData%\Microsoft\VPDExpress\11.0\ComponentModelCache
and restart Visual Studio.
The version of Visual Studio you have is specified by the number e.g.
Visual Studio 2012 is 11.0 (as shown above)
Visual Studio 2013 is 12.0
Visual Studio 2015 is 14.0
Visual Studio 2017 is 15.0
Visual Studio 2019 is 16.0
For those that don't know:
%LocalAppData%\ is the same as C:\Users\{yourUsername}\AppData\Local
For those who have multiple versions of Visual Studio installed, e.g. 2012 and 2013, it might help to remove the ComponentModelCache for both versions before restarting Visual Studio, e.g. 11.0 and 12.0.
No need to rename or delete the whole folder:
(%AppData%\..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache)
Just rename or delete the Microsoft.VisualStudio.Default.cache file inside the above location.
Visual Studio Express 2012 has different paths.
Visual Studio Express
...\Users\{user}\AppData\Local\Microsoft\WDExpress\11.0\ComponentModelCache
With Visual Studio Express 2012 for Web
...\Users\{user}\AppData\Local\Microsoft\VWDExpress\11.0\ComponentModelCache
I did not have to re-install Visual Studio Express
This will really work like a champ:
Solution: Try to delete ComponentModelCache folder from the below location.
[C:]\Users\[your user name]\AppData\Local\Microsoft\VisualStudio\[Visual Studio version number]
And after successful delete, recreate the folder with the same name, "ComponentModelCache".
This issue can be resolved by deleting or clearing all the folders and files from %AppData%\..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
This actually clears the Visual Studio component model cache.
On Windows 7 machines, the path is different. When you type %appdata% in Run dialog, it opens the folder C:\Users\<username>\AppData\Roaming.
Click the 'up' button to navigate to the parent folder and select the folder 'Local'.
Final path: C:\Users\<username>\AppData\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
Deleting the Component Model Cache did not work for me (well, the relative directory given above did not exist in my machine). Instead, I installed an extension to Visual Studio 2012 Express. Menu Tools → Extensions and Updates... → Online → Choose any and then download. This apparently invalidates the cache causing Visual Studio to rebuild it.
Here's my source.
For Visual Studio 2013 you need to remove that folder from this path:
%AppData%\..\Local\Microsoft\VisualStudio\12.0
for Visual Studio 2012 and later versions, the solution must be deleting the content of the folder ComponentModelCache:
C:\Users\[username]\AppData\Local\Microsoft\WDExpress\11.0\ComponentModelCache
Visual Studio 2013
C:\Users\[username]\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
I had the same problem upon launching Visual Studio 2013 Ultimate, and the solutions here didn't work for me. I tried deleting the mentioned folders and starting Visual Studio again, but it didn't work.
However I had other problems too, like Microsoft.visual studio package did not load correctly and also Page '312e8a59-2712-48a1-863e-0ef4e67961fc' not found VS 2012. The latter refers to a message in the Team Explorer window saying "Page 'somenumber' cannot be found".
So I run devenv /setup on the Visual Studio command prompt with administrative rights. It did the job, and everything is fine now.
Remove ComponentModelCache folder content.
%AppData%..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
Clearing the folders didn't work for me. So I went to 'Programs and Features' and used the change button to startup the Visual Studio 2013 setup.
In the setup I choose the repair function and that fixed the problem for me.
I had the same problem with Visual Studio Express 2013 of Windows 8.1.
Unfortunatly there was no "ComponentModelCache" folder in
%AppData%..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache.
I found the "ComponentModelCache" folder in
..\Users[username]\AppData\Local\Microsoft\WDExpress\12.0
and solved this problem by removing this folder from there.
If you have VS 2013, you have to go to: %LOCALAPPDATA%\Microsoft\VisualStudio\12.0
then rename the ComponentModelCache folder.
I experienced a similar problem after some updates released from Microsoft (part of them where about .NET framework 4.5).
On the Internet I got the following link to the Microsoft knowledge base article:
Update for Microsoft Visual Studio 2012 (KB2781514)
It worked for me.
This happened to me with Visual Studio 2013 Web, after Windows installed several updates. Unfortunately none of the suggestions in this thread helped.
I had to re-run the installer and select the "Repair" option. After that (and a reboot) it was working once again.
In some cases you may have to repair more than one version of Visual Studio. One example is when a Script Task control in VS 2013 opens VS 2012 when you click Edit Script.
Renaming the ComponentModelCache folder worked for me in Visual Studio 2015, but with a slightly different path:
%AppData%\..\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
I have Windows 7 x64 with a second partition on which Windows 8 (preview installed). While working with Microsoft Visual Studio Express 2012 for Windows Phone, I come up with the same problem. But the ComponentModelCache is found here:
C:\Users\Jayaram\AppData\Local\Microsoft\VPDExpress\11.0
I am unable to delete or rename as I get the "access is denied" message when I try to use command prompt:
Administrator: VS2012 X64 CrossToolsCommandPrompt
This issue is because of a MEF cache corruption.
Installing the feedback extension (or installing any extension) will invalidate the cache causing VS to rebuild it.
click for source.
i experienced this problem in Microsoft Visual Studio Express 2012 for windows phone while trying to open file.
Then i browsed to
C:\Users\MyUserName\AppData\Local\Microsoft\VPDExpress\11.0\ComponentModelCache
And Inside ComponentModelCache i deleted Microsoft.VisualStudio.Default.cache CACHE file. Finaly i restarted visual studio and reopened my project.
Then my problem was solved, i was able to open file.
Note: My OS is windows 8. And i installed SDK 8 for developing windows phone app
Thanks
I am using Visual Studio 2012. After installing the Visual Studio 2013 web express, when I want to run or open any project in Visual Studio 2012 it shows me the following error:
"no exports were found that match the constraint contract name".
I also tried the above solution for clearing the ComponentModelCache,
but I did not find the folder. I solves my problem just by: Repair Visual Studio 2012
For the Express versions of the software, the folder you need is in a slightly different place(s): For Express 2012 for Web it is C:\Users\XXXXXXXX\AppData\Local\Microsoft\VWDExpress - not in the Visual Studio folder.
I got an error with the same error message - two years later.
It's a different problem this time though, related to .NET Core dnx things.
I couldn't find an answer on Stack Overflow, but there's a GitHub issue that contains a workaround: https://github.com/aspnet/Home/issues/1455
Below is the most important part of the workaround:
Delete the entire C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\Extensions\Microsoft\Web Tools\DNX directory. (As far as I understand, it belongs to the old version of ASP.NET Core
RC1, which for some reason is still shipped even with Visual Studio 2015 Update-3).
Delete the C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\14.0\devenv.exe.config file.
Run the Developer Command Prompt for Visual Studio 2015 as Administrator, and execute the devenv /setup command. The new devenv.exe.config file is generated. This time there are many assemblies that refer to the
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\DotNet directory.
Run the Visual Studio 2015 and check that it shows the Microsoft .NET Core Tools (Preview 2) 14.1.20624.0 in the Help => About Microsoft Visual Studio menu.
Thanks to olegburov's post on GitHub for figuring this out.
I had to uninstall some external components like Postsharp and Apex and then it worked. I also tried the chosen solution but it gave me more errors.
Deleting the folders haven't worked for me i have go control panel and repaired
Visual Studio Installer Projects extensions for VS 2013.
And it worked for me
I got this error after reinstalling IntelliJ IDEA and ReSharper for C# in Visual Studio 2013.
First, I got an error problem with extensions, and after this I got this error:
"No exports were found that match the constraint contract name”
I simply removed folder ComponentModelCache and resolved this error.
My 2 cents:
Following all above lifesaving tips, I had a slightly different experience; mine is VS 2017 Community Edition, installed once, and I notice that have all these 3 folders:
%LocalAppData%\Microsoft\VisualStudio\15.0 ==> Empty
%LocalAppData%\Microsoft\VisualStudio\7f0c75b0 ==> has only the CoreCon folder
This is the one that has the ComponentModelCache:
%LocalAppData%\Microsoft\VisualStudio\15.0_7f0c75b0
Deleting only the Microsoft.VisualStudio.Default.cache had no effect.
So, I deleted all 4 files there: .cache, .err, .external and catalogs.
On restarting VS, problem gone and appeared a 5th file:
Microsoft.VisualStudio.Default.scan
Removing ComponentModelCache did not work for me. Reinstalling VS 2019 did thanks to a recommendation on this Microsoft support thread.
Details
This seems to be a known bug with a fix incoming from MS (as of 1/7/2020)
Experienced after upgrading from VS2019 Pro 16.2 (i think it was?) to 16.4.2 using Visual Studio Installer
Error displayed when trying to launch both nuget console and nuget package manager
I installed Visual Studio 2010 Premium on my Windows 7 workstation. After loading a test C++ project, I noticed that it could not locate iostream. I took a look in C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include and noticed that only two files exist here, srv.h and wmiatlprov.h
I installed the VS2010 product on a test virtual machine, and this directory (...\VC\include) is filled with the usual collection of folders and headers (the materials you'd expect to find in the includes directory.)
I have taken the following steps to rectify the missing headers on the problem workstation:
Verified that I have no A/V software active (I am using MS Security Essentials, realtime is disabled)
Uninstalled Visual Studio 2010 Premium and all other sub-products from Programs & Features
Ran the VS2010 Uninstall Tool with the /full and /netfx parameters
Deleted the Visual Studio 10.0 directories from both Program Files and Program Files (x86)
Reinstalled Visual Studio 2010 from a freshly downloaded ISO from MSDN.
I also completed the above steps, but used a different edition for the reinstall, VS2010 Professional.
So far, nothing above has been able to produce an installed Visual Studio 2010 product with all of the C++ headers installed on my workstation.
Ideas?
The solution to this problem is as follows. It is based on the solution given in
http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing
Uninstall Visual Studio 2010.
Uninstall Visual Studio 2010 SP1 (despite the warning it gives).
Open Registry Editor (regedit).
Search for keys named PaddedVersion
Remove any parent keys VisualStudio\10.0\VC\Libraries, or similar (note the version number 10.0, which corresponds to 2010). Delete all of these registry paths. The search for the PaddedVersion key is just to ease up this search.
Install Visual Studio 2010.
Install Visual Studio 2010 SP1.
This solution may not be minimal, but it works for me. Hopefully others can confirm. The important difference here is that it is not just the HKEY_LOCAL_MACHINE from which the registry path must be deleted, as indicated in the link above.
While doing some research on this topic it seems like no matter how you uninstall Visual Studio there are always pieces left behind.
Two options to consider.
Option 1
Install VS 2010 on virtual machine.
Zip needed files from your virtual machine.
Copy and unzip them over to the workstation.
Option 2
Format hard drive.
Install fresh copy of Windows 7.
Install fresh copy VS 2010.
The Visual Studio installer is a fickle beast, to put it mildly. The generic diagnostic is that your registry is dirty, having a record of a sub-component of VS installed while it is not actually present anymore. There are a lot of sub-components and an enormous number of registry entries that keep track of their install state and their config. Finding such a dirty key back is a serious needle-in-a-haystack problem.
This kind of registry damage is very common if you ever had a beta or RC edition installed. I never had a beta version that didn't give me an enormous problem getting the RTM version installed. The VS2010 beta went particularly badly for me, albeit that I shot my foot badly by updating to Windows7 without uninstalling the beta. A gigantic mess, to put it mildly. You can expect similar kind of upheaval of you ever had an un/install that didn't complete. And of course registry damage is always around to turn this into misery.
The problem is quite common, there are Visual Studio cleanup tools around that aim to purge the registry after something like this happened. For VS2010 there are actually several. Google "vs2010 uninstall utility" to find them. No idea if they are different someway, no reason I can think of to not just run them all.
Chips are seriously down when that still doesn't fix the problem. Only thing left is to dig through the dd*.txt files that are left in the TEMP directory after an install. They contain a detailed trace of the installer's decisions. Beware that you'll drown in the amount of data.
I tried several rounds of uninstalling and reinstalling. The hack that finally worked was to copy the entire contents of the VC folder from a machine with a working VS 2010 installation. You probably don't need to copy all of these , but I was missing 3000+ files in include, lib, and other folders within VC.
I ran into this problem on Windows 8.1 when the VS 2010 Web installer failed to install correctly the first time. I followed Kaba's steps above with a slight difference and it solved the problem for me (so kudos to Kaba). The difference is that I deleted all the “VisualStudio\10.0” keys and all its sub-keys, as well as the “VisualStudio\10.0_Config” and sub-keys.
The solution at http://connect.microsoft.com/VisualStudio/feedback/details/774158/re-installed-visual-studio-2010-and-c-standard-headers-are-missing not worked for me.
After Uninstall Visual Studio 2010 and SP1, I used a registry cleaner software CCleaner and installed again. It fixed.
I'm trying to install the SP1 for Visual Studio 2010. I first installed the beta and it worked fine. Then I used the web platform installer to install the SQL CE Compact 4, which I assume installed the full SP1 after (this installation took over 12 hours, so I canceled it). The web platform installer told me that SP1 and Silverlight 4 was installed.
Visual Studio tells me SP1 was partially installed. So I downloaded the installer from the site and now it gives me this error:
Microsoft Silverlight 4 SDK - The feature you are trying to use is on a network resorce that is unavailable. Seeking application package 'silverlight_sdk.msi'.
How can I fix this error?
It's because Silverlight 4 isn't bundled with SP1 (apparently). Download Silverlight 4 tools, extract and point the SP1 error dialog to silverlight_sdk.msi. Should resolve it.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b3deb194-ca86-4fb6-a716-b67c2604a139&displaylang=en
To solve this problem you have to follow these steps:
Download "Microsoft Silverlight 4 Tools for Visual Studio 2010", but do not install.
Rename the downloaded installer file "Silverlight4_Tools.exe" to "Silverlight4_Tools.rar".
Extract the .rar file using tools like 7-Zip.
You can find the file silvelright_sdk.msi in the extracted files.
Go back to your Visual Studio 2010 SP1 installer. If you are still on the error window, click the browse button to browse and choose the silvelright_sdk.msi from the folder where you extracted the files.
I downloaded the offline installer and it worked fine.
I used the following link and it worked...
http://www.microsoft.com/en-us/download/confirmation.aspx?id=7335
After the execution of the web installer you will notice that a new directory has been created on the root of your C drive.
It would be a directory named like C:\961adfde6904297e47d06caaccf530. If you have many of those "strange named" directories you have to check the date modified and select the most recent. Inside that directory you will find the silverlight_sdk.msi file.
This is the file that is needed to be pointed by the "Use source" field of the "Microsoft Silver Light 4 SDK" installation error message.
Going on the installation, you may need the MSI file of the "WCF RIA Services v1.0 SP1". You can download it from WCF RIA Services V1.0 SP1 for Silverlight 4.
And then you can again point it to your error message.
I installed Visual Studio 2008 package FULL option. It worked with out any problem. I installed Vstudio 2008 and MSDN in separate folder in the D drive. 2 days later in order to remove my projects i uninstalled every thing and also i deleted visual studio 2008, visual studio 2005 folders from C:\Documents and Settings\IRCTC\My Documents. (I believe these 2 folders were automatically created when we install visual studio) also I cleared %path% and path (c/windows/path). Again I installed VISUAL STUDIO 2008 but now I can't able to create window application (other web, vb also), what is the solution for this ...
ERROR that shown is
c:/documents and settings/IRCTC/local settings/temp/g1zzsdl.bak/temp/windowsFormsApplication.csproj cannot be opened because project type (.csproj) is not supported by this version of visual studio.......
Whether any system file corrupted (windows temp or .net folber in windows).....
No other installation problem found in my system.....
please help.....
What are the files/folders required for the installation......
When you get that error is usually because:
You are trying to open a project created with a previous version of Visual Studio (not your case)
There was a bit of a screw-up during the installation (sounds like your case)
I'd uninstall the thing and reinstall completely first thing.
If it still doesn't work, it could be related to VS templates and you might wanna try and run from Visual Studio 2008 command prompt:
devenv /InstallVSTemplates
If it still doesn't work, open Visual Studio, in the menu, Open Tools->Options->Projects and Solutions->General. At this point you will notice the path of Project Templates is set to "C:\Documents and Settings[yourUserName]\My Documents\Visual Studio 9\Templates\ProjectTemplates" or something very similar to that. In order to fix it you gotta set that path to C:\Program Files\Microsoft Visual Studio 9\Common7\IDE\Project Templates or the same path according to wherever you installed Visual Studio
I don't think is related to VS project Templates though - see this link
Try and see what happens!
Why didn't you use visual studio's uninstall function available from the control panel|add/remove programs?
I would uninstall the latest installation as described above, and try again.