How to Remove Unrendered ActiveX Text Banners in WinCC WebNavigator Clients

To remove the persistent block of unrendered installation text covering the top of WinCC WebNavigator HMI screens, install the Siemens WinCC WebNavigator Client component locally on the client PC using administrative privileges. When the client machine lacks the pre-installed ActiveX components or when browser security suppresses ActiveX registration, the web server's welcome banner fails to collapse. Running 'WebNavigatorClient.exe' directly from the server's installation directory registers the necessary COM objects, collapsing the banner and displaying the HMI.

Mechanism of the WebNavigator ActiveX Banner Display

In SIMATIC PCS 7 and WinCC WebNavigator architectures, the client-server handshake begins when a remote user opens the web portal hosted by Microsoft Internet Information Services (IIS).

The welcome page (WebNavigator.asp) contains an embedded ActiveX initialization check:
* When the ActiveX plugin (WebClient.ocx) is correctly installed and registered, the browser instantiates the control.
* The script detects successful initialization, collapses the download banner, and launches the full-screen WinCC Graphics Runtime view.
* However, if the control fails to instantiate, the browser displays the static fallback header banner containing installation links, language definitions, and system requirements text across the top half of the screen.

Why Automatic Web Installation Fails on Modern Operating Systems

In historical Windows XP environments, Internet Explorer automatically downloaded and installed cabinet files (*.cab) from the web server. On modern Windows 10 and Windows 11 enterprise endpoints, multiple security layers prevent this automated process:
1. User Account Control (UAC): Modern Windows operating systems silently block background ActiveX registration because writing to C:\Program Files (x86)\Siemens\WinCC\WebNavigator\Client and the HKEY_CLASSES_ROOT registry hive requires administrative elevation.
2. Missing Code Signing Roots: If the client PC does not trust the self-signed certificate generated by the WinCC IIS server, Windows blocks execution with an untrusted publisher error.
3. Cross-Site Scripting (XSS) and SmartScreen Filters: Windows Defender SmartScreen intercepts the cabinet payload, treating the dynamic download as untrusted.

Step-by-Step Procedure for Manual Client Component Installation

To completely eliminate the fallback banner and enable seamless runtime display without relying on web browser auto-installers:

Retrieve the Standalone Installer Package:
* On the WinCC WebNavigator Server, navigate to the public web distribution directory:
C:\Program Files (x86)\Siemens\WinCC\WebNavigator\Server\Web\install\
* Copy the folder or the standalone installation file setup.exe (or WebNavigatorClient.exe) to a USB flash drive or local directory on the client PC.
Execute Administrative Setup on the Client Station:
* On the client machine, close all instances of Microsoft Edge, Internet Explorer, and other browsers.
* Right-click setup.exe and select Run as Administrator.
* Follow the installation wizard. Select the complete client installation, which registers WebClient.ocx, CCWebNavigator.ocx, and all standard WinCC graphic controls.
Register COM Components:
* Open Windows Command Prompt as Administrator and verify registration:
regsvr32 "C:\Program Files (x86)\Siemens\WinCC\WebNavigator\Client\bin\WebClient.ocx"
* Ensure a dialog appears reporting DllRegisterServer in WebClient.ocx succeeded.
Launch WebNavigator in Configured Browser:
* Reopen the browser in IE Mode. The browser immediately loads the local, pre-registered ActiveX engine, bypassing the download script entirely.

Verification

Launch the browser and connect to the WebNavigator address.
Verify that the top of the screen is clear of any installation text blocks, language tables, or unrendered code.
Confirm that the WinCC user login dialog appears centered on the screen, followed by immediate loading of the primary plant overview graphic (@Overview1.pdl).

Limitations and Operational Precautions

Client setup packages must strictly match the service pack and update version installed on the WebNavigator Server. If the server is updated with an Update Collection (e.g., UC05), the client software on all remote machines must be reinstalled.
User accounts operating the client computer do not require local administrator rights during daily operation; administrative elevation is required only during initial installation and COM registration.

Engineer FAQ

Can I deploy the WebNavigator Client silently across multiple PCs?
Yes. The installer supports silent deployment via command line: setup.exe /silent or via enterprise IT software distribution tools (such as Microsoft SCCM / Intune).
Does clearing the browser cache remove the text block?
No. Clearing the browser cache will not resolve the issue because the problem is caused by the absence of registered ActiveX COM controls, not cached temporary files.
Why did the issue happen across all workstations simultaneously?
A corporate IT policy update likely removed administrative rights or enforced new browser restrictions that invalidated the dynamic registration of unsigned browser extensions.

Technical References

SIMATIC WinCC V7/V8 WebNavigator Operating Instructions (A5E41356372-AA).
Siemens Industry Online Support Entry ID 109801081: Standalone Installation of WebNavigator Clients.
Microsoft Windows IT Pro Center: Managing ActiveX Controls in Modern Enterprise Environments.