| Author |
 Topic  |
|
|
.oisyn
Tomato Guru
168 Posts |
 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:
quote:
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).
|
Edited by - .oisyn on Oct 16 2022 6:18:50 PM |
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
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.
https://docs.wholetomato.com/default.asp?W105
VS may complain on the next startup, but that should only happen once.
What version of Visual Assist are you using? |
 |
|
|
.oisyn
Tomato Guru
168 Posts |
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
Stable Includes:
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;
Other Includes:
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;
|
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
|
|
.oisyn
Tomato Guru
168 Posts |
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?) |
Edited by - .oisyn on Oct 16 2022 6:39:37 PM |
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
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? |
|
|
|
.oisyn
Tomato Guru
168 Posts |
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? |
Edited by - .oisyn on Oct 16 2022 6:45:09 PM |
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
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.
https://support.wholetomato.com/default.asp?W404
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. |
|
|
|
.oisyn
Tomato Guru
168 Posts |
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? |
|
|
|
Admin
Whole Tomato Software
USA
74 Posts |
Posted - Oct 16 2022 : 6:59:12 PM
|
| Yes. |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Oct 16 2022 : 6:59:30 PM
|
I tried anyway.
Turns out 2022.1 works! |
|
|
|
ChrisG
Whole Tomato Software
USA
299 Posts |
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. |
|
|
|
.oisyn
Tomato Guru
168 Posts |
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. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
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. |
zen is the art of being at one with the two'ness |
|
|
|
.oisyn
Tomato Guru
168 Posts |
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) |
Edited by - .oisyn on Dec 02 2022 6:07:02 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
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.
case=148884
Fingers crossed this helps to move us forward a bit. |
zen is the art of being at one with the two'ness |
|
|
|
lokeshgovindu
New Member
India
9 Posts |
Posted - Sep 20 2023 : 08:06:11 AM
|
| I am also facing the same issue, could you please help me. Thank you. |
Thanks,
Lokesh |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
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. |
zen is the art of being at one with the two'ness |
|
|
|
lokeshgovindu
New Member
India
9 Posts |
Posted - Sep 20 2023 : 11:16:07 AM
|
| VS 2022 Professional 17.7 and VA VA_X_Setup2502_0_Build2023.5. |
Thanks,
Lokesh |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 13 2025 : 6:20:22 PM
|
quote:
Originally posted by feline
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.
case=148884
Fingers crossed this helps to move us forward a bit.
Hi feline,
Unfortunately the problems have returned somewhat. I have again got a new license, and the initial process seemed fine. Then I installed the lastest VA, and it again complains about the security key not being valid.
This time no hang, but I get a dialog where I can enter a username and a serial number. For some reason, it prefills in the username with
quote:
REDACTED@REDACTED (1-user license) Support ends 2018.10.09
Yes, this is indeed a license I once purchased. Just filling in my new key doesn't work, nor when I change the name to my actual name I used when registring.
I've tried removing the current license as described in this topic, and deleting the C:\users\<username>\AppData\Roaming\Embarcadero folder, but it keeps getting this information from somewhere. |
Edited by - .oisyn on Apr 13 2025 6:22:24 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
Posted - Apr 14 2025 : 07:50:34 AM
|
Just to double check, since I have a horrible feeling I know what is going on here, you are getting an error message.
Title = Key Required
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 default setting (if any).
Followed by an "Enter Key" dialog, with two fields, "Name" and "Key", asking you to "Enter the registration name and key below, exactly as given to you."
If this is what happening, then the message boxes aren't coming from "us". This isn't how the VA license dialog looks or works. What is happening is that a black box license / security module is throwing an error, and putting up these messages. But because of this, a valid VA license will never be accepted, since it isn't actually asking for a VA license key.
Despite all sorts of tests and experiments, I have never been able to reproduce this problem here. Still, hope springs eternal. Do you have any "odd" tools or utilities installed? Anything that could possibly be detected as trying to hack the VA license module? Low level tools for driver development perhaps?
This component is a black box to us, and we simply don't know what is setting it off, hence the near hopelessly vague question.
As for a solution, ideally we need to get rid of this component, and replace it with something else that doesn't cause problems:
case=164266
Unfortunately for now all I can suggest for now is trying a different build of VA. We do know that this problem is build specific, so while one build will show the problem, often one build newer or older won't show the problem. This is a terrible answer, and I wish I had a better one for you.
You can download different builds of VA from this page:
https://www.wholetomato.com/kb/a/archive-of-visual-assist-builds-and-release-notes |
zen is the art of being at one with the two'ness |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 14 2025 : 09:49:26 AM
|
quote:
Originally posted by feline
Title = Key Required
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 default setting (if any).
Followed by an "Enter Key" dialog, with two fields, "Name" and "Key", asking you to "Enter the registration name and key below, exactly as given to you."
Yes, that's the one!
quote:
If this is what happening, then the message boxes aren't coming from "us". This isn't how the VA license dialog looks or works. What is happening is that a black box license / security module is throwing an error, and putting up these messages. But because of this, a valid VA license will never be accepted, since it isn't actually asking for a VA license key.
Ok, but I've had these key files in the past, as that was how older versions worked. And it somehow is still getting that information somewhere, seeing that it is actually quoting one of my older licenses. My current Windows install has lasted at least a decade so it definitely has some old data somwhere. I figure if I start with a complete fresh install of Windows I wouldn't be running into this issue, right? So we need to find out where it stores this information so I can remove it.
I assume in your attempts to reproduce this, you've also tried starting from a very old visual assist version with a license key file, and probably also do the old style renewal, and then upgrading it to current day?
I've tried running procmon to see which files and regkeys devenv accesses during startup, up until it shows that message. Unfortunately I get way too much data to be able to pinpoint the culprit. At one point I got it to show the new install dialog on startup after deleting some registry keys and the Embarcadero folder. After filling in my license info, all was fine. During that session, at least. The next startup of Visual Studio I was getting the error again.
Unfortunately, I was unable to repro this by deleting that stuff again. Perhaps I missed something.
I'll try older builds later todat when I'm behind my old computer again.
quote:
Do you have any "odd" tools or utilities installed? Anything that could possibly be detected as trying to hack the VA license module? Low level tools for driver development perhaps?
Not that I'm aware of, no. Just a very long lasting Windows that has been upgraded since Windows 8 and has seen various migrations to new harddisks and PCs over time. |
Edited by - .oisyn on Apr 14 2025 10:39:30 AM |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 14 2025 : 10:58:29 AM
|
I've bisected VA_X installs. I'll update this post as I go:
2556: bad
2511: bad
2500: bad (with hang like my issue 3 years prior!)
2491: good
2488: good
2471: good
Ok done. It seems 2491 (VA 2023.3) is the last good version.
I would argue you at least have some control over the whole process, given that I'm not getting the same result for each version, right? |
Edited by - .oisyn on Apr 14 2025 11:09:34 AM |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 14 2025 : 4:22:46 PM
|
I also found this topic: https://forums.wholetomato.com/forum/topic.asp?TOPIC_ID=20456.
Unfortunately, pasting an older 2-line activation key doesn't work for me like it did for that user.
I noticed I also still have Visual Studio 2015 installed. I'll try going back to a very old Visual Assist. |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 14 2025 : 4:31:06 PM
|
| Sigh. Sadly the older setups from 2018 simply immediately exit. Are they not Windows 11 compatible? |
|
|
|
.oisyn
Tomato Guru
168 Posts |
Posted - Apr 14 2025 : 4:54:43 PM
|
OMG I figured it out. Somewhat. Most of the keys I had are renewal keys. Unfortunately I no longer have access to the original key I bought somewhere in 2004. HOWEVER, in 2008 I asked for a 2-pc-1-user replacement, and I got a new full key (not a renewal). That one worked! It's all ok now.
Unfortunately I didn't have procmon running so I still don't know where it stores its key information :(. You should really try to figure it out so it can be properly removed from anyones PC. I hope I won't again suffer from this issue as I upgrade at a later date. |
Edited by - .oisyn on Apr 14 2025 5:40:50 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19164 Posts |
Posted - Apr 15 2025 : 09:04:51 AM
|
For the older installers instantly exiting, this is a known problem. You are seeing a bug that causes our older exe installers to crash when they try to work out which versions of Visual Studio you have installed. The trigger is VS2022 being installed, and running an older installer.
To work around this you simply need to 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. Easy if you know how, but until you have been told about this, hardly something you would know.
As for the license situation, this is fascinating, and not at all what normally happens. "Normally", if I dare use that word for a situation like this, when this error is happening, if you install a slightly different version of Visual Assist, it either shows the same error, or works perfectly, without you needing to re-enter or do anything with or about your license.
Needing to go back to an older license would make perfect sense if you were still using an old style 2 line license key, but in that situation you should get a different dialog, that prompts for the previous license key, actually asking for the previous key clearly. But once you have moved to the new license system the old keys should not be required.
Honestly I am not sure what happened here, but I am very glad you have managed to get this working again, and thank you for the update :) |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
"Wrong key" dialog makes Visual Studio unresponsiv
