1 (edited by mario17 2024-06-21 07:40:50)

Hi all,

Tried to install Kinovea on my Lenovo with AMD Ryzen 7 Pro 5850U  and can not open it, has logo for a split and then nothing.
Can anybody help what could be wrong, could it be about Ryzen CPU ?   It works fine on my other laptop with Intel.
v  2023.1.2
June 2024

Tx
Mario

2

Could you confirm the other laptop with Intel is also running 2023.1.2 or a previous version? I haven't had a lot of comments on 2023.1.2 so I'd like to make sure it's not a regression general to this release.

3 (edited by mario17 2024-06-22 05:53:09)

Hi Joan,
Just confirmed it's working OK on , Intel i5 8th gen.
Could be something special on my Ryzen Lenovo laptop which I bought used, I also have few problems with other software (Photo Mechanics).
I afraid that this laptop came from some special corporate environment.  But Overall I don't feel comfortable with Ryzen.

Any Ryzed users, will appreciate your feedback. I'm on Windows 10 pro 64.

Thanks to all
Best
M

4

I doubt it's related to the CPU to be honest. A number of people have reported a similar symptom over the years but I've never been able to reproduce it on any of my machines.
Based on the symptom I would say that since it flashes the splash screen it means the .NET framework is installed and compatible, but one of the system assembly that is dynamically loaded during the initialization is not found or not the right version. Or maybe one of the program's assembly or one of its dependencies has been put in quarantine by the AV.

See if you can try right click and "Troubleshoot compatibility".

older threads
https://www.kinovea.org/en/forum/viewtopic.php?id=1627
https://www.kinovea.org/en/forum/viewtopic.php?id=1167

5 (edited by mario17 2024-06-23 07:23:05)

Closer look revealed this problem, not sure if this the reason.
Checking it now.  My current driver is   dd 4/132022  30.0.1.14052.5  /as of June 2024/.

The Version of AMD Radeon Software You Have Launched Is Not Compatible...pa-300

https://www.reddit.com/r/techadvice/com … on_of_amd/

Easiest  solution is stay away from AMD/Radeon I  think.