Visual Studio 2022 editorconfig exclusion.dic randomly stops working

Question

In my solution I have an .editorconfig file with the following section:

[*.cs;*.md]
spelling_languages = en-us
spelling_checkable_types = strings, identifiers, comments
spelling_exclusion_path = ./.spell-checking.dic
spelling_use_default_exclusion_dictionary = false
spelling_error_severity = information

This works as intended:

• Visual Studio shows spelling mistakes in my code
• I can instruct it to "exclude" a certain word
• "Excluded" words are not shown as spelling mistakes anymore
• "Excluded" words are added to my spell-checking.dic file

It all works as intended, for a few minutes.

Every few minutes or so, entirely randomly, the spell-checker of Visual Studio goes haywire:

• It starts showing all of the words that I have previously "excluded" as spelling mistakes
• If I instruct it to exclude a word again, it adds it to my spell-checking.dic file even though the word already exists in that file

The only way to get the Visual Studio spell checker out of this haywire state is to close the solution and re-open it, or restart Visual Studio.

I used to have to do this several times per day. Due to unknown reasons, I currently have to do this several times per hour. Hence, this question on Stack Overflow.

Does anyone know of any fix for this?

---

I have Microsoft Visual Studio 2022 Community (64-bit) Version 17.12.4.

The only extensions that I have installed are "VsColorOutput64" and "Editor Guidelines".

I used to suspect that this was ReSharper's fault, but I have a fresh computer without ReSharper and the problem persists.

I used to suspect that this was happening if I opened two different files with the same filename from different directories, but it is also happening when I do not do that (although doing that seems to trigger the problem sooner).

I have tried calling my spell-checking dictionary exclusion.dic instead of spell-checking.dic, it makes no difference.

There used to be other problems in the past with the text encoding of spell-checking.dic, and with the UTF BOM, they seem to have been resolved, this problem persists.