|T O P I C R E V I E W
||Posted - Jan 06 2022 : 1:38:43 PM
After updating VS 2022 Community Preview to version 17.1.0 Preview 2.0, extensions produced warning/error on startup, not being sure of this being due to extensions, I tried repairing the VS edition.
Note: The warning is about not loading microsoft.visualstudio.testtools.testcasemanagement.qualitytoolspackage correctly, referring me to "C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\17.0_########\ActivityLog.xml".
After the repair, extensions got removed as well of course. From this point on VA_X_SetupXXXX_0.exe has just shown the hour-glass. But no window of any kind appears, regardless of VS being open or not, and the installation is not starting/ is not successful.
Making sure it is not the VS version, I tried to install VS 2022 Community 17.0.4 alongside the Preview (even removed the Preview not to render VAX installer choose between the VS versions in the background and fail) without any success regarding VAX installation.
(But noticed that the warnings could be somehow related to ReSharper C++ extension(used alongside VAX previously without any problems besides a small lag), because after its installation on the fresh VS setup, the warning from before occurs right away.)
At the marketplace I found a VSIX version of the earlier 2420 VAX build. But it does not install due to lack of version support according to the logs. So updating from that build to the latest does not seem to be an option.
Any solutions/workarounds? Even some info about what the Setup executable checks that can make it stop/not start without any notice.
** Edited by Feline **
SOLUTION - if you are seeing this problem then you have probably installed a fairly recent build of Visual Studio 2022. If so then you are running into a bug that causes our older exe installers to crash when they try to work out which versions of Visual Studio you have installed.
To work around this can you please right click on the exe installer, select Properties, and go to the Compatibility tab in the properties dialog. If you enable "Compatibility mode" and set it to run in compatibility mode for Windows 7 the installer will load and run without any problems.
|25 L A T E S T R E P L I E S (Newest First)
||Posted - May 16 2022 : 10:42:03 AM
^ That sounds much easier.
||Posted - May 16 2022 : 05:47:36 AM
Alternatively, to work around this can you please right click on the exe installer, select Properties, and go to the Compatibility tab in the properties dialog. If you enable "Compatibility mode" and set it to run in compatibility mode for Windows 7 the installer should load and run without any problems.
||Posted - May 15 2022 : 3:06:33 PM
Yes, please ping email@example.com and we can send you a VSIX installer.
||Posted - May 15 2022 : 10:47:38 AM
Is there a workaround for legacy licences? I am using 2358 and now have no way of using my VAX after moving to VS2022
||Posted - Jan 31 2022 : 4:12:14 PM
||Posted - Jan 31 2022 : 4:07:29 PM
This issue (case 147623) is fixed in VA build 2022.1.
||Posted - Jan 27 2022 : 07:09:51 AM
fraggis email sent.
||Posted - Jan 26 2022 : 1:27:18 PM
Same here, could you send me the links as well? Thank you!
||Posted - Jan 26 2022 : 08:29:58 AM
@feline Thank you very much!
||Posted - Jan 26 2022 : 08:18:11 AM
gbehn email sent.
||Posted - Jan 26 2022 : 07:55:04 AM
Same Issue here. Had 2017, 2022 (17.1 Preview 4) as well as the non Preview Version of 2022 installed. Uninstalling Preview 4 made no difference btw.
||Posted - Jan 24 2022 : 08:00:31 AM
@feline. Thanks, works now!
||Posted - Jan 24 2022 : 05:52:53 AM
tbraun, email sent.
||Posted - Jan 22 2022 : 12:12:45 PM
Sorry everyone. If you are experiencing this issue, please upvote this developer community bug report to get this fixed!
||Posted - Jan 22 2022 : 11:34:03 AM
I'm also experiencing the issue that the latest 2440 installer does not work. It looks like it crashes.
I have VS 2022 and 2017 installed. Can I also get an alternate installer?
Microsoft Visual Studio Community 2022
Microsoft .NET Framework
Installierte Version: Community
Visual C++ 2022 00482-90000-00000-AA333
Microsoft Visual C++ 2022
ASP.NET and Web Tools 2019 17.0.795.42246
ASP.NET and Web Tools 2019
C#-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.
Linux-Kernspeicherabbild debuggen 126.96.36.199808
Aktiviert das Debuggen von Linux-Kernspeicherabbildern.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Microsoft Visual C++-Assistenten 1.0
Microsoft Visual C++-Assistenten
NuGet-Paket-Manager in Visual Studio. Weitere Informationen zu NuGet finden Sie unter https://docs.nuget.org/.
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
Testadapter für Boost.Test 1.0
Aktiviert Visual Studio-Testtools mit Komponententests, die für Boost.Test geschrieben wurden. Nutzungsbedingungen und Drittanbieterhinweise stehen im Installationsverzeichnis der Erweiterung zur Verfügung.
Testadapter für Google Test 1.0
Ermöglicht die Verwendung von Visual Studio-Testtools mit Komponententests, die für Google Test geschrieben wurden. Die Nutzungsbedingungen und Drittanbieterhinweise stehen im Installationsverzeichnis der Erweiterung zur Verfügung.
TypeScript-Tools für Microsoft Visual Studio
VC-Paket für Microsoft Visual Studio 1.0
VC-Paket für Microsoft Visual Studio
Visual Basic-Tools 4.0.1-1.21568.1+6ab6601178d9fba8c680b56934cd1742e0816bff
Visual Basic-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.
Visual C++ für Linux-Entwicklung 188.8.131.52808
Visual C++ für Linux-Entwicklung
Visual C++ für plattformübergreifende Mobile-Entwicklung (Android) 17.0.31822.380
Visual C++ für plattformübergreifende Mobile-Entwicklung (Android)
Visual Studio-Tools für CMake 1.0
Visual Studio-Tools für CMake
Visual Studio Code-Debugadapter-Hostpaket 1.0
Interopebene zum Hosten der Visual Studio Code-Adapter in Visual Studio
Visual Studio IntelliCode 2.2
KI-gestützte Entwicklung für Visual Studio.
||Posted - Jan 21 2022 : 06:05:18 AM
Email with the links sent, this should get you up and running nice and quickly.
||Posted - Jan 21 2022 : 03:05:11 AM
Could i ask for a link as well? I am experiencing the same issue with vs22 pro(preview), exe crashes instantly. Everything feels off without VSX :(
||Posted - Jan 20 2022 : 06:43:58 AM
There is a problem caused by the latest VS2022 preview, VS2022 Preview 2, which is causing our exe installer to crash. So far the problem only appears if you have this preview installed. We are looking into this:
Even with the preview installed the individual VSIX installers still work. I have sent emails with the links for the individual installers.
||Posted - Jan 19 2022 : 11:57:19 PM
I have the same problem. Can you email me a workable installer?
||Posted - Jan 19 2022 : 4:42:33 PM
I might be wrong but I remember that the .EXE which was not working had a different size (77841KB) from the current one(77840KB). Anyway, after a few days and a regular VS reinstall, I tried a fresh EXE (not knowing it might be new), and it works with an identical setup of VS as with which the EXE did not work.
Has anything been updated on the Whole Tomato/VAX side? If yes, what was the issue? :) Thanks in advance.
||Posted - Jan 10 2022 : 1:13:27 PM
Confirmed, uninstalling indeed has no effect on the exe installer. The preview that keeps on giving
As for errors with other plugins, I am also seeing this problem, and on a Windows 10 test system that has never had VA installed on it, so it is something about the preview its self. Hopefully that will all be worked out soon.
As for the installers, they have moved, I just need to get my instructions updated for the new location, which will make things a bit easier for everyone.
||Posted - Jan 10 2022 : 08:17:16 AM
Something is definitely wrong with the new preview because not only VAX but other plugins also have issues after the latest preview is installed. But I do not think the preview is the sole reason why exe installers do not work. Exes do not do anything even after the preview edition is removed and non-preview ones are installed. Something might have got messed up around the environment( even registry) too. But it is good news you could reproduce.
Is there an official site to get the individual vsix files, specific for VS versions, you are talking about? Because I got the one I could install for VS 2022 via support mail. And if the issue is not resolved until next VAX version release, updating might be an issue without those. :D
||Posted - Jan 10 2022 : 07:57:19 AM
Thank you for reporting this, I have just checked on a system with several versions of Visual Studio installed, along with the latest VS2022 preview, and the exe installer doesn't do anything. I did not check this at first, never expecting the preview to have this effect.
We are looking into this, thankfully the individual installers still work as expected.
||Posted - Jan 07 2022 : 2:24:47 PM
Thanks for the reply and help. I did install the VS 2019 since my last post. For it does have the VAX built in the extensions facility(VSIX), I managed to install it from within VS 2019 for that version exclusively. But somehow, even so, EXE installers terminate right away I execute them(tracked with Resource Monitor) and vanish from the services list after a few 10 seconds. The VSIX version of build 2440_0 provided separately via support mail works fine with VS 2022 though(now release/current edition, not Preview FYI).
||Posted - Jan 07 2022 : 07:22:30 AM
Do you have any other versions of the IDE installed, or do you just have VS2022 preview and release installed?
I ran into both problems yesterday, but wasn't sure if it was just a problem with my test system or not. Partly because I am seeing the warning/error on startup sometimes even without having VA installed, so I am not quite sure what is going on there.
For the installer problem, I have put in a bug report about this:
and I am emailing you a link to the VS2022 specific installer, which works correctly for me in this situation.