|T O P I C R E V I E W
||Posted - Oct 16 2022 : 6:09:26 PM
I've had Visual Studio 2022 installed for a while now, but the latest VA version I was able to get in my support period didn't support it yet so I stuck to 2019 in the mean time.
I recently got a new license and installed VA in 2022. But now I can't use Visual Studio 2022 because VA complains about a key not being correct (probably because it still refers to my old license). I can't choose any of the dialog options because the whole thing just freezes and the Windows "program not responding" message pops up. Waiting for it doesn't seem to help in any way. Sometimes the process just kills itself.
The message is:
The security key for this program currently stored on your system does not appear to be valid for this version of the program. Select Yes to enter a new key, or No to revert to the defautl setting (if any).
|19 L A T E S T R E P L I E S (Newest First)
||Posted - Sep 21 2023 : 06:12:58 AM
I have mainly replied in the other thread where you asked about this:
||Posted - Sep 20 2023 : 11:16:07 AM
VS 2022 Professional 17.7 and VA VA_X_Setup2502_0_Build2023.5.
||Posted - Sep 20 2023 : 08:09:31 AM
Which IDE and version of VA are you using?
Do you know the support end date for your current license?
You can run into problems if you are trying to use a version that your current license doesn't cover, but you should be being told this clearly if this happens.
||Posted - Sep 20 2023 : 08:06:11 AM
I am also facing the same issue, could you please help me. Thank you.
||Posted - Dec 05 2022 : 07:48:25 AM
In recognition of your impressive experience with using VA, we have upgraded your support level to include emailing you at the latest email address
I have just sent an email to your current forum email address, hopefully it is clear. It's just a bit complex.
Fingers crossed this helps to move us forward a bit.
||Posted - Dec 02 2022 : 6:05:04 PM
Hi. I just got back here to see if there was an update and read your last message. I wondered why I never saw that email, but it appears this forum was still using a *VERY* old email address of mine that I haven't had access to anymore in ages :D.
Anyway, I've updated my email in my profile. I would appreciate it if you sent it again :).
(edit: wow, seriously. Registered in 2004. I've been here even longer than you have been :D)
||Posted - Nov 14 2022 : 12:51:37 PM
Apologies for the slow reply here, I am emailing you about this. I am wondering if this is somehow a profile specific problem, and the steps for testing this in VS2022 are a little complex.
||Posted - Oct 19 2022 : 6:54:06 PM
Just to let you know, I tried if I could update to a later VA version now that it was succesfully initialized once in VS 2022, but I can't. I'm still getting the same error message with builds 2451 and 2458.
Let me know if you need some more info like a minidump or something.
||Posted - Oct 16 2022 : 7:00:31 PM
Thank you, and good to know. We will see if we can get a reproduction going on our side.
||Posted - Oct 16 2022 : 6:59:30 PM
I tried anyway.
Turns out 2022.1 works!
||Posted - Oct 16 2022 : 6:59:12 PM
||Posted - Oct 16 2022 : 6:57:30 PM
Quick question before I try that. Can I run different versions of VA in different Visual Studios side by side?
As in, if I just check the box for VS 2022, will it leave the (newer) versions installed for 2019 and 2017 alone?
||Posted - Oct 16 2022 : 6:49:56 PM
Yes, you can restore the folder from the recycling bin and that should skip needing to re-register.
If you are willing to try one more build, please download and install 2022.1 from here.
I'm trying to see if it was a regression at some recent point, as I cannot reproduce at this time.
I will also be sending you a trial license, with activation instructions. I know you are registered but using the trial may help reset whatever is going wrong with the internal licensing system. It won't override your paid registration.
||Posted - Oct 16 2022 : 6:44:53 PM
Nope, still same issue.
When I start VS 2019 now I get the standard VA dialog asking me to register, which is what was to be expected, right?
||Posted - Oct 16 2022 : 6:40:55 PM
Yes, VANet17 is created when Visual Assist starts up (properly) in VS 2022. If it's missing, it just gets filled with the default values and that's fine.
Let's try resetting your licensing.
Please close VS first if it is running. Then navigate to %AppData% and delete the Embarcadero directory. Finally, navigate to the following registry key like you did before and delete the PortalUser, UserName and UserKey values if present.
Computer\HKEY_CURRENT_USER\Software\Whole Tomato\Visual Assist X
Does that seem to help?
||Posted - Oct 16 2022 : 6:28:30 PM
Yes. I uninstalled it and installed it again, and same issue.
Is there a way to wipe all settings? I've tried deleting the registry key but that didn't help (also, I don't seem to have a VANet17 yet, but I'm not sure whether I should have it?)
||Posted - Oct 16 2022 : 6:23:15 PM
Does the same key dialog appear if you download and install version 2022.2 from here?
||Posted - Oct 16 2022 : 6:20:48 PM
Well yeah I can enter Visual Studio. Starting devenv with /safemode is also an option. But I'd really like to use Visual Assist :)
This is what 2019 reports:
License: Non-renewable Personal *************
VA_X.dll file version 10.9.2458.0 built 2022.07.29
DevEnv.exe version 16.11.32106.194 Community
msenv.dll version 16.0.32002.118
Comctl32.dll version 6.10.19041.1110
Windows 10 10.0 21H2 Build 19044.2006
16 processors (x86-64, WOW64)
Language info: 1252, 0x413
Platform: Project defined
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Include\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\VS\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\VS\UnitTest\include;
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\include;
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.8\include;
Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.19041.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\VS\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfc;
||Posted - Oct 16 2022 : 6:14:09 PM
Sorry you are having this issue.
You can remove VA without starting VS by deleting the install directory in the extensions folder.
Here is how you can locate the extensions folder.
VS may complain on the next startup, but that should only happen once.
What version of Visual Assist are you using?