IMDTouchKnowledge BaseShop main store

Troubleshooting

EasyBuilder Pro Menus Too Small on a 4K Display: the Fix

HMI and touchscreens Published 6 min read

Short answer

Tiny, clipped or unusable EasyBuilder Pro menus on a 4K monitor are a display-scaling defect in the engineering tool, not in the project or the terminal. Install version 5.03.01, the corrective release for this fault, and verify the menus at the monitor's native 4K resolution and scale. Lowering the resolution only coarsens the desktop and leaves the menus broken.

On this page
  1. What the symptom is — and is not
  2. Why 4K breaks menus that worked at 1080p
  3. The arithmetic on a 27-inch 4K panel
  4. Fixes that miss the fault
  5. Baseline before you change anything
  6. Install version 5.03.01
  7. Verify the fix at native 4K
  8. The decision
  9. Questions asked

EasyBuilder Pro menus that come out tiny, clipped or partly unusable on a 4K monitor are a display-scaling defect in the engineering tool itself. Weintek issued EasyBuilder Pro version 5.03.01 for exactly this complaint: install it, then verify the menus at the monitor's native 4K resolution and scale. Lowering the monitor resolution does not repair the menus — it drops pixel density below the level Windows assumes and only coarsens the desktop. The HMI project and the terminal are not at fault, and nothing on the machine side touches this symptom.

What the symptom is — and is not #

On a 4K display, the engineering tool's main menus and submenus draw with text far too small for the row, labels cut off at the menu border, or commands whose click area does not sit on the visible row.

The fault is repeatable: close and reopen the application at the same resolution and scale, and the same menus misbehave the same way. That repeatability separates a scaling defect from a one-off drawing glitch. When other applications on the same workstation size correctly at the same settings, the monitor, cable and video driver are doing their job; what fails is the way this application computes its interface geometry.

The project is unaffected. The runtime screen on the terminal shows exactly what it did before, because the defect lives in the workstation editor — not in PLC logic, terminal scan time or the communication link.

Why 4K breaks menus that worked at 1080p #

Windows lays application interfaces out in logical units and maps them onto physical pixels at a scale factor. A scaling-aware application applies that one factor consistently to font height, menu-row height, dialog boundaries and pointer hit areas. The 4K menu defect is an application-side scaling fault: text metrics and container dimensions get computed against inconsistent scale information, so a label is drawn at one size inside a row or border sized at another. The results are tiny text, clipped labels and hit areas that fall outside the menu — geometry, not project logic.

The fault hides at lower densities. A 24-inch 1080p monitor sits near 92 PPI, essentially the 96 DPI baseline, so scale errors of this kind stay invisible there and surface on 4K.

The arithmetic on a 27-inch 4K panel #

Take a 27-inch 3840 × 2160 workstation monitor as a worked example; these figures are calculated from panel geometry, not a measured test.

  • Diagonal pixels: √(3840² + 2160²) = √(14,745,600 + 4,665,600) = √19,411,200 ≈ 4406 px
  • Pixel density: 4406 px ÷ 27.0 in ≈ 163 PPI
  • Windows sizes a 100% desktop against a 96 DPI logical baseline, so the required scale is 163 ÷ 96 ≈ 1.70 — which is why such a panel runs at roughly 150–175% in display settings
  • An editor that lays out its menus as if the panel were a 96 DPI display renders them at 96 ÷ 163 ≈ 0.59 of their intended physical size: a menu row meant to read at 20 px of apparent height lands at about 12 px, and any container computed at the other scale clips its label

Lowering the same monitor to 1920 × 1080 puts √(3,686,400 + 1,166,400) = √4,852,800 ≈ 2203 px across the same 27.0 in, about 82 PPI — below the 96 DPI baseline. That is the reported outcome in numbers: the whole desktop renders coarser while the menu fault survives the resolution change.

Fixes that miss the fault #

Attempt What it changes Why it misses
Lower the monitor resolution The desktop pixel grid Density falls below the 96 DPI baseline; the desktop coarsens and the menu fault stays.
Change the project screen size The HMI runtime canvas The broken menus belong to the workstation editor, not the terminal screen.
Resize the application window The available client area It never recalculates the text metrics and container scales that disagree.

Resizing the window is worth one thing only: dragging it large enough to reach a Save or Close command while you arrange the update.

Baseline before you change anything #

  1. Open the workstation's display settings and write down the active resolution and scale for the 4K monitor — for example 3840 × 2160 at 150%.
  2. Read the installed EasyBuilder Pro version from the application's version information; if the menus block access, read the version Windows records for the installed program.
  3. Open every main menu and one submenu. Note which labels are too small, clipped or drawn outside the border, and click one command per menu to record any hit-area offset.
  4. Close and reopen the application without touching display settings. A repeatable symptom confirms the scaling defect; a one-time glitch does not.
  5. Save a backup copy of the HMI project. This is the one precaution that matters here: an update that goes wrong must not cost project work.

Install version 5.03.01 #

  1. Download the EasyBuilder Pro 5.03.01 package from Weintek's official download area — the download section of the applicable terminal product page carries it. Choose the file that identifies version 5.03.01 explicitly; a file without visible version identification is not verification.
  2. Exit EasyBuilder Pro so none of its executable files are in use.
  3. Run the installer through the workstation's normal authorized software process.
  4. Start the application and read the version again. It must report 5.03.01 — a stale shortcut, parallel copy or incomplete update can still launch the old executable and make the defect look unchanged.

Before installing, confirm the engineering software version still matches the HMI models and firmware you support; that check is covered in checking HMI engineering software before a panel replacement.

Verify the fix at native 4K #

  1. Restore the recorded resolution and scale if anything changed while troubleshooting; the test only counts at native 4K.
  2. Open the same project and window arrangement used for the baseline.
  3. Walk every menu that was abnormal, plus at least one submenu: each label fully visible, nothing cut off at the top, bottom or side.
  4. Click a representative command in each. The highlighted row and the action taken must match — larger text alone is not a pass while the hit area is offset.
  5. Close and restart the application, then repeat the menu check once; this catches a correction that holds only for the first drawing cycle.

If the menus work only with the resolution lowered, the 4K condition has not been tested: restore native settings and repeat. If you later move the project to the V6 software generation, a separate HMI no-response fault that appears after that upgrade is covered in the EasyBuilder Pro V5 to V6 upgrade showing HMI no response.

The decision #

  • Menus tiny, clipped or mis-hitting at native 4K on a version older than 5.03.01 → install 5.03.01 and run the verification above. That is the documented correction for this defect.
  • Text readable after the update but clicks landing on the wrong row → not a pass. Restart and retest; if the offset survives, the executable running is not the one you updated — read its version again.
  • Verified 5.03.01 with the fault still present → confirm the display scale is a standard step such as 150% or 175% rather than a custom value, confirm the reported version, and take those readings to Weintek support.
  • Tempted to lower the resolution instead → do not. You trade desktop sharpness for nothing and the menus stay broken.

Questions asked

Does lowering the monitor resolution fix the small menus?

No. On a 27-inch 4K panel, dropping to 1920 × 1080 takes the density from about 163 PPI to about 82 PPI, below the 96 DPI baseline Windows assumes at 100%. The whole desktop renders coarser and the menu fault survives. The documented correction is the software update, verified at native 4K.

Is the fault in my HMI project?

No. The defect is in the engineering tool's interface geometry on the workstation. The project's configured screen size governs only what the terminal shows at runtime; changing it cannot enlarge an editor menu and can disturb object placement on your screens.

How do I confirm which version is installed?

Read the version from the application's About or version information. If the menus block access to that dialog, read the version Windows records for the installed program — and do not rely on the project file's properties, which describe the project, not the editor executable that opened it. After the update the application itself must report 5.03.01 — a stale shortcut can still launch an older executable.

Will the update change what runs on my HMI terminals?

No. The update replaces the workstation editor; the runtime project already loaded on a terminal keeps running. Before installing, confirm the engineering software version still matches the HMI models and firmware you support, and keep a project backup so a failed update costs no work.

The menus look fine at 1080p. Is the problem solved?

No. The defect appears at native 4K scale, so verification only counts there. Restore the recorded 4K resolution and scale, reopen the affected menus and submenus, and click one command per menu to confirm the hit areas before you call it corrected.

Keep reading

  • Troubleshooting

    HMI Text Runs Off the Screen After Downloading the Project

    The panel and the project are both fine: the engineering PC's Windows display scaling is above 100%, so the downloaded layout lands past the panel edge even though the editor and offline simulation look correct. Set the scale to 100%, restart the PC, then redownload.

    HMI and touchscreens

  • How-to

    How to Fix Overlapping Graphics Hiding HMI Symbols

    Put the static background picture inside a frame container so it sits behind the process symbols, bring each symbol forward through the editor's object list, and leave the generated source alone. Assign z-values ten apart by role so new layers insert without renumbering. Stacking fixes visibility only; click handling and state-driven colors need their own runtime checks.

    HMI and touchscreens

  • How-to

    Launching Windows programs from a Vijeo Designer runtime

    No. A Vijeo Designer runtime screen cannot start a Windows program: the object action lists contain no run-program entry, and the only application-level control is the exit-runtime key. Configure third-party tools from the Windows desktop after exiting, or reach them through a remote session while the runtime keeps running.

    HMI and touchscreens