Windows 8.1 Command Prompt can’t show fonts listed in registry editor

Scott Hanselman had a post on exactly that topic Using Consolas as Windows Console Font. Also here.

As well as the list of steps you linked to, This article lists some further restrictions.

To test that things are working, you should be able to do this (I did, in Win7 64-bit):

1. Go to

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont
   

2. Add a string entry 000 with value Courier New

3. Close the CMD windows and open a new one. (If you do not do this, the font appears in the Properties > Fonts list but does not actually work when clicked).

If you use a font that does not meet the criteria, it just won't appear, which is frustrating. Here are the restrictions repeated from the MS support article:

The fonts must meet the following criteria to be available in a command session window:

• The font must be a fixed-pitch font.
• The font cannot be an italic font.
• The font cannot have a negative A or C space.
• If it is a TrueType font, it must be FF_MODERN.
• If it is not a TrueType font, it must be OEM_CHARSET.

Additional criteria for Asian installations:

• If it is not a TrueType font, the face name must be "Terminal."
• If it is an Asian TrueType font, it must also be an Asian character set.

[...]

The name needs to be incremented with 0 for each additional font. The Data entry needs to match the font’s entry in the following registry location:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts

I found that the DejaVu Sans Mono font worked, and that font has a wider range of unicode characters than Consolas, Lucida Console, or Courier New.