Here, I have attached my error log.
1/30/2019 5:09:42 PM - Microsoft.VisualStudio.ExtensionManager.CorruptInstanceException: VSIX Installer has encountered a problem. To troubleshoot, follow the steps here: https://aka.ms/pc5ifb ---> Microsoft.VisualStudio.Setup.Dependencies.DependencyGraphConstructionException: The dependent package of 'Microsoft.VisualStudio.Product.Professional,version=15.9.28307.222' cannot be found: Component.8B84B9F8-7BCA-41C4-9235-EA560AA96519,version=16.4.0.49.
at Microsoft.VisualStudio.Setup.Engine.Initialize()
at Microsoft.VisualStudio.Setup.Engine.GetProducts()
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.IntializePackages()
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.GetPrerequisitesInternal(IInstallableExtension extension, ICollection`1 installedPackages, ICollection`1 installablePackages, ICollection`1 unresolvedReferences)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.GetPrerequisites(IInstallableExtension extension, IEnumerable`1& installedPackages, IEnumerable`1& installablePackages, IEnumerable`1& unresolvedReferences)
at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
--- End of inner exception stack trace ---
at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
I've run into a very similar issue.
Here is the log message:
Error Log Message
After hours of searching the internet, I finally was able to find the solution.
I wanted to post it here and give clear step-by-step instructions on what I did so that other people won't have to go digging around the internet as I did.
TL;DR: This is a solution for Windows computers only.
First, if you can, you should try to uninstall the extension first. To do that, go to the directory where VSIXInstaller.exe is installed
(should be located where default Visual Studio is installed; e.g. C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\VSIXInstaller.exe).
Then open a PowerShell window as an Administrator in the installation directory. You can also open PowerShell as an Administrator and direct yourself to that directory by using the cd command.
Then enter this command to uninstall forcefully: .\VSIXInstaller.exe /a /f /u:<GUID_OF_EXTENSION> (in your case, that would be .\VSIXInstaller.exe /a /f /u:8B84B9F8-7BCA-41C4-9235-EA560AA96519). Note that this may fail due to this dependency failure.
If that worked, then good, you can move on to the next step. If not, go to where the extensions are (C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions) and use some search program like Agent Ransack to search this package ID (and make sure to search it by content) and find the extension package folder that contains this package ID (to find the extension's ID refer to this). Once you've found it, delete that package folder to uninstall the extension manually. If this doesn't delete the package as well, then refer to this previously answered StackOverflow question, as there are some extension packages that may be installed on the system and need to be deleted from the Programs and Features from the Control Panel (if you are using Windows, that is).
Since this extension package is considered a dependency, you must also go and delete this extension from devenv.isolation.ini, vsga.isolation.ini, and blend.isolation.ini (they are all located under C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE if you are working with Visual Studio 2019).
Finally, using a search program (again I would recommend using Agent Ransack), go to %PROGRAMDATA%\Microsoft\VisualStudio\Packages and search for this extension's package ID (or package name; usually available from the extension.vsixmanifest in the vsix package Example Package ID). The search results should show which package folder is declaring this extension as a dependency. Delete that folder.
Once the extension is fully uninstalled, then you must find state.json and state.packages.json and delete the JSON properties that contain this package ID (or package name) (this solution was from this answer).
Once all of the above steps are done, you should be able to reinstall this extension. In my case, this issue was blocking me from being able to repair, uninstall, or modify Visual Studio completely, and following these steps allowed me to update Visual Studio.
I've run into a very similar issue, too.
Thanks for D.K, your answer works for me.
After I've installed Visual Studio 2022 Preview (version 17.1.0 preview 1.0), I want to update Visual Studio 2019 from 16.11.5 to 16.11.6. But its failed, and it show the following error message:
"The dependent package of 'Microsoft.VisaulStudio.Product.Enterprise,version=16.11.31729.503' cannot be found: Component.Microsoft.ML.ModelBuilder,version=16.7.6.2150501."
Error Message from Visual Studio Installer
So, I follow the steps of D.K's answer.
In my case I should delete the package of "Component.Microsoft.ML.ModelBuilder" for all steps, and the command of PowerShell should change to '.\VSIXINstaller.exe /a /f /q /u:Component.Microsoft.ML.ModelBuilder' in step 3.
Related
I'm trying to update Visual Studio 2017 RC from 15.0.25909.2 to 15.0.25914.0 and when I hit Update button it throws following error
Path to vsix file 'update' is invalid or you don't have required access permissions. Please check the path is valid and you have required access permissions.
Usage: VSIXInstaller.exe [/quiet] ...
...
I ran it as Administrator unfortunately same issue occurs.
Recorded Screen-cast is here
Thanks to #panagiotis-kanavos I did be able to solve the issue. For those who may hit the same wall, here is the steps I followed.
You need to locate Visual Studio Installer which is not in Start Menu!. You may find it at C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe
Once you run it, click on Update button.
It will probably give you errors like this
[232c:0020][2016-12-09T09:31:36] VSIX installer does not exist at 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VSIXInstaller.exe'.
[232c:0020][2016-12-09T09:31:36] Package '...' failed to uninstall. Return code: 2
Check the path and make sure VSIXInstaller.exe is there
Once again, click on Update button.
this time, it will throw a different error and if you open the log file that upgrade process provides, it should have full command details which is/are failing
🚨 WARNING 🚨 following code was in "my" log file and I placed it here "only for demonstration purpose", do not use it directly, check your log file to get correct failing errors
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VSIXInstaller.exe" /q /s /admin /appidinstallpath:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe" /logFile:"C:\Users\ciler\AppData\Local\Temp\dd_setup_20161209094800_001_GitHub.VisualStudio.log" /skuName:Enterprise /skuVersion:15.0.25928.0 /appidname:displayName /uninstall:c3d3dc68-c977-411f-b3e8-03b0dccf7dfc
Run that command in your Command Prompt and make sure you change the /logfile: filename in order to eliminate overwriting the existing one.
I am trying to install the Visual Studio 2015 Update 3, but I am receiving an error each time. I have tried both the web installer and the ISO, and I have also tried going into Control Panel/Programs and modifying the 2015 install. All of these result in the same error: "Setup Engine - The parameter is incorrect". I've read about some of the other issues with the installer, but I'm hoping somebody else might have seen this one or something similar. The logs always have the following error in them:
[1B10:1DA0][2016-07-18T11:39:28]e000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4}
[1B10:1DA0][2016-07-18T11:39:28]e151: Detect failed for package: Win10_Universal_CRT_SDK_Extension_SDK, error: 0x80070057
I have even tried to download the full installer for VS2015, but all installers seem to run through the same error. Any ideas on how I might repair this particular component so the installs will succeed?
Additional information, this is happening on a VM of Windows 10 running in Parallels 11.
Screen shot of installer failing
I found a similar issue here: https://connect.microsoft.com/VisualStudio/feedback/details/974081/visual-studio-update-3-installation-keeps-failing-error-message-setup-engine-the-parameter-is-incorrect
The reply from Heath[MSFT]:
The logs confirm that some of your Windows Installer product
registration is corrupt. For the first issue, open a command prompt
(preferably elevated to avoid multiple UAC prompts later) and run the
following:
start /wait msiexec /fomus {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} REINSTALL=ALL
That should get
you past the first problem. If it does not, manually remove the
product like so and re-install it from the package cache:
start /wait msiexec /x {284FA9A0-CEDD-81D3-5A19-5858E95FD0C4} IGNOREDEPENDENCIES=ALL
start /wait msiexec /i "C:\ProgramData\Package Cache\{A79F6653-6AF1-4AF2-BC15-F5D6C05E1E6A}v2.0.40326.0\packages\sptoolsDependencies\enu\WorkflowManagerTools_x64.msi" ADDLOCAL=ALL NOVSUI=1
(change the above file
WorkflowManagerTools_x64.msi according to your log file record) After
this, installing VS Update 3 should work.
I had a very similar problem which at its root exhibited the same issue identified above in the Visual Studio 2015 Update 3 setup error (I couldn't install SSMS 17.1 which uses the Visual Studio 2015 Isolated Shell). I tried the solution above which unfortunately did not work for me. I did some more digging through the vs_isoshell.exe log file and found lines similar to those below.
[6BE0:36E0][2017-07-13T13:05:36]i000: Error 0x80070057: Failed to convert version: to DWORD64 for ProductCode: {9A7E3828-17FB-3E0C-9B28-48493E01937A}
The ProductCode refers to the "Microsoft Visual C++ 15 x86 Debug Runtime - 14.10.24269".
A perusal of my installed programs showed I did not have this installed, and I was unable to install it again due to a later version being present (it turns out it was upgraded, or removed, when I installed Visual Studio 2017).
I did some more searching and came across this page which had steps I adapted to my situation. I performed the same registry profiling of the installer with Process Monitor and the same key was missing. I added a key called DisplayVersion (string - REG_SZ) to the path below with a value of 14.10.24629 and that worked.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\8283E7A9BF71C0E3B9828494E31039A7\InstallProperties]
Adding the key/value pair allowed the installation of the VS 2015 Update 3 Isolated Shell to finish successfully which in turn allowed the SSMS 17.1 installation to complete successfully.
I was installing Visual Studio-Community 2015, and I got the error (0x80070643), also known as Team Explorer Fails. The installer runs for a while, and then outputs this: (Screenshot) I have used microsoft repair tools, reinstalled the redistributables, checked the hash, (fine) and run a SFC scan, (fine). I have been searching everywhere, yet I am to have found a solution. Here is the log, (shortened, because it is massive): (Error Log)
That error code is generic in that it just means "Fatal error during installation"
You need the installation log of the particular MSI that failed.
Do you have that already? Look in your temporary directory (i.e. just type in %TEMP% in the windows explorer address bar and hit enter) for something like "dd_vs_version info_vs_teamExplorerCore.log"
If that's not there, you might be able to manually execute the MSI yourself and capture a log:
From a command prompt (ideally elevated) you could run the command:
msiexec /l*v "%TEMP%\teamexplorer.log" /i "*full installer path*packages\TeamExplorer\Core\vs_teamExplorerCore.msi" MSIFASTINSTALL="7" USING_EXUIH="1"
You need to update that command so that the path to the MSI is correct. If you've downloaded the ISO, then it will be in there; otherwise, while you're running the installer, you can probably find it under the package cache, e.g. C:\ProgramData\Package Cache{48992F68-BEE6-35D8-89AC-6A81406F1096}v14.0.24712 looking at the log.
Using a tool like Void Tools Everything will make it easy to find the MSI and logs amongst a sea of temporary folders and caches.
After installing Update 4, I now find myself unable to build (or even clean) any solution. I keep getting:
Error 1 The "CheckPathAttributes" task could not be loaded from the
assembly C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.Tasks.dll.
Could not load file or assembly 'file:///C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.Tasks.dll'
or one of its dependencies. The system cannot find the file specified.
Confirm that the declaration is correct, that the assembly
and all its dependencies are available, and that the task contains a
public class that implements
Microsoft.Build.Framework.ITask. HandlePageNotFound
Does anyone know how to resolve this please?
Well, here's "my solution".
First the horrific "prompt of death" (plus the same "licensing issue" annoyance) in this post:
What I've attempted (and result) based on info from the interwebs:
Close VS 2013 and rename the folder:
C:\Users\[your user name]\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
Result: No effect/errors persist (VS will re-create that folder on startup)
Rerun the Visual Studio Update 4 installer and Repair
Result: Successfully "fixed" whatever it was.
This will take about an hour which is slower than when I originally installed the update so that was a clue, or rather, more like "well, I hope that means it found what it did wrong or forgot/missed out on" (and not, "oh crap, now I'm really screwing things up even more")
A quick summary of my environment so that hopefully will guide you to your solution:
I did install Office Developer Tools Nov 2014 prior to the Update so in my case, that wasn't the issue (I did not remove/uninstall)
I have Resharper, and I did not disable it, so this too doesn't seem related (some have pointed this out)
I did update to Web Essentials 2013 for Update 4 after the initial Update (it will prompt you to after installing VS Update 4). I didn't do anything after the Repair (didn't remove/re-install/etc Web Essentials after the Repair).
I have VS 2012 as well, just mentioning this though that was never affected in any way (and was my fallback while this issue was stopping me from using VS2013)
Hth...
Found the solution via this
TransformXml task could not be loaded from Microsoft.Web.Publishing.Tasks.dll
In my case, I had Visual Studio 2012 installed on an E: drive already, so I found a copy of Microsoft.Web.Publishing.Tasks in
E:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web
So I copied that file, and Microsoft.Web.XmlTransform to here:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web
and now all is well :)
Uninstalling "Office Developer Tools for Visual Studio 2013 – November 2014 Update" helped me. Now all works as before.
If you have VS 2012 installed on your machine. Copy Microsoft.Web.Publishing.Tasks.dll and Microsoft.Web.Publishing.targets from C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\web\ into C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web (the path for VS 2013). Restart visual studio.
I have only VS2013 (now with Update 4) and I solve this problem as follows: Close VS, copy "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.Tasks.Dll" into the "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web" directory and start VS (folder v11.0 no contains Web subfolder). Now I can rebuild website projects without any error again.
My problem cleared thanks to the same TransformXml link and the suggestion to install Windows SDK for Windows 7 and .NET Framework 4
Copying "Microsoft.Web.Publishing.Tasks.dll" and "Microsoft.Web.XmlTransform.dll" from "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web" to "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web" also works
I've seen a confusing behavior regarding the MSI files generated by a VDPROJ file. If I build my MSI in Visual Studio and then right-click and pick "Install" from within Visual Studio, it will automagically uninstall any version that is already installed and then install the new MSI.
However, if take the generated MSI and run it directly it will complain if a previous version is already installed. I have to uninstall it explicitly (in Add/Remove Programs) first.
What's the deal? Is there a command-line argument that Visual Studio executes the MSI with?
Yes Visual Stuido will be passing the REINSTALLMODE and the REINSTALL properties to the windows installer when it runs your install
something like:
msiexec /i your.msi REINSTALLMODE=vomus REINSTALL=ALL
Check the MSDN documents linked above to see what these options are doing
Edit:
Now I come to think of it. Studio may also just be uninstalling your application first by using the /x command line arg
msiexec /x <package> or <product code>
Maybe someone else can confirm which is being used?