IMDTouchKnowledge BaseShop main store

Troubleshooting

Why your HMI software reports a missing installed font

HMI and touchscreens Published 5 min read

Short answer

A missing-font warning for an installed font means Windows registered it for your user account only, while the editor reads only the system folder C:\Windows\Fonts. Install the font and its bold face with the Install for all users action, reopen the project, and rerun the editor's Check missing font command until it lists nothing.

On this page
  1. Where Windows puts a font, and where the editor looks
  2. Why the restart changes nothing
  3. Read the missing-font list before you fix anything
  4. Working the case: NB software V1.531, Gautami and its bold face
  5. Install the font for all users
  6. Clear to transfer
  7. Questions asked

A missing-font warning for a font that is already installed almost always means one thing: Windows registered the font for your user account, and the editor reads only the machine-wide folder. The NB HMI editor looks in C:\Windows\Fonts. The ordinary Install action on a font file registers it under your profile instead, so the editor cannot see it even though every other Windows program lists it, and restarting changes nothing. The fix is the documented Install for all users action, which places the font in the system folder. Then reopen the project and rerun Tools → Check missing font until the list is empty, and transfer the project only once it is.

Where Windows puts a font, and where the editor looks #

Windows documents two install actions on a font file: Install, which registers the face for the account doing the installing, and Install for all users, which registers it machine-wide. The two actions write to different places. Install stores the font under your profile, in the per-user folder at AppData\Local\Microsoft\Windows\Fonts; Install for all users copies it into C:\Windows\Fonts, the folder every account shares.

The NB editor reads only the system folder. That one fact explains the whole symptom: another application on the same laptop can show Gautami in its font picker while the editor calls it missing, because the two programs read different locations. Reinstalling the same file with the same default action lands it in the same per-user folder, so the warning survives every reinstall.

This is a font-registration fault on the engineering PC, not a project fault. Tag addresses, communication driver settings and screen logic cannot move a font between folders, so leave them alone while you trace this.

Why the restart changes nothing #

A restart makes the editor rebuild its font list, and that is all it does. It cannot move a registration from your profile into the system folder, so a per-user font stays invisible across any number of reboots. The reported case, an NB project on a Windows 10 laptop, did exactly this: both faces installed, laptop restarted, editor reopened, warning unchanged. Restart once after the all-users installation so the editor rebuilds its list from the system folder; restarting before that only repeats the same read.

Read the missing-font list before you fix anything #

The Tools menu carries Check missing font, and its output is the specification for the repair. Run it on the project before changing anything, then:

  1. Record every family and style it lists, in the exact spelling it prints.
  2. Open the text objects behind those entries and note where each font is used: labels, alarm banners, numeric displays, multilingual screens.
  3. Separate a missing family from a missing style. The reported project wanted Gautami and, as its own entry, the bold form; a regular face in the system folder does not satisfy a bold entry.
  4. Check each listed face against C:\Windows\Fonts itself. Its presence in another program's font picker proves nothing about that folder.
  5. Save a copy of the project before you edit any font selection, so a typography change stays reversible.

Working the case: NB software V1.531, Gautami and its bold face #

Inputs, all from the reported case:

  • Editor and PC: NB HMI software V1.531 on a Windows 10 engineering laptop.
  • Faces the project requires: 2, Gautami regular and Gautami bold.
  • Faces installed before the fix: 2, both through the ordinary Install action.
  • Entries still reported missing after that install and a restart: 2.
  • Restarts performed before the fix: 1.

Rule: an editor that reads only C:\Windows\Fonts finds a face if and only if that face is registered in C:\Windows\Fonts. A per-user registration is invisible to it, and a restart re-reads the folders without moving a file between them.

Arithmetic: faces still missing = faces required − faces visible to the editor = 2 − 0 = 2. Installing both faces for all users moves both into the folder the editor reads, so the same subtraction gives 2 − 2 = 0.

Result: the check reports 0 entries once both faces sit in C:\Windows\Fonts.

Decision: transfer only at 0 entries. Each remaining entry is a face the project still lacks on the engineering PC, so one entry left means install that face for all users and rerun the check before building, not transfer with a known gap.

Install the font for all users #

  1. Obtain the font from your organization's approved software library or the font's authorized distributor, matched to the family and style names on the recorded list. Check the license covers installation on your engineering machines before you copy the file anywhere.
  2. Close the editor so it rebuilds its font list at the next start.
  3. Right-click the font file in File Explorer and choose Install for all users. The plain Install entry on the same menu registers the face for your account only, which is the fault being repaired, so the entry you pick matters. Windows asks for administrator approval because the system folder is protected; an account without those rights needs an administrator to run this step.
  4. Install every listed style the same way. The bold face is a separate file.
  5. Confirm each face in C:\Windows\Fonts itself.
  6. Reopen the project and rerun Tools → Check missing font, then compare the output with the list you recorded.

Let Windows perform the installation rather than dragging files into protected folders by hand; the install action copies and registers the face together, and the registration is what the editor's enumeration reads.

Clear to transfer #

An empty missing-font list is the first acceptance check, not the last one. A face newly registered in the system folder can change character widths and line breaks inside fixed-size objects, so walk the affected screens in the editor: bold labels, alarm banners, multiline text and the language-specific characters that called for this font, watching for clipped characters or wrapping that no longer fits its object.

If this update is preparation for replacing the panel, capture what is running on it before you transfer anything; reading an old HMI program before panel replacement covers that backup.

Build and transfer through the normal workflow. If the editor is clean but the panel is detected and the download still fails, the fault has moved to the transfer path, and why an HMI is detected but the project download fails takes that case apart. Any other workstation that maintains the project needs the same all-users installation, because a project backup carries screen definitions, not fonts.

Questions asked

Can I copy the font file into C:\Windows\Fonts myself?

Use the documented action instead. Install for all users on the font file's right-click menu copies the file and registers it in one step, and that registration is what the editor's font enumeration reads. A file dragged into the folder by hand can skip the registration step, leaving a face that sits in the right folder yet still does not show up. The install action is also what keeps the installation properly licensed and reversible.

Does Install for all users need administrator rights?

Yes. The all-users action writes into the system font folder, which Windows protects, so it requests administrator approval. The per-user Install action needs no approval, which is exactly why it becomes the habit on locked-down engineering laptops and why this fault keeps coming back. If your account cannot approve the elevation, an administrator performs the installation once per workstation, and every account on that machine keeps the font afterwards.

The check still lists one entry after an all-users install, what now?

Read the exact remaining entry before reinstalling anything. In most cases it is a style rather than a family: the bold face is a separate file from the regular face, and installing only the regular file leaves the bold entry standing. Match the entry by the family and style names it prints, install exactly that face for all users, and rerun the check until it reports nothing.

Does Check missing font upload fonts to the panel?

No. The command audits the project's text formatting against the fonts registered in Windows on the engineering PC and lists the families and styles it cannot find; it transfers nothing and has no upload function. The repair happens in Windows, not in the project file, which is why a correct project combined with a per-user font still warns until the font is installed for all users.

Keep reading

  • Troubleshooting

    When an HMI Model Is Missing From the Programming Software

    The model-selection list in HMI programming software contains only the panels whose definitions are installed on that workstation, so a missing model means missing model support. Run the editor's model-support setup utility from its own installation directory, or get the software upgrade from the vendor, and never substitute the nearest similar model number.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Project That Fails After a Git Clone

    The clone is broken because a referenced bitmap .PLK was never committed, not because of an ignore rule. Read the HMI Output tab for the exact filename, prove the file is untracked with git check-ignore followed by git ls-files, then restore and commit it and re-test from a clean clone. Track the .tgt and .def files for the HMI BIOS version as well.

    HMI and touchscreens

  • Troubleshooting

    Fixing TwinCAT HMI publish failures after a NuGet update

    The publish task fails with every symbol unresolved because TF2000, TE2000 and the HMI NuGet packages are at mixed versions after a partial TcPkg upgrade. Update all three groups together on the engineering PC and the IPC, redeploy an empty project to prove the path, then republish: the failure sits in the environment, not the project.

    HMI and touchscreens