Fixing Garbled ActiveX Text Block Errors in WinCC WebNavigator Under Microsoft Edge

Fixing Garbled ActiveX Text Block Errors in WinCC WebNavigator Under Microsoft Edge

A large block of garbled text (beginning with 'AllBackBack tochangeChange OptionsConfiguration...') appears at the top of WinCC WebNavigator screens in Microsoft Edge when Internet Explorer Compatibility Mode is misconfigured or when Windows security zones block the execution of WebNavigator ActiveX controls. This unformatted string is the raw fallback HTML text from the WebNavigator client installation page ('WebNavigator.asp'). Adding the WebNavigator server URL to Microsoft Edge's Trusted Sites zone, enabling unsigned ActiveX scripting, and running the browser in elevated IE mode eliminates the text block and restores the graphic interface.

Table of Contents

• Root Cause of the Unrendered Fallback Text String
• Edge IE Mode Configuration and ActiveX Permissions
• Step-by-Step Resolution Procedure
• Verification
• Limitations and Operational Precautions
• Engineer FAQ
• Technical References
• Related Articles
• Related Tags

Root Cause of the Unrendered Fallback Text String

When corporate IT policies decommission standalone Microsoft Internet Explorer and enforce Microsoft Edge, engineers accessing legacy SIMATIC PCS 7 V8.x or WinCC V7.x WebNavigator servers frequently observe an unformatted block of concatenated text at the top of the browser:
AllBackBack tochangeChange OptionsConfigurationContactCustomCustomer SupportDeleteEmptyEnglishExcel SheetFAQFile... This Website needs scripts for running...

This phenomenon occurs because:
1. ActiveX Architecture of WebNavigator: WinCC WebNavigator relies on proprietary ActiveX controls (WebClient.ocx, CCWebNavigator.ocx) to render industrial process graphics and dispatch operator inputs.
2. Failure of Client-Side Installer Script: When the WebNavigator landing page (WebNavigator.asp or default-en.htm) loads, an embedded JavaScript routine detects whether the required ActiveX plugins are installed and registered on the client PC.
3. Fallback Text Leakage: If Microsoft Edge blocks ActiveX instantiation or disables active scripting in its rendering container, the browser cannot execute the detection script. Instead of running the interactive installer, the browser engine strips the underlying HTML tags and dumps the raw, unrendered contents of the multilingual language table onto the screen.

Edge IE Mode Configuration and ActiveX Permissions

Microsoft Edge does not natively support ActiveX. It requires Internet Explorer (IE) Mode, which embeds an Internet Explorer 11 MSHTML engine within the Edge container.

To execute ActiveX plugins within Edge IE Mode, specific Windows Internet Options security flags must be configured:
* The WebNavigator server URL must be placed in the Trusted Sites zone.
* The Internet Options security policy must permit "Download unsigned ActiveX controls" (set to Prompt or Enable).
* "Initialize and script ActiveX controls not marked as safe for scripting" must be enabled.
* "Active scripting" (JavaScript) must be enabled.

Step-by-Step Resolution Procedure

Execute the following configuration workflow on the client workstation:

1. Configure Microsoft Edge for IE Mode:
   * Open Microsoft Edge. Navigate to Settings -> Default browser.
   * Under Internet Explorer compatibility:
   • Set "Allow sites to be reloaded in Internet Explorer mode" to Allow.
   • Under "Internet Explorer mode pages", click Add and enter the exact URL of the WebNavigator server (e.g., http://192.168.1.100/WebNavigator).
2. Configure Windows Internet Options:
   * Open the Windows Run dialog (Win+R), type inetcpl.cpl, and press Enter.
   * Go to the Security tab. Select Trusted Sites and click Sites.
   * Add the WebNavigator URL (uncheck "Require server verification (https:)" if using standard HTTP).
   * With Trusted Sites selected, click Custom level....
   * Configure the following settings:
   • ActiveX controls and plug-ins -> Download signed ActiveX controls: Enable.
   • Download unsigned ActiveX controls: Prompt.
   • Initialize and script ActiveX controls not marked as safe for scripting: Enable.
   • Run ActiveX controls and plug-ins: Enable.
   • Scripting -> Active scripting: Enable.
   • Click OK and apply the settings.
3. Install the WebNavigator Client Plugin Manually:
   * If automated ActiveX download remains restricted, install the plugin manually.
   * On the WebNavigator server, locate the client setup executable in:
   C:\Program Files (x86)\Siemens\WinCC\WebNavigator\Server\Web\install\setup.exe
   * Copy setup.exe to the client computer, right-click, and select Run as Administrator.

Verification

• Launch Microsoft Edge and navigate to the WebNavigator server address.
• Confirm that the Edge address bar displays the Internet Explorer mode icon (blue 'e' badge).
• Confirm that the garbled text string is completely gone and the prompt to run or install the WinCC WebNavigator client appears.
• Log in with operator credentials. Confirm that plant graphics, dynamic tag updates, and faceplates open normally without text artifacts.

Limitations and Operational Precautions

• Microsoft Edge IE Mode lists configured locally expire after 30 days by default. For permanent corporate deployment, configure an Enterprise Mode Site List (EMIE XML policy) via Group Policy (GPO).
• Lowering ActiveX security restrictions should be confined strictly to the Trusted Sites zone; never apply relaxed ActiveX policies to the general "Internet" zone.
• In newer PCS 7 versions (V9.1 SP2+), consider deploying WinCC WebUX, which uses pure HTML5 and SVG technologies, completely eliminating ActiveX dependencies and browser compatibility friction.

Engineer FAQ

• Can WinCC WebNavigator run on Google Chrome or Mozilla Firefox?
  Legacy WebNavigator relies on ActiveX, which is proprietary to Microsoft. It cannot run on Chrome or Firefox without third-party IE emulation extensions. Modern WinCC WebUX, however, runs on any modern HTML5 browser.
• Why did this issue appear suddenly without any PCS 7 changes?
  Corporate IT policies pushed a Windows update that disabled standalone Internet Explorer, forcing user workstations into Microsoft Edge without configuring the required IE Mode compatibility flags.
• Where does that strange text string come from?
  It is the raw, unparsed string table stored inside WebNavigator.asp used to render multilingual buttons on the client download page.

Technical References

• SIMATIC WinCC V7/V8 WebNavigator Manual: Installation and Security Guidelines.
• Microsoft Documentation: Configure IE Mode Policies and Enterprise Site Lists in Microsoft Edge.
• Siemens Industry Online Support Entry ID 109801081: Operating WinCC WebNavigator with Microsoft Edge.

Related Articles

• Migrating from WinCC WebNavigator to HTML5-Based WinCC WebUX in PCS 7.
• Deploying Enterprise Mode Site Lists (EMIE) for Industrial HMI Web Clients.

Related Tags

WinCC, WebNavigator, PCS 7, Microsoft Edge, ActiveX, IE Mode, Troubleshooting, Cybersecurity