Fix Windows font display problems with the right remedy

In the process of using the computer, sometimes we will encounter some font display problems, such as some fonts in the system display is incomplete, or some files open into a garbled code. The following author will combine some common font display problems, analyze the causes and introduce the corresponding solutions.

Failure 1: System font display is incomplete

If the interface fonts of some programs suddenly appear incomplete when the system is in normal use, most of them are caused by Windows font cache errors. The solution is to reset the current Windows font cache. You can first find the font cache service “Windows Font Cache Service” and stop it (Figure 1). Then start Powershell as administrator and execute “Get-ChildItem -Path C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache -File | foreach { $_.Delete()}” and “Remove-Item C:\Windows\System32\FNTCACHE.DAT” commands to clear the font cache file (Figure 2). Finally, restart the “Windows Font Cache Service” service.




If there is a problem with all screens on the system, then the problem may be caused by damaged system files. You can try to scan the system and repair the system files using the commands “SFC /scannow” and “DISM /Online /Cleanup-Image /RestoreHealth”.

Failure 2: After installing and uninstalling fonts, the system or part of the software interface font display problems

In order to beautify the system, some of you will install many fonts in the system. However, since some font files may not be compatible with Windows 10, so it will be easy to malfunction when calling that font display. In this case, you can try to restore the default settings of fonts to solve the problem.

Open “C:\Windows\Fonts” and click “Font Settings” in the left pane, then click “Restore Default Font Settings” in the opened settings window (Figure 3). Figure 3). Then the system will use the default font to display, for example, the system interface and menu will use the “elegant black” font to solve the display problems caused by using non-default fonts in these interfaces.


However, to restore the default settings, you need to have the corresponding font files on your system. If some of you delete the font file when optimizing the system, it may cause the system interface or program menu to display the “mouth” symbol (Figure 4).


At this point, you can extract the system font file from the installation image to recover it. For example, you can first load the Windows 10 installation ISO file into the virtual CD-ROM drive, then use 7-Zip to open the “H:\sources\install.wim\1\Windows\Fonts\” directory (assuming the disk letter of the virtual CD-ROM drive is H: ) and extract the The font files can be extracted to the “C:\Windows\Fonts” directory (Figure 5).


Failure 3: Display failure caused by files using different encoding

The program associated with a file by default can open and display the file normally due to the corresponding fonts and codecs built into the program. However, in daily operation, as each program uses different default encoding, different encoding can easily lead to decoding problems. For example, I used Notepad to open and edit a TXT document in Windows 11, but when I used Notepad to open it again in Windows 10, it showed a bunch of garbled codes (Figure 6).


The reason for this is that when saving with “Notepad” in Windows 11, the program uses the “UTF-8” encoding by default (you can also see the UTF-8 characters displayed at the bottom of Figure 6), and the font encoding is used after saving “UTF-8” (Figure 7).


However, Windows 11’s Notepad program will add a BOM code (special character, not visible) to the header of the TXT file after saving it with “UTF-8” encoding. The Windows 10 Notepad program does not have the ability to adjust the encoding, so it cannot correctly identify the BOM code, which results in garbled code. The solution is to use other programs that can adjust the encoding to open, for example, you can use Word to open the above messy file, in the pop-up text conversion window, select “other encoding → Unicode (UTF-8)”, you can normally display the text (Figure 8).


in Word after the normal opening of the document, press the “Ctrl + A” shortcut to select the text, copy it to the Notepad program and save, set the encoding in the Save window to “ANSI”, so that you can display the text normally.


The Notepad program will remember the last encoding you chose by default. Therefore, if the last encoding you chose in Notepad was “UTF-8”, you must remember to set it to “ANSI” when you save the text next time. If you use “UTF-8” to save a TXT file, when you send it to your friends via QQ, they will often show garbled code when you open it. The solution is to let your friend open it in Word, or save it as “ANSI” encoding and then pass it on.

Leave a Comment