I was trying to install several extensions in Visual Studio 2022 17.0.5 version. But every time I am getting this error in the VSIX installer. Screenshot in link VSIX installer error
the installation log file shows the following lines-
1/15/2022 12:07:57 PM - Microsoft VSIX Installer
1/15/2022 12:07:57 PM - -------------------------------------------
1/15/2022 12:07:57 PM - vsixinstaller.exe version:
1/15/2022 12:07:57 PM - 17.0.5234
1/15/2022 12:07:57 PM - -------------------------------------------
1/15/2022 12:07:57 PM - Command line parameters:
1/15/2022 12:07:57 PM - C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\vsixinstaller.exe,/appidinstallpath:C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe,/skuName:Community,/skuVersion:17.0.32112.339,/appidname:Microsoft Visual Studio Community 2022,/culture:en-US,/noep,C:\Users\User\AppData\Local\Temp\VSIXf154kdcy.vsix
1/15/2022 12:07:57 PM - -------------------------------------------
1/15/2022 12:07:57 PM - Microsoft VSIX Installer
1/15/2022 12:07:57 PM - -------------------------------------------
1/15/2022 12:07:57 PM - System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at VSIXInstaller.App.SetGlobalLogger(IInteropLogger logger)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
I couldn't understand the log file. Can anyone please help me to figure out the issue going on? Thanks in advance.
Not a solution but a workaround: I encountered the very same error when removing Visual Studio 2019 to fully rely on Visual Studio 2022. Reinstalling a leight-weigth version of VS2019 to have access to its VSIXInstaller.exe worked for me.
Note: This seems not to happen on every machine. I tried same setup on a virtual machine and had no need for VS2019. So this might only occur on computers that had formerly an older version of Visual Studio installed.