IMDTouchKnowledge BaseShop main store

Troubleshooting

Why FactoryTalk View Studio Pop-Ups Render Clipped on Windows 11

HMI and touchscreens Published 6 min read

Short answer

Clipped, non-resizable object-editing pop-ups in FactoryTalk View Studio on Windows 11 come from three missing Windows fonts: Courier Regular, MS Sans Serif Regular and MS Serif Regular. Windows 10 shipped them and Windows 11 omits them. Install all three from an approved source and reopen View Studio; DPI overrides and a version rollback do not fix this.

On this page
  1. What the fault looks like
  2. What you can skip, and why
  3. Why an absent font clips a dialog
  4. Check the three fonts and install what is missing
  5. Worked example: the clipped add-button pop-up on Windows 11 with View Studio v14
  6. If the pop-up still clips with all three fonts present
  7. Questions asked

The pop-up that shows clipped options and refuses to resize when you add or edit an object in FactoryTalk View Studio on Windows 11 is a Windows font problem, not a project, DPI or version problem. Windows 11 does not include three legacy fonts that the editing dialogs request — Courier Regular, MS Sans Serif Regular and MS Serif Regular — so Windows substitutes a different face and the fixed-size controls clip. In the case that documented the fix, a restart, ME-versus-SE configurations, a high-DPI override on the executable and a revert from version 14 to version 13 all changed nothing; installing the three fonts corrected every dialog. Check the font names before you touch anything else.

What the fault looks like #

The defect follows specific editing pop-ups, not the whole application. In the documented case the dialogs for adding a button and for changing settings during normal operation drew their options clipped, and the windows could not be enlarged to reveal them. Most of the software stayed usable, which is why the fault is easy to misread as a version or configuration bug.

Read the pattern this way:

  • The clipping follows particular pop-ups while the rest of the screens render normally — look at how Windows draws those specific dialogs.
  • The same dialogs clipped in ME and in SE network-distributed and SE local-station projects — the project mode is not the differentiator.
  • One exit and restart of View Studio left the dialogs unchanged — this is not transient application state.
  • The same projects rendered correctly in earlier View Studio versions on Windows 10 and Windows 7 machines — the fault tracks the Windows build, not the project.

What you can skip, and why #

Each of these was tried on this fault and failed, so treat them as ruled out until the font check passes:

  • Switching between ME and SE network distributed and SE local station made no difference to the dialogs.
  • Exiting and restarting View Studio made no difference.
  • A high-DPI compatibility override on the executable made no difference. View Studio also runs as many separate executables, so one override covers only one set of dialogs.
  • Reverting from version 14 to version 13 left the same pop-ups clipped.

The decision that falls out of those results: on Windows 11, when the clipped windows are object-editing pop-ups, go to the font check first. Every fix above costs an hour or more; the font check costs minutes.

Why an absent font clips a dialog #

Windows draws dialog labels and controls with fonts it resolves by name. When a requested name is not installed, Windows substitutes another face; the substitute's different character widths and spacing overflow the fixed-size controls, so text clips and the pop-up cannot be resized to compensate. The three names involved are legacy faces that shipped with Windows 10 and are not present in a default Windows 11 installation, which is why the same project looked correct on a Windows 10 machine and clipped on Windows 11. Microsoft documents how to restore fonts that go missing after a Windows upgrade in its Windows deployment guidance; the mechanism here is the same, except the fonts were never installed rather than lost.

This is a Windows font-resource fault on the workstation, not the project-level warning described in why your HMI software reports a missing installed font — there the project asks for a typeface it cannot find for its text objects, while here Windows itself lacks the faces the editor requests.

Match the names exactly. A similarly named face does not answer a request for the missing name, so installing a look-alike changes nothing.

Check the three fonts and install what is missing #

  1. Close FactoryTalk View Studio and its editing windows.
  2. Open the installed font list: right-click the Start menu, select Settings, and search the font list.
  3. Search for each exact name — Courier Regular, MS Sans Serif Regular, MS Serif Regular — and note which are absent.
  4. Obtain the missing files from an approved source for your organization, such as its standard Windows image or your administrator. Do not install font files from an unknown party or accept them through an informal file transfer.
  5. Install them into the Windows Fonts folder with your organization's procedure. If Windows asks for elevated rights, have the administrator complete the install rather than working around the prompt.
  6. Reopen View Studio and repeat the exact operation that failed: add a button, then open the settings pop-ups that clipped.

Verify with the same project and the same dialogs. Confirm the labels and choices are fully visible and that the controls respond, then close and reopen View Studio once and repeat, so the correction is confirmed across an application restart. A dialog that looks right but ignores clicks is not fixed.

Worked example: the clipped add-button pop-up on Windows 11 with View Studio v14 #

Inputs, each from the documented case:

  • Workstation: Windows 11 with its default font set.
  • Engineering tool: FactoryTalk View Studio v14; version 13 was tested and clipped the same way.
  • Failing operation: the dialog for adding a button, plus settings pop-ups during normal operation — options clipped, windows not resizable.
  • Font check: Courier Regular absent, MS Sans Serif Regular absent, MS Serif Regular absent.
  • Already tried with no effect: restart, ME and SE configurations, high-DPI override on the executable, revert to version 13.

Rule in words: a dialog that requests one of the three legacy names clips for as long as that name is missing, and the number of fonts to install equals the number of requested names absent from the installed list.

Arithmetic:

  • Names the dialogs request: 3.
  • Names found installed: 0.
  • Fonts to install: 3 − 0 = 3.

Result: with 3 of 3 fonts installed in the Windows Fonts folder and View Studio reopened, the add-button dialog and the settings pop-ups rendered completely; in the documented case the whole editor behaved normally afterward, and the earlier DPI changes could be left alone.

Decision: if even one of the three names is missing, install it — every dialog that requests that name stays broken until it is present. With all three names installed and the same pop-up still clipping, move to the high-DPI branch below.

If the pop-up still clips with all three fonts present #

Only then treat it as a high-DPI layout fault. Right-click the executable you launch, choose Properties, open the Compatibility tab, click "Change High DPI Settings", enable "Override high DPI Behavior" and select "Scaling performed by System". Change one executable at a time, restart View Studio between changes so the dialogs redraw, and restore the previous setting when a change makes no difference. Record the Windows build, the Studio version, the font-check result and the affected dialogs: that record gives support a reproducible fault description that does not point at project mode or an unverified version change.

Questions asked

Does the missing-font fault affect the HMI runtime on the operator panel too?

No. The clipped windows are in the editing software on the PC, which asks Windows for those three faces. The runtime on the terminal renders the project with the fonts stored in the panel, so the machine display is unaffected and the project needs no re-download after the fix.

Why do only some pop-ups clip while the rest of the software looks normal?

Only the dialogs that request the three legacy names break; screens drawn with faces Windows 11 still ships render normally, so most functions keep working. You can confirm the cause by opening the same project on a Windows 10 machine, where the dialogs render correctly because the fonts are present.

Can I copy the fonts from the Windows 10 machine that works?

The three names ship with Windows 10, so a licensed Windows 10 system in your organization carries them. Whether copying is permitted under your licensing is a question for your administrator; the clean route is your standard software image or IT, never an informal file from outside your organization.

Will a newer FactoryTalk View version clear the fault?

Not this fault. The same dialogs clipped on version 14 and on version 13 in the documented case, because the cause sits in the Windows 11 font list, not in the Studio build. Fix the fonts on the workstation first, then pick a Studio version on its own merits.

What if a pop-up still clips after all three fonts are installed?

Re-check that each exact name is installed, because a similarly named face does not count. If all three names are present, apply the high-DPI override to the executable you launch, one at a time, restarting View Studio between changes so the dialogs redraw; restore any setting that changes nothing.

Keep reading

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    HMI and touchscreens

  • How-to

    Decoding SLC N-File ASCII and Bit Arrays in FactoryTalk View ME

    20549 is hex 0x5045, the packed ASCII bytes for P and E — correct data read as an integer because FactoryTalk View ME has no Character Array object. Rebuild the text on a string-capable mapping (on ControlLogix, COP the bytes into a String tag's .DATA and set .LEN), and extract two-bit multistate codes with AND masks 3, 12, 48, 192 shifted right 0, 2, 4, 6.

    HMI and touchscreens

  • How-to

    Making Remote HMI Access Read-Only Over RDP

    RDP forwards keyboard and pointer input, so no setting inside the remote session makes a PanelView read-only. Replace the launch chain: publish a read-only FactoryTalk ViewPoint client, or enforce view-only mode in the VNC server, then verify from the operator account that every visible control leaves the controller untouched.

    HMI and touchscreens