1 Topic by Jotter6330

  • Jotter6330
  • -
  • Offline

Hi all,

I've used Kinovea for several years however recently my PC has been updated to Windows 11.
Since then I am not able to get passed the loading screen. I have uninstalled my version and installed the latest, or older versions and all have the same problem.
Multiple colleagues use Kinovea on exactly the same hardware/software and Windows version without any issues.

Perhaps one of you can point me in the right direction?
Thanks in advance!

2 Reply by joan

  • joan
  • joan
  • Admin
  • Offline

There have been several similar reports over the years but unfortunately I've never been able to reproduce it, so I don't know what to investigate. I have tested on several Windows 11 machines including a fresh install and never got the problem.

3 Reply by Jotter6330 (edited by Jotter6330 2024-10-09 07:44:22)

  • Jotter6330
  • -
  • Offline

Thanks for your reply.
If I wait approximately 10min it will launch however when opening a MP4-File (not file specific) Kinovea crashes.

From the log file I retrieved the following errors:
612057 - ERROR - [Main] - RecoveryManager - Recovery data were found but the referenced file couldn't be found.
726480 - ERROR - [Main] - FileBrowserUserInterface - Error while adding path to file watcher. Z:\

4 Reply by joan

  • joan
  • joan
  • Admin
  • Offline

Very interesting. So maybe it's the file explorer thing that's blocking everything for certain people. This part of the code is based on some truly ancient Windows APIs.

Do you have network drives bound to drive letters? Or some other slightly atypical things that might trip it up?

5 Reply by Jotter6330

  • Jotter6330
  • -
  • Offline

I tried to select "This PC" from the browser and that triggered a crash.
By my knowledge there aren't any weird things that could trip the program, there are 3 network locations and 3 drives all accessible via the file explorer.

Is there a method to prevent Kinovea from loading all locations in the browser? Maybe that can help me troubleshoot the problem and pinpoint it to a location.