digiKam 8.8.0 crashes on Windows 10 after splash screen

Help
1

i all,

I’ve recently upgraded to digiKam 8.8.0 on Windows 10 (64-bit, fully updated). Unfortunately, the application crashes right after the splash screen when it begins loading media.

Steps I’ve tried:

  • Fresh install of digiKam 8.8.0

  • Uninstall/reinstall multiple times

  • Tested with earlier versions of digiKam as well

  • Same crash occurs consistently

Observed behavior:

  • Splash screen appears normally

  • digiKam crashes immediately when loading media

  • Main window never opens

Expected behavior:

  • digiKam should start successfully and load the media library without crashing

Additional notes:

  • No custom configuration applied; default settings used

  • I can provide a backtrace with debug symbols if needed (please advise on the best way to capture this on Windows)

Has anyone else experienced this issue on Windows 10 with digiKam 8.8.0? Any suggestions for troubleshooting or workarounds would be greatly appreciated.

2 Likes
2

I have the same problem on Manjaro Linux/KDE. Renaming config files does not help

3

Having this same problem, after it initially worked. It started not working. Windows install. Shows “loading albums…” as the last step on the splash screen, then goes away, and never starts. Any ideas how to solve or troubleshoot this? (I’m a newb)

4

I have exactly the same problem on a Win 11 PC. Everthing worked fine until I added a new collection on a NAS Drive. Tried everything @vincentywt has described (deinstalling, cleaning out registry, removing LocalApp files etc.). No success. Any suggestions?

5

Same (I think?) issue, opened a thread quite some time ago (“Digikam is not showing up“).

In my case something must have gotten corrupted on my system after a digikam crash, though, because v. 8.cant’remember used to work before, now it doesn’t.

8.4 works, every single version after that (including 9.0) doesn’t.

DebugView seems to point to a problem with SnoreToast.exe in the digikam root folder.

I don’t know if this issue is the same as mine.