A Basic Application Could Not Be Started Wincc 75 | DELUXE › |

The error message "A basic application could not be started" in WinCC 7.5 typically indicates a problem that prevents the WinCC application from launching properly. WinCC (Windows Control Center) is a supervisory control and data acquisition (SCADA) system from Siemens used for monitoring and controlling industrial processes. When encountering such an error, here are several steps and areas you can investigate to troubleshoot and hopefully resolve the issue:

🔍 Error Features & Identifiers

| Feature | Description | |---------|-------------| | Error text | "a basic application could not be started wincc 75" | | Affected software | Siemens WinCC (Version 7.5) — often Runtime or Explorer | | Commonly appears when | Starting WinCC Runtime, opening a project, or after a Windows update | | Primary symptom | WinCC fails to launch the basic application (e.g., graphics runtime, global script, or tag management) | | Typical error codes (accompanying) | May appear with 0x8000FFFF, 0x80040154, or HRESULT errors in Windows Event Log |

2. Installation and Configuration

  • Reinstall WinCC: If the application was working previously, try reinstalling it. Ensure you have the installation media and a valid license.
  • Check Configuration Files: Corrupted configuration files can prevent the application from starting. Check for any recent changes to configuration files or system settings.

3. Run WinCC as Administrator (and Disable UAC)

WinCC needs elevated rights to write to protected system folders. a basic application could not be started wincc 75

  • Right-click the WinCC Explorer shortcut → Properties → Compatibility → Check “Run this program as an administrator”.
  • Optional but effective: Temporarily disable User Account Control (UAC) via Control Panel → User Accounts → Change UAC settings → set to “Never notify”. Reboot.

⚠️ Re-enable UAC after troubleshooting for security.

Step 4: Repair SQL Server (WinCC Native Database)

WinCC 7.5 uses a bundled SQL Server (Siemens specific). If SQL is paused or corrupted, the basic startup sequence fails. The error message "A basic application could not

Check SQL status:

  1. Press Win + R, type services.msc, press Enter.
  2. Look for services named: MSSQL$WINCC or SQL Server (WINCC).
  3. Ensure the status is Running. If not, right-click > Start.

Repair SQL Instance:

  1. Open Control Panel > Programs and Features.
  2. Find Microsoft SQL Server (Version) – Do not uninstall.
  3. Right-click > Change > Repair.
  4. Follow the wizard. Insert your WinCC DVD if prompted.

Step 2: Run WinCC as Administrator (Permanent Setting)

WinCC 7.5 requires extensive system access. If UAC is enabled, the "basic application" will be blocked.

Fix:

  1. Navigate to C:\Program Files (x86)\Siemens\WinCC\bin\
  2. Right-click WinCCExplorer.exe (or the specific runtime executable).
  3. Select Properties > Compatibility tab.
  4. Check "Run this program as an administrator".
  5. Click Change settings for all users and repeat.
  6. Apply > OK.
  7. Restart your PC.

Option B: Reinstall the Siemens Common App Framework

The error sometimes lives in a shared component used by TIA Portal and WinCC.

  1. Open Control Panel > Programs and Features.
  2. Find "Siemens Automation Common Applications" (version depends on your install).
  3. Click Repair.
  4. Reboot.

6. Corrupted Installation or Missing Hotfixes

WinCC 7.5 requires specific updates (e.g., Update 15, 16, or 17). Running a base version without critical hotfixes can cause runtime failures, especially on Windows 10 or Windows Server 2019/2022. Reinstall WinCC: If the application was working previously,