A Basic Application Could Not Be | Started Wincc 75 Best
Siemens provides a troubleshooting tool often referred to as WinCCReset or checking the system status.
Navigate to Windows Logs → Application. Look for errors from:
Typical event IDs: 1000, 1001, 1026 (indicating a crash in RTSS.exe or CCERuntime.exe). a basic application could not be started wincc 75 best
| If none of the above works | Action |
|----------------------------|--------|
| Repair WinCC installation | Run WinCC setup → Select Repair. |
| Uninstall/Reinstall WinCC | Use Siemens’ Total Uninstall tool first. |
| Restore VM snapshot | If running on a virtual machine (VMware/Hyper-V). |
| Contact Siemens Support | Provide error log from C:\ProgramData\Siemens\WinCC\Diagnostics.
If the environment is clean, the issue may lie within the project structure or the license configuration. Check for conflicting services : Ensure that no
WinCC 7.5 is highly sensitive to User Account Control (UAC). If the application does not have administrative rights, it cannot start critical background services.
How to fix it:
Pro Tip: To make this permanent, go to Properties > Compatibility > Check "Run this program as an administrator." Then click "Change settings for all users."
Why this works: SQL Server services and license daemons require elevated privileges to write logs and check licenses. Siemens provides a troubleshooting tool often referred to
Open Command Prompt as Administrator and run:
cd C:\Program Files (x86)\Siemens\WinCC\bin
regsvr32 comctrls.ocx
regsvr32 mscomctl.ocx
regsvr32 CCEActiveCtrl.ocx
| Symptom | Solution |
|---------|----------|
| Error only in one project | Use Project Duplicator to create fresh copy |
| Error after moving project | Check path length < 80 chars, no special characters or spaces |
| Error after Windows Update | Run WinCC Installation Repair from Control Panel → Programs → Siemens WinCC → Change → Repair |
| Multi-user / client-server | Verify network share permissions (full control for Everyone temporarily for test) |