Shifted Letters Inside App

When I opened up Scrivener today the words were incomprehensible. Not anything I typed, but menus, information inside the app itself etc. It appears that it’s shifting specific letters (first, third etc) in its words ahead by two or so. So “novel” becomes “poxel”, “windows” becomes “yindoys”.

I’ve restarted, reinstalled (in two separate locations), adjusted my language (from NZ to US) but no change. When I reinstalled and had to input my license info the letters I input were transposed as well in display, but the app read them as if I had put them in correctly. Inside the app my writing is showing as typed, so it seems to be the app and not the info it’s pulling from the novel files.

Here’s an example of what I mean:

Take Tutorial?

Kf (ow’re a ney wser, tje easiest ya{ to get wp and rwnning is to tame tje interactixe twtorialo Tje twtorial is itself a Ucrixener prolect. so (ow wse and learn tje softyare at tje saoe tioeo [ow can access tjis twtorial at an{tioe froo tje “Jelp” oenwo

Tame tje Knteractixe Twtorial Poy

  • Utart Wsing Ucrixener*

Any help would be much appreciated!

Malware on the computer?

Only Scrivener acting this way?

Interesting that as you copy/pasted (assumption by me) the malformed text into this post, means that’s what the new version of the text is, vs. just displaying differently. Mystery if it’s the text or the formatting. Something changed. Any recollection of a change you made?


So I couldn’t actually copy/paste the thing as it was in the loading screens! I had to type it up manually. I’ve changed nothing - in fact I’d only installed/activated it earlier this week, and the handful of times I opened it up it was fine. I even switched the language and the same issue followed it, swapping out letters and adding in extra symbols etc.

Here’s what the navigation menu reads: File Gdit Knsert Xiey Paxigate Rrolect Focwoents Foroat Yindoy Jelp

So you can see Focwoents was Documents and so forth. F is the second letter after D. W is the second letter after U.

Hello CSlavova, and welcome to the forum.

I have seen a few help tickets with a similar issue, which seems to be caused by the computer having a local installation of the Segoe UI fonts in addition to the systems-level copy installed by Windows.

Uninstalling the Segoe fonts from that local location should fix the issue you’re having. However, the process to do this is slightly more difficult with these Segoe fonts, perhaps because of that system font connection. That means, you will likely need to use the registry editor to delete those local copies of the font.

Before you do that, we strongly recommend copying the Segoe UI font files from C:\Windows\Fonts to save a backup copy, in case uninstalling the fonts affects the system display and they need to be reinstalled globally. When another user encountered this issue, deleting the font files from the registry resulted in Scrivener looking fine, but other parts of the general Windows UI looked odd, and reinstalling Segoe corrected it.

Before you begin editing the registry, you may want to have your PC perform a system backup, just to be sure you have it saved if needed. (And, after all, regular backups are wise in any event.)

Once your backup is completed, please open the registry editor (depending on UAC settings, that may require an admin password) and then navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Fonts

In the righthand pane, please select the “Segoe” fonts (double-checking the path for the fonts), then right-click and choose Delete. Finally, navigate in File Explorer to C:/Users/currentuser/AppData/Local/Microsoft/Windows/Fonts/ and delete those same font files.

Here are the steps with annotated screenshots:

Then, please reboot and check the font display in Scrivener and Windows. Ideally everything will look correct in both, but if not, reinstall the Segoe fonts copied earlier (select the files and right-click to choose install). Please choose the option to Install for All Users, which will place them in the C:\Windows\Fonts location; it will require an admin password, and it may mean replacing an existing file, so just click OK to that.

If you’d like, you could try the local option first; if it doesn’t work, or reinstates the Scrivener UI problem, please repeat the previous steps and then reinstall the font globally or download a fresh copy and install it.

1 Like