I might have found kind of a bug...

[UmbertoGuitar]

I frequently get this error message from Reaper:



I always thought that it comes from Reaper because it says so. But now I realize, I get it only but 100% when I load another project that also contains TX16Wx without ending Reaper before.

So to reproduce:
1. Load TX16Wx in Reaper and use it.
2. Close project but don't quit Reaper
3. Open other project that also contains an instance of TX16Wx
4. There you go, I get that message and Reaper terminates.

I can then start Reaper normally and load the other project, so it's more of an inconvenience than a real problem, but I thought I should tell you.

And maybe it's not TX's fault at all... I don't know

Windows 10/64
Reaper 7.05
TX- latest

[elcallio]

This sounds like you have somehow gotten the MSVC runtime libraries corrupted/version skewed. Please first try uninstalling TX16Wx, then re-installing. It should set up MSVC libraries correctly. If that does not work you might need to manually install the MSVC 2022 C runtime to correct it.

[UmbertoGuitar]

Thanks for your quick answer, I'll give it a try.

Edit:
Yes, that did it!
Normally I just update but I followed your advice and did a fresh install.
I uninstalled TX first then reinstalled and the problems seems to be gone!

Thanks again!

Edit Edit... I now remember, that the problem had disappeared after the 3.6 update but came back just recently. So it is quite possible that some other software installed an incorrect version of the runtime?

OK, but if the "repair" is so easy it's not really a problem... .

[elcallio]

The MSVC runtime should normally keep track of its own versions and make sure it is consistent for all applications, but sure, it is possible some software you installed managed to break the registration or what not.