Troubleshooting
How to Recover a WinCC On-Screen Keyboard Placed Off-Screen
Short answer
Set PosLeft, PosTop, PosRight and PosBottom to 0 under the Windows account that runs the HMI, then restart Windows: the keyboard reopens at a sensible default. The values live under HKEY_CURRENT_USER\SOFTWARE\Siemens\SimaticHmiIM on a documented WinCC V17 station, but the subkey varies, so search for PosLeft under HKCU\SOFTWARE\Siemens when the key is not there.
On this page
- Why does the WinCC keyboard end up off the screen or too small to use?
- Which keyboard component is saving the bad position?
- Which registry values hold the keyboard's position?
- How do you reset the keyboard to a usable default?
- Why did the registry startup script fail to write anything?
- Can a WinCC button bring the keyboard back without registry edits?
- How do you stop the keyboard escaping again?
- Questions asked
Set PosLeft, PosTop, PosRight and PosBottom to 0 under the Windows account that runs the HMI, then restart Windows, and the WinCC on-screen keyboard reopens at a sensible default. On the documented WinCC V17 touch station those four DWORD values live in HKEY_CURRENT_USER\SOFTWARE\Siemens\SimaticHmiIM. Importing a .reg file with tested values does the same job without typing, and a maintenance button configured with OpenScreenKeyboard and mode=maximized is worth adding as a touch-reachable fallback. None of it needs the Windows Alt+Space window-move sequence, which a touch-only station cannot run anyway.
Why does the WinCC keyboard end up off the screen or too small to use? #
The keyboard saves its window rectangle when it closes and reuses those edges on the next open, so one fat-fingered drag can park the saved rectangle outside the visible desktop or shrink the window until its keys cannot be hit.
A changed desktop resolution, Windows scaling factor or monitor arrangement does the same thing in reverse: a rectangle that was fine at the old settings lands off screen after the change, with nobody touching the keyboard at all.
On a station with a physical keyboard and mouse, Windows offers the standard rescue: give the window focus, press Alt+Space, choose Move, tap an arrow key and the window snaps to the pointer. A touch-only HMI has none of that input. In the documented attempt, tapping ALT on the virtual keyboard itself halved the keyboard's width instead of opening any move menu, which is one step from causing the very fault being fixed. Decision: on a touch-only station, skip the Alt+Space route and go straight to the saved geometry.
Which keyboard component is saving the bad position? #
On a classic WinCC runtime the keyboard belongs to the HMI input manager and stores its geometry under the Siemens key in the registry; WinCC Unified PC runtime instead uses the Windows on-screen keyboard, and panel devices have their own mechanisms.
Three different things get called the WinCC keyboard:
- Classic WinCC runtime, the documented case: the values sit in
HKEY_CURRENT_USER\SOFTWARE\Siemens\SimaticHmiIM, but the subkey moves between installations. If the key is not there, search underHKEY_CURRENT_USER\SOFTWARE\Siemensfor a value named PosLeft; that finds the live keyboard on that station. - WinCC Unified PC runtime: the keyboard is the Windows one, enabled under Settings, then Ease of Access, then Keyboard, with "Use the On-screen Keyboard". It is a Windows component with its own settings, and none of the Pos values below apply to it. Check where WinCC Unified runtime can run before porting any of this to a Unified station.
- Windows-based operator panels from the WinCC flexible era: keyboard size and position are set from the Control Panel's InputPanel icon — position it, press Save, then Close Input Panel. WinCC flexible on-screen keyboard off-screen fix covers that generation in detail.
Which registry values hold the keyboard's position? #
Four DWORD values — PosLeft, PosTop, PosRight and PosBottom — define the saved window edges, while NumPadWidth and NumPadHeight store the numeric keypad's size separately in the same key.
Here is the layout one working WinCC V17 station had saved, exactly as documented:
| Registry value | Saved value (hex) | Decimal | What it sets |
|---|---|---|---|
| PosLeft | 000000c9 | 201 | Left window edge |
| PosTop | 00000000 | 0 | Top window edge |
| PosRight | 000003c4 | 964 | Right window edge |
| PosBottom | 0000011c | 284 | Bottom window edge |
| NumPadWidth | 0000013c | 316 | Numeric keypad width |
| NumPadHeight | 00000070 | 112 | Numeric keypad height |
Check the rectangle before trusting it, arithmetic shown. Hex to decimal: 0xc9 = 12×16 + 9 = 201; 0x3c4 = 3×256 + 12×16 + 4 = 768 + 192 + 4 = 964; 0x11c = 1×256 + 1×16 + 12 = 284. Window width = PosRight − PosLeft = 964 − 201 = 763 px; window height = PosBottom − PosTop = 284 − 0 = 284 px. Against a 1920 × 1080 desktop that rectangle sits fully inside the display. On the failure side, an illustrative PosLeft of 2000 on the same desktop puts every key past the right edge, and an illustrative PosBottom of 1200 pushes the bottom row out. Decision rule: compare all four edges against the desktop's width and height; any edge past a bound, or a left or top edge already beyond the far bound, means the saved layout cannot open on screen.
These example figures are one station's documented layout, not a recommended geometry. To capture your own, position the keyboard once where operators want it, close it, and read the four values back; that becomes your known-good import file. Regedit displays DWORDs in hexadecimal by default and offers a decimal toggle, so keep the base straight — 0x3c4 and 964 are the same number only when the base matches.
How do you reset the keyboard to a usable default? #
Set all four position DWORDs to 0 under the account the HMI runs on, restart Windows, and the keyboard opens at a sensible default — this exact sequence is the proven fix on a WinCC V17 touch station.
- Identify the Windows account the runtime logs in under. HKCU is that account's hive, and nothing edited under your own login touches it.
- Export the whole key to a
.regfile first, so the original geometry can be restored. - Close the runtime or at least the keyboard, so it cannot rewrite the old values on exit.
- Set PosLeft, PosTop, PosRight and PosBottom each to 0. Leave NumPadWidth and NumPadHeight alone unless you have tested values for them.
- Restart Windows, touch an input field, and confirm the keyboard opens fully inside the display.
The reboot is part of the documented fix, not a superstition: the keyboard reads its geometry when it starts, so a value written while it runs is overwritten when it closes.
One safety note: if a UAC consent prompt blocks the edit, fix the account context rather than disabling UAC — that prompt is the last gate on a PC that also runs your machine logic.
Why did the registry startup script fail to write anything? #
HKCU always belongs to whoever executes the command, so a script launched elevated, from a service, or under an administrator logon writes a different user's hive — and a consent screen a touch-only operator cannot accept means nothing gets written.
The documented failures on the original station were exactly that: shell:startup entries and reg import or regedit /s combinations that either sat behind a UAC prompt the touchscreen could not answer or completed silently against the wrong hive. What worked on the same station was a pair of files: a .reg holding tested values and a batch file importing it, executed in the runtime user's own logon session, where an HKCU write changes nothing machine-wide.
The documented .reg contents, matching the table above:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Siemens\SimaticHmiIM]
"PosLeft"=dword:000000c9
"PosTop"=dword:00000000
"PosRight"=dword:000003c4
"PosBottom"=dword:0000011c
"NumPadWidth"=dword:0000013c
"NumPadHeight"=dword:00000070
Substitute your measured values — or zeros in the four position entries — before importing. Decision: trigger the import at runtime-user logon, unelevated; if station policy still prompts, do the import from an authorized maintenance session instead of weakening the policy.
Can a WinCC button bring the keyboard back without registry edits? #
Possibly: a button configured with the system function OpenScreenKeyboard and mode=maximized is the touch-reachable candidate, but it is a proposal to test, not a proven fix, and it only helps if that function drives the same keyboard instance that opens on input focus.
The original station never configured a keyboard command; the keyboard appears automatically whenever an input field takes focus. The documented lever for that behavior in WinCC RT Professional is the system function SetScreenKeyboardMode, which enables or disables the automatic display of the screen keyboard. OpenScreenKeyboard with mode=maximized was proposed on top of that as a recovery control, because a maximized keyboard cannot also be parked off screen.
Test it in this order:
- Confirm your runtime edition exposes OpenScreenKeyboard with its maximized mode.
- Bind it to a visible maintenance button, not an invisible touch target operators must remember.
- Test with the keyboard closed, then again with an input field active.
- Reproduce the off-screen layout in a controlled window and check the button still yields a full-width keyboard inside the display.
Pass all four and you have a registry-free recovery control. If the button merely reopens the same lost rectangle, the function is not driving that keyboard instance — fall back to the position reset.
How do you stop the keyboard escaping again? #
Import your proven layout at runtime-user logon, run the HMI full screen so the Windows desktop is never exposed to a finger, and keep a physical admin keyboard and mouse for maintenance — that combination closes all three doors.
The per-logon import makes geometry deterministic: even if an operator drags the keyboard away on Tuesday, Wednesday's logon rewrites the known-good rectangle before the runtime starts. Full-screen runtime removes the desktop where the dragging happens, the standard arrangement for touch-only stations precisely because operators then have no Windows chrome to misplace. The physical set covers maintenance, the same sessions you need when you redownload an HMI project after a user lockout. Decide once per station: logon import plus full screen on every touch-only HMI, and a keyboard and mouse in the cabinet for everything else.
Questions asked
Where is the screen keyboard enabled in WinCC V7 and V8?
In WinCC Explorer, select Computer, open the shortcut menu, choose Open, then Local settings and Runtime Options, and set Monitor keyboard. That switch controls whether the runtime keyboard appears at all. It does not retrieve one already dragged off screen, so pair it with the position reset when the keyboard exists but is unreachable.
Does zeroing the values also reset the numeric keypad size?
No. The window position lives in PosLeft, PosTop, PosRight and PosBottom, while the keypad size is stored separately as NumPadWidth and NumPadHeight. The zero-and-reboot sequence is proven for the four position values only; zeroing the two size values is untested, so if the keypad comes back the wrong size, write measured values into them instead of zeros.
Why does the reset work when you test it but not for the operator?
Because HKCU is per account. Logging in as administrator, zeroing the values and rebooting fixes the administrator's keyboard geometry and leaves the runtime account untouched. Do the reset, or run the .reg import, inside the Windows account the HMI actually logs in under, and repeat it for any other account that runs the station.
How do you reposition the keyboard on Unified Basic Panels?
Their runtime screen keyboard has an Undock button in its upper left corner. Press it, then drag the keyboard to the wanted position inside the display boundary. That is the designed repositioning path on those panels, so no registry editing is involved.