Open-source project
Tatsu-syo/noMeiryoUI avatar
Tatsu-syo/noMeiryoUI

No!! MeiryoUI: the Windows shell font and its three blind spots

No!! MeiryoUI is Windows system font setting tool on Windows 8.1/10/11.

6,782 stars191 forksC++MIT

At a glance

What is it?
No!! MeiryoUI is a C++ executable that brings back the Windows shell font setting removed since Windows 8 by editing the registry, in the branch it tells you to back up first. It ships as a release zip with no build step, and it leaves the taskbar, preinstalled UWP apps and the Windows 11 titlebar untouched.
Who is it for?
No!! MeiryoUI does one job: putting a chosen shell font back on Windows 8 through 11 without a system-wide install.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Tatsu-syo/noMeiryoUI6,782 ★ · +75
Star history
Repository2026-09-232026-11-15
Tatsu-syo/noMeiryoUI6.7k6.8k

75 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The shell font control Windows 8.1 took away

Windows used to let you pick the typeface used for shell text, and that setting disappeared with Windows 8. No!! MeiryoUI exists to put it back. It is described as a Windows system font setting tool for 8.1, 10 and 11, and the repository language is C++, so what ships is a native executable rather than a script or something you pull in through a package manager. The stated requirement is Windows 8 or newer, with a note that the tool should work on Windows Vista but is not actively tested for compatibility, so treat 8 as the real floor. The name is a Japanese exclamation, "Meiryo UI mo daikkirai!!", though the interface and help are available in English, Japanese, Korean, Brazilian Portuguese, Simplified Chinese and Traditional Chinese. What the tool changes is which font the shell asks for, so the font you pick has to exist on the machine already, and the documentation says nothing about where it should come from.

The registry branch noMeiryoUI edits, and the backup to take first

The installation section opens with an important note rather than a download link: the tool makes changes to the registry, and backing that up before applying anything is recommended. The note carries a runnable command rather than prose advice, saving the Control Panel branch of the current user hive into a file called reset_font.reg in the folder you are standing in. HKCU is the per-user hive, so that copy covers your own profile rather than machine-wide settings, and the /y flag overwrites an existing reset_font.reg without asking. Keep the file somewhere you will find it again: the README gives the restore command, reg restore "HKCU\Control Panel" .\reset_font.reg, run with administrator privilege, and says the archive also contains utils\SAVEreg.bat and utils\RESTOREreg.bat which do the same. The tool itself has a preset menu to reset fonts to the Windows 8/8.1, 10 and 11 defaults and can save and load font settings to and from a file. Change the font twice and this same branch is what you return to.

bash
reg save "HKCU\Control Panel" .\reset_font.reg /y

Downloading the zip and running noMeiryoUI.exe

There is no build step and no install command. You download a zip archive from the project's Releases page, extract it, and run the executable named noMeiryoUI.exe. That is the documented path for users; the README also has a Building section that opens program\noMeiryoUI.sln in Visual Studio 2022 or later (or the 2012 and 2008 solutions) and builds the Release configuration. Two things follow from that shape. Upgrading means downloading another zip and replacing the file, not installing through a version manager. And there is no documented statement about what happens to a font chosen by an older build, so treat each upgrade as a fresh change to the same registry branch rather than an in-place migration.

text
noMeiryoUI.exe

Where the new font does not reach: taskbar, UWP apps, titlebar

The project is explicit about the gaps, and they are not cosmetic. It does not work with the Windows taskbar, so the bar along the bottom of the screen keeps the font it already had. It does not work with preinstalled UWP apps, with Settings and Paint named as the examples, which is the part that catches people out: the windows they most want restyled are the ones Windows draws itself. Applications that ignore the system font setting are untouched too, and that is true by definition rather than by defect. On top of that, the titlebar font on Windows 11 cannot be modified at all, and the introduction warns that there are further limitations on Windows 11 22H2 without saying what they are. Plan on a separate per-application tool for the windows this one skips.

Antivirus detection is a documented side effect

One of the listed limitations has nothing to do with fonts. The project states that noMeiryoUI might be detected as Trojan or virus software by some antivirus products, and gives the reason: it changes system font settings. That is behaviour-based detection working as designed against a program whose whole purpose is editing system configuration, so on the project's own account the warning is a false positive. The README does not discuss code signing, does not publish checksums for the release archives, and gives no instructions for adding an exclusion. The order of operations matters here. Confirm the zip came from the project's own Releases page, keep the saved registry copy from the earlier section, and only then decide whether your security software needs a narrow exception. A utility that writes to HKCU deserves that sequence.

program/, util/, lang/, help/ and packaging/ in the source tree

The repository root lines up with what the README describes. Its entries are three README translations, a plain ReadMe.txt, CONTRIBUTING.md, the LICENSE file, and five directories: help, lang, packaging, program and util. Only packaging/ obviously points at release artifacts, which lines up with the zip archive the installation step tells you to download. The README fills in the roles: the source code is in program/, the help file sources are in help/, interface translations go in lang/, and release packages (portable zip, installer and language packs) are made with the scripts in packaging/. The fair summary is that this is source with a clear top level and a documented Visual Studio build, while the Releases page remains the simple entry point for anyone who just wants the program.

text
help/
lang/
packaging/
program/
util/

TAG-3.5.0, TAG-3.5.1 and the dated 3.5.2 snapshot

Three releases sit at the top of the release history. TAG-3.5.1 was published on 2026-09-06, TAG-3.5.2_20261004 on 2026-10-04 under the name Version 3.5.2 snapshot 20261004, and TAG-3.5.2_20261018_2 on 2026-10-18 under the name Version 3.5.2 snapshot 20261018. The shape of the two snapshot tags is worth a second look: they carry a build date inside the tag and call themselves snapshots, which the plain TAG-3.5.1 does not. The repository's last push is dated 2026-11-01, after the newest snapshot, so the default branch, master, has moved on since the latest published archive. If you need a build that corresponds to a particular source state, compare the tag against the branch instead of assuming the newest download matches the newest commit. The project is MIT licensed, with the text in the LICENSE file at the root, and that file is the one to read before forking or redistributing the C++ sources.

When a per-app font setting is the better answer

No!! MeiryoUI is the wrong tool in several ordinary situations. Anyone not running Windows gets nothing from it, since it is an executable for a Microsoft shell and the README offers a single entry point with no command line to drive. Anyone who wants one application restyled is asking for more than a tool that cannot reach individual programs ignoring the system font. Anyone whose goal includes the taskbar, the Settings window or the Windows 11 titlebar will finish the run with part of the request untouched. It also does not address how text gets drawn. The project changes which font is requested and says nothing about rendering, hinting or scaling, so anyone chasing sharper text at an awkward resolution is looking at a different problem. What remains for this tool is narrow and clear: the shell font on a Windows desktop, set by editing one branch of your own registry.

Editorial conclusion

No!! MeiryoUI does one job: putting a chosen shell font back on Windows 8 through 11 without a system-wide install. Skip it if you need the taskbar, preinstalled UWP apps or the Windows 11 titlebar restyled, and skip it off Windows entirely. Before running noMeiryoUI.exe, save the HKCU\Control Panel branch with reg save, and settle where the font file comes from, since the documentation does not say.

Frequently asked questions

Is it possible to change the Windows default font with No!! MeiryoUI?

Yes for the shell side of Windows 8.1, 10 and 11, which is the setting the project exists to restore. It states that it does not work with the Windows taskbar, preinstalled UWP apps such as Settings and Paint, or the titlebar font on Windows 11.

Does No!! MeiryoUI work on Windows 11?

It is built for Windows 8 or newer and targets 8.1, 10 and 11. The README notes there are some limitations on Windows 11 22H2 without listing them, and that the titlebar font on Windows 11 cannot be modified.

How do I put the old font back after No!! MeiryoUI changes it?

The README recommends backing up the registry before any change, saving HKCU\Control Panel with reg save into reset_font.reg. To restore it, the README gives reg restore "HKCU\Control Panel" .\reset_font.reg run with administrator privilege, and the archive's utils\RESTOREreg.bat does the same; the tool also has a preset menu to reset fonts to Windows defaults.

Will antivirus software flag noMeiryoUI.exe?

The project says it might be detected as Trojan or virus software by some antivirus products, because it changes system font settings. It does not publish signing details or checksums for the release archives.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. Tatsu-syo/noMeiryoUI on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tatsu-syo-nomeiryoui.svg)](https://hysenlabs.com/projects/tatsu-syo-nomeiryoui)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tatsu-syo-nomeiryoui.svg)](https://hysenlabs.com/projects/tatsu-syo-nomeiryoui)

Was this useful?