TITITO is not starting / missing files ".dll"

Started by Xardeuss, July 16, 2025, 06:54:54 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Xardeuss

Good afternoon, everyone! How are you?

So, I had a small problem launching the TITITO app.

I installed it normally, just like I did with FET. However, when I click to launch the app, it alerts me with a system message saying:


"TiTiTo.exe - System Error

Code execution cannot continue because VCRUNTIME140_1.dll was not found. Reinstalling the program to fix the problem."

And also:

"TiTiTo.exe - System Error

Code execution cannot continue because MSVCP140_1.dll was not found. Reinstalling the program to fix the problem."


After that, when I click "OK," the same two messages reappear a couple more times each, and the screen closes.

I tried reinstalling the app as instructed, sometimes selecting the option to replace all files; I also tried deleting all the files and reinstalling everything.

I couldn't solve it. Can you help me with this problem, please?


Thank you in advance for your attention!

Volker Dirr

#1
hmm... I sadly have no idea at the moment how to fix that.

Did you use
https://www.volker-dirr.de/TiTiTo-8.7.1.exe
or
https://www.volker-dirr.de/TiTiTo-8.6.6.exe ?

Can you please also try the other one and tell me if the bug is there also?

Thank you!

Volker Dirr

Ok. I read some more. This missing dll files are not distibuted by me, Qt or the compiler that I used. The dll files should be in your Windows OS already.

So you might have an too old (or new? I hope not) Windows or your Microsoft Visual C++ Redistributable is damaged.

You can download the latest version from Microsoft.
See:
https://learn.microsoft.com/de-de/cpp/windows/latest-supported-vc-redist?view=msvc-170

You probably need this one:
https://aka.ms/vs/17/release/vc_redist.x64.exe

Please let me know if this helps.
Thank you!

Xardeuss

Good afternoon, everyone! How are you doing?

Volker, I managed to solve the problem by following your instructions! I just ran one more repair command from the command prompt at the end, and it worked perfectly! There were corrupted files in the Windows system itself, having nothing to do with your program. But, since your application had requested these files, I thought it might be a bug and rushed to report it, hahaha... I apologize for that!!

Thank you for your attention and help! ;D

Volker Dirr