The dialog says: SpellChecker Error SourceTree detected the following invalid Dictionary file references. These are known to cause performance issues. Do you want to remove these invalid dictionaries? I click "Yes" every time, and it still comes back the next time I start up.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

After updating to 1.9.9.20, I get an invalid Dictionary notification every time I start up, but it doesn't list any "invalid" files

Chris Traina

The dialog says:

SpellChecker Error

SourceTree detected the following invalid Dictionary file references. These are known to cause performance issues.

Do you want to remove these invalid dictionaries?

I click "Yes" every time, and it still comes back the next time I start up.

Accepted answers

Mikael Sandberg

If you un-check "Spell check commit comment" under Tools > Options it will go away. May or may not be the intended functionality in order to bypass Windows’ own spellchecker performance issues.

All comments

Mikael Sandberg

If you un-check "Spell check commit comment" under Tools > Options it will go away. May or may not be the intended functionality in order to bypass Windows’ own spellchecker performance issues.

Chris Traina

I had to un-check it, restart (the message was displayed again), re-check it, and restart again (the message was NOT displayed). Thanks!

Austin Kirchhoff

I am experiencing the same issue. The error message goes away if I disable spell checking of my commit comments, but the message comes back when I re-enable spell checking. I would like to keep spell checking enabled. Does anyone know any other workarounds?

Ackara Zangetsu

I am experiencing the same issue. It seems like every update introduces a new bug, you guys need to get it together.

Isaac PXS

In my case SourceTree had a "stuck" dictionary file. I had to delete it manually.

This is on Windows 10.

You'll need to first find the location of the file.

Open SourceTree's log file in <user directory>\AppData\Local\Atlassian\SourceTree\sourcetree.log

Look for where it says something like this. Most recent entries are at the bottom.

ERROR [2016-12-16 11:24:35,973] [1] [SourceTree.Configuration.WpfSpellCheckerPreFlightCheck] [Run] - Keeping dictionary reference [C:\Users\&lt;user&gt;\AppData\Local\Temp\u3vdz0px.dic]
ERROR [2016-12-16 11:24:36,524] [1] [SourceTree.Configuration.WpfSpellCheckerPreFlightCheck] [Run] - Removing non-existent dictionary reference []

Note the location of the .dic and delete it.

Ackara Zangetsu

I tried your method, it did not work, I'm still getting that message, it seems that sourcetree itself generating those invalid dictionary when it starts.

alex75

THIS one is the right answer.

In my case I deleted ALL the Temp folder content.
Next start of SourceTree showed the error but this time the list of disctionaires were there.
I clicked "Yes" (to remove the dictionaries), closed and restarted.
Error is no more there.

I also deleted the SourceTree_Url_ghasdhkfdsahkfg folder near the "SourceTree" one.
It contains a folder for every version you have installed (also the current one).
Bad idea. On the successive start of the program it begun the install procedure. I stopped it and restored the deleted folder (from the trash bin). Just 2 files about "configuration" (sorry, I haven't noted the names) was changed. I restored all with the old one.
Start again: OK.
I added this details to share the real experience I had but I think the solution was just to remove the bad disctionaries from the "Temp" folder.
version 1.9.10

Many thanks Isaac.

luttik

Yup @Alessandro Piccione that worked for me too.

vuistiner

After deleting all *.dic files from the temp folder, I still get the folllowing error as @Edward Savage:

ERROR [2016-12-29 18:39:48,560] [1] [SourceTree.Configuration.WpfSpellCheckerPreFlightCheck] [Run] - Keeping dictionary reference [C:\Users\bibi\AppData\Roaming\Microsoft\Office\15.0\bbae5a57\Proofing\RoamingCustom.dic]

The beginning of the file(RoamingCustom.dic) looks like this:

'
'Anita
'Daniel
'David
'Denis

I deleted the first line (the one with the single "single quote") and the error went away smile

mangapi

I had to delete dictionary file ( "dictionary.lex" ) which was is located at C:\Users\<username>\AppData\Local\Atlassian\SourceTree folder and restart SourceTree. Its working fine now.

Once the application started it recreated "dictionary.lex". The error is gone and spell check is working as it should.

I'm in windows 10.

Matt Slay

I tried deleting this file as you stated, but it did not fix the problem for me

Steve Pryce

I searched for .dic in the

C:\Users\spryce\AppData\Local\Temp\

folder, then deleted all. After restarting SourceTree I received the same invalid dictionary message however this time there was actually a list of invalid .dic files in the message. I confirmed yes to removing them and then restarted again.

Error message gone.

kloct_hlg

I looked in the registry key Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Spelling\Dictionaries in the _Global value it lists some files and I removed the one path where the file did not exist. It worked today for me. I hope it continues after the weekend

Matt Slay

Solved the empty list complaint!!

In the registry value:

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Spelling\Dictionaries in the property named "_Global_", there is a list of dictionary names. Right-click-> Modify on the value and the list of entries pops up in an edit window. Scroll down to the bottom, of the list there was a blank row with a carriage return, and I removed that row and it then stopped giving me the error where it complained when I launched it.

It was weird that after removing the blank line and I clicked OK, it popped up a message that said "Data of type REG_MULTI_SZ cannot contain empty strings. Registry Editor will remove all empty strings." I clicked OK on that message and everything is now fixed.

2017-01-21_5-23-01.png

Modify to get this widow, then remove blank line at bottom of list:

2017-01-21_5-30-04.png

When I clicked OK, it gave this warning:

2017-01-21_5-17-33.png

But now the problem is FIXED!!

2017-01-21_5-23-01.png

2017-01-21_5-30-04.png

2017-01-21_5-17-33.png

Austin Kirchhoff

This worked for me. I did not get the regedit warning either.

unknown

This worked for a day and then the error started occurring again. sad

Steve Pryce

This worked for me also, but it's just another band-aid solution. My last fix lasted for 2 weeks before I had the same issue again.

Steve Pryce

This lasted about 2 weeks for me. Since that time I've tried a few other methods, the last attempt lasted less than one day, but it seems these are all temporary clean ups and dont resolve the crux of the problem.

Scott Molinari

I solved this by turning off the commit spell checking option, restarting Source Tree, pressing "Yes" to removing the invalid dictionaries, then restarting Source Tree again. Problem was gone.

Scott

Bob Provencher

It's nice that people were able to work around this by turning off the feature, but that is not a fix. If Atlassian can't reliably fix the problem when you click yes, they should either fix it or remove the attempted fix.

Sean_Wilson

I had to delete the folders under "C:\Users\<username>\AppData\Roaming\Microsoft\Office\16.0", once I did that it resolved the issue. Just removing the .dic file didn't seem to be enough.