Fixing WinCC TIA Portal HMI Simulator Black Screen in VMs

Problem Description

When launching the WinCC (TIA Portal) HMI runtime simulator, the panel control chrome loads (function key labels, F1–F8 strip, screen-change buttons, and the system menus) but the configured screens, graphics, tags, and trends remain invisible. The runtime process is active and responds to F-key inputs, but the display surface renders as a black, white, or transparent rectangle. This symptom is reported consistently across Siemens Comfort and Basic panels simulated inside virtual machines, including the KTP700 Basic, TP1200 Comfort, TP700 Comfort, and MP 377 panel classes.

The defect is not a fault of the TIA Portal project, the WinCC compile output, or the panel image. It is a host-hypervisor-guest graphics pipeline failure that prevents the HMI surface from being composited into the VM framebuffer. The same TIA project, when copied to a physical host running Windows 7 SP1 x64 or Windows 10 x64, renders correctly without code or panel image changes.

Affected Software Matrix

The bulk of field reports concentrate on TIA Portal V13 SP1 Update 7 with the matching WinCC Advanced Update 7 build. This build shipped a new Direct3D 9/11 rendering path for the panel simulator that depends on hardware-accelerated vertex and pixel pipelines. The native TIA RT was already OpenGL/D3D-driven since V12, but the V13 SP1 update tightened the OpenGL profile requirements, which exposes weaknesses in virtual graphics drivers.

Affected Hypervisor Configurations

Root Cause Analysis

WinCC (TIA Portal) uses a hardware-accelerated rendering surface for the HMI simulator. The composition path is:

1. HMIRtm allocates a Direct3D 9Ex/11 device backed by the system's primary GPU.
2. WinCC draws screen primitives (vector graphics, bitmaps, trend buffers, alarm views) into an offscreen surface.
3. The surface is blitted to the panel window's HWND via IDirect3DSwapChain9::Present or IDXGISwapChain::Present.
4. The Windows window manager composites the HWND into the desktop framebuffer.

Inside a virtual machine, the primary GPU is virtual. Three failure modes are common:

1. Software-only virtual display adapter – The guest is presented with a basic Microsoft Basic Display Adapter (MSBDD) or an XPDM mirror driver that has no 3D pipeline. D3DERR_NOTAVAILABLE is returned at swap-chain creation, and WinCC silently fails to the GDI fallback. F-key chrome still draws because it is owner-drawn GDI; the screen canvas does not.
2. Stalled or blacklisted WDDM driver – The guest sees a WDDM 1.1/1.2/1.3 driver (VMware SVGA 3D, VirtualBox Graphics Adapter), but the driver has been put on the Windows display driver block list or has not been updated to a build that exposes the required feature levels (9_3, 10_0, 11_0).
3. Disabled 3D acceleration in the VM configuration – The hypervisor is configured to expose a non-accelerated framebuffer. The guest cannot negotiate a hardware device, so the simulator falls back to a non-rendering state.

All three modes produce the same visual symptom: chrome visible, screens black. The fix is to ensure the guest advertises and uses a working WDDM 3D driver, and that the hypervisor is configured to provide it.

Step-by-Step Solution for VMware Workstation / Player

Prerequisites

• VMware Workstation 12.x or later, or VMware Workstation Player 12.x or later.
• Guest OS: Windows 7 SP1 x64, Windows 10 x64, or Windows 11 x64.
• Host GPU with hardware OpenGL 3.2 / Direct3D 10 support (Intel HD Graphics 2000 or later, NVIDIA, AMD).
• VMware Tools installed at the current build matching the hypervisor version.

Procedure

1. Power off the virtual machine. Do not suspend; power off cleanly so the .vmx file is not locked.
2. Open the VM settings: VM > Settings > Hardware > Display.
3. Set 3D graphics to Accelerate 3D graphics (checked). The Graphics memory field should be raised to at least 1 GB; 2 GB is recommended for TP1200 and larger panels. Do not exceed the maximum recommended for your VMware build.
4. Open the .vmx file in a text editor and verify/add the following keys:

   mks.enable3d = "TRUE"
   svga.vramSize = "268435456"
   svga.enable3D = "TRUE"
   vmmouse.present = "FALSE"
   hint3DConfig = "TRUE"
   

5. Boot the VM. Open Device Manager > Display adapters. The adapter should read VMware SVGA 3D (not VMware SVGA II and not Microsoft Basic Display Adapter). Right-click > Properties > Driver tab: Driver Provider VMware, Inc., Driver Version matching the latest VMware Tools build.
6. If the adapter shows Microsoft Basic Display Adapter, VMware Tools did not install the display component. Repair the install: Control Panel > Programs > VMware Tools > Change > Repair, or reinstall VMware Tools to match the hypervisor version exactly.
7. Open dxdiag (Win+R > dxdiag). On the Display tab, Direct3D Acceleration must show Enabled. DirectDraw Acceleration must show Enabled. AGP Texture Acceleration must show Enabled. If any show Disabled, click Enable next to that line.
8. Launch TIA Portal, open the project, compile the HMI, and start the runtime simulator. The configured screens should now render.

Step-by-Step Solution for Oracle VM VirtualBox

Prerequisites

• Oracle VM VirtualBox 5.1.x or later (5.2 / 6.0 / 6.1 / 7.0 supported).
• Guest additions ISO matching the VirtualBox version.
• Host GPU with hardware OpenGL 3.0 or Direct3D 9 minimum.

Procedure

1. Power off the VM.
2. Open Settings > Display > Screen. Set Video Memory to at least 128 MB. Tick Enable 3D Acceleration.
3. Set Graphics Controller to VBoxSVGA (recommended for Windows 7+), not VMSVGA or VBoxVGA. VBoxVGA has no 3D pipeline and will not render the screen content.
4. Boot the VM. Insert the Guest Additions CD image (Devices > Insert Guest Additions CD image) and run VBoxWindowsAdditions.exe with the Direct3D Support (Experimental) option enabled. Reboot.
5. Confirm in Device Manager that the adapter reads VirtualBox Graphics Adapter (WDDM) with a current driver date.
6. Open dxdiag and verify Direct3D Acceleration is Enabled.
7. Run VBoxDrvCfg.exe (if present) to confirm the 3D driver is loaded. Restart the guest if the driver was just installed; the runtime will not pick it up until the desktop session is fresh.
8. Launch the WinCC simulator.

Verifying the Graphics Driver State

Open Device Manager and expand Display adapters. The single entry must be the hypervisor's WDDM 3D adapter. Multiple entries, an Microsoft Basic Display Adapter override, or a yellow warning triangle all indicate a broken graphics chain.

Open dxdiag (Start > Run > dxdiag > Display tab) and confirm:

Run DxDiag /64bit on a 64-bit guest if the panel image is a 64-bit HMI runtime. Inspect Notes and Warnings at the bottom of the Display tab; any line beginning with Problem blocks hardware acceleration.

Host GPU and Driver Considerations

The host GPU and its driver feed the virtual adapter. If the host is using a stale or basic driver, the virtual adapter inherits the same limitations. Field data shows that Intel HD Graphics integrated into Core i5-560M (Arrandale) and similar first-generation Intel HD parts can run the VM, but the host driver must be at least Intel 15.36.x or later and provide OpenGL 3.2. NVIDIA Kepler and later, and AMD GCN and later, are reliable choices.

Confirm host readiness:

• Host dxdiag shows a real adapter (not Microsoft Basic Display Adapter).
• OpenGL renderer string from GPU-Z or OpenGL Extensions Viewer reports a hardware renderer, not a software fallback.
• Host driver is not on the Windows display driver block list (Windows 10/11 upgrades may downgrade the host driver to the Microsoft Basic Display Adapter; reinstall the OEM driver).

Windows 7 Specific Notes

Windows 7 SP1 x64 is the most frequently reported guest OS for this failure because it ships the WDDM 1.1 driver model. WinCC V13 SP1 Update 7 expects a WDDM 1.2 minimum. Practical fixes:

• Install KB2670838 (Platform Update for Windows 7) to enable WDDM 1.2 in the user-mode driver.
• Apply the latest VMware Tools (10.x or later for VMware 12.5.x). Tools 9.x predates the required WDDM 1.2 path and is not sufficient.
• Disable Aero theme (right-click Desktop > Personalize > Basic theme). Aero adds a DWM composition layer that interacts badly with broken 3D paths; the WinCC simulator is GDI on top, not DWM, so Aero can be disabled without loss.
• Verify HKLM\SOFTWARE\Microsoft\Direct3D\MaximumTextureBlendStages is not capped below 8 (default 16 is fine).

Advanced Diagnostics

Direct3D Test Inside the Guest

1. Download the DirectX End-User Runtime Web Installer and accept the EULA to ensure D3DX9_43.dll is present.
2. Run the in-box dxdiag tool. On the Render tab of DirectX Features, observe the feature levels reported. 9_3, 10_0, 10_1, 11_0 are required for the panel simulator.

Process Monitor Trace

Use Sysinternals Process Monitor to capture the boot of HMIRtm. Filter on Process Name is HMIRtm.exe. The simulator will read d3d9.dll, d3d11.dll, dxgi.dll, and the hypervisor's display driver DLL. A NAME NOT FOUND or ACCESS DENIED on the hypervisor display DLL confirms the WDDM path is broken.

Event Log Inspection

Check Applications and Services Logs > Microsoft > Windows > DisplayAdapters for events with Event ID 4101 (display driver stopped responding and recovered). If present, the hypervisor GPU is dropping frames; lower the VM's allocated graphics memory or disable 3D in the host, then re-enable.

Test Pattern with a Sample Project

Create a new TIA Portal project, add a Comfort panel (for example TP900), insert a default screen, drag one rectangle and one text field, compile, and start the RT. This isolates the symptom from a corrupt project file or a malformed panel image.

Fallback Solutions

If 3D acceleration cannot be enabled in the host environment (locked-down corporate image, remote desktop without GPU, Hyper-V Gen 2 without RemoteFX), use the following fallbacks:

1. Run TIA Portal on the host directly, not in the VM. This is the canonical engineering recommendation. The WinCC simulator is a 32-bit/64-bit native Windows application; no VM is required to develop or test it.
2. Use a Windows native or ProxMox KVM GPU passthrough with VT-d/IOMMU. Pass a discrete GPU to the guest; install matching host and guest drivers; configure the VM with QXL or VirtIO-GPU as the boot display and the passed-through GPU as the simulation target. This is a heavy setup but solves the WDDM limitation completely.
3. RemoteApp / RDP to a physical workstation with a real GPU. RDP supports Direct3D redirection from Windows Server 2012 R2 onward and can carry the WinCC surface to a remote client.
4. Use the WinCC Runtime Advanced web option (Sm@rtServer / WebUX) to publish the runtime to a browser, bypassing the local GDI surface entirely. Requires a real panel image that supports WebUX.

Verification Checklist

Troubleshooting Matrix

Preventive Configuration

For engineering teams that must run WinCC inside a VM, the following baseline configuration eliminates the issue in 95% of field cases:

• VMware Workstation 15.5.x or later (or Workstation Pro 17.x).
• VMware Tools build matched to the hypervisor, installed with the Complete option.
• VM video RAM: 2 GB.
• 3D Acceleration: enabled.
• Guest OS: Windows 10 22H2 x64 with current cumulative updates, or Windows 7 SP1 x64 with KB2670838.
• TIA Portal: V16 Update 7 or later, or V17/V18 with matching WinCC updates.

For teams on VirtualBox, use the same baseline with the current VirtualBox release (7.0.x or later) and the matching Guest Additions ISO. Avoid VBoxVGA; always use VBoxSVGA for Windows 7 and later guests running WinCC.

FAQ