Version ⁨26.09.3 crashes

Anki Help
1

I’m posting here (not in the add-ons sub-forum) as I am not completely confident my issue is add-on related.

I have upgraded my anki desktop to: Version ⁨26.09.3 (29bb700b)⁩ Python 3.13.15 Qt 6.11.2 Chromium 140.

My system spec is Windows x64 PC: Edition Windows 10 Home, Version 22H2, OS Build 19045.7725.

Issue: When I open the anki executable, I see the usual elements at the top of the window:

  1. First line = "my-profile-name Anki"
  2. Line below = “File Edit Views Tools Help”

but nothing appears below that, although I have a great many sets of cards (as confirmed on ankiweb). Sometimes I get a complete crash.

I have tried uninstalling and installing slightly older versions, but with similar results.

In safe mode, as suggested by the trouble-shooting steps, I can see my card sets as usual. So I think this means there may be a sync-ing or add-on problem. Sync-ing seems ok in that it completes without errors, though I haven’t tested it specifically. So, perhaps it’s an add-on issue? But, when I look at ‘Tools/Add-ons’, I only see ‘anki-launcher’, which sounds fundamental and not like something I should delete as part of debugging.

I don’t think I have installed anything like an add-on myself, but I have imported other people’s shared decks in the past. Is it possible one of these is using a buggy add-on somehow, in a way I can’t immediately see? If so, how do I go about figuring out which is the problem deck, please?

Debug info below, from when I open in safe mode:

Anki 26.09.3 (29bb700b)
Python 3.13.15 Qt 6.11.2 PyQt 6.11.0
Platform: Windows-10-10.0.19045-SP0

Tools-Check database corrected a few issues. I sync-ed with the web. This did not resolve the local crashing issue.

Thank you in advance for any help you can offer.

2

We got a few reports of this. Switching the video driver should fix this: Troubleshooting - Anki Manual

But before doing that, can you run Anki from the console (See Startup Issues - Anki Manual) and post any text you get? This will hopefully reveal something.

3

Thank you. Here is the console output with the default Direct3D as in the original install:

image

You are correct, a switch to Software driver does solve the issue. (That’s my bad for not following the trouble-shooting instructions to the letter, sorry; I tried one change of driver without it solving the problem and concluded - incorrectly - that it was more likely to be linked to add-ons.)