As you can see in my initial post, it's not a Windows problem.
Added the stack trace. Seems like it's connected to the key error.
Don't want to send my personal data that got corrupted due to an app error. As it first appeared the last few days, I doubt a direct relation with an earlier version (Last update 09.09.21). Also the relevant database was created in the end of August so this error from my perspective could at most be caused by the Android version before this one. But again it must be mentioned that the error first occurred at the end of October so this issue should definitely be investigated in detail as a direct relationship is at least questionable.