A Basic Application Could Not Be | Started Wincc 75
A locked-down Windows 10/11 IoT or Server installation may block WinCC services.
WinCC 7.5 requires administrative privileges. If the user launching runtime does not have full read/write access to the project folder, %ProgramData%\Siemens\, or the SQL Server instance, basic apps will abort.
For automation engineers and plant operators, few things are as frustrating as a Siemens WinCC runtime that refuses to start. One of the more cryptic and persistent errors you might encounter in WinCC V7.5 (and earlier versions) is the message:
“A basic application could not be started.”
This error typically appears when trying to activate a WinCC project, either during initial development or after a system reboot. It signals that the WinCC runtime environment cannot initialize a core component, often leaving you stuck with no visualization, no alarms, and no control.
This article breaks down what this error means, why it happens, and—most importantly—how to fix it.
Siemens provides a tool (often found in the installation directory or via Support) that resets the WinCC environment to a clean state without deleting project data. This is highly effective if registry keys are stuck.
Based on Siemens support documentation and real-world experience, this error often stems from:
Troubleshooting the "A basic application could not be started" error in WinCC 7.5 involves a systematic approach to checking the system's configuration, software installation, and operational environment. Documenting any changes made during the troubleshooting process can help in case you need to escalate the issue to Siemens support or to a WinCC expert.
The error message "A basic application could not be started" in SIMATIC WinCC 7.5 usually indicates a conflict between the software, its required SQL Server instance, or the operating system's compatibility. Common Root Causes
Version Incompatibility: WinCC 7.5 and its Service Packs have strict Windows version requirements. For example, using WinCC 7.5 SP2 on certain builds of Windows 10 (like 22H2) may require specific updates (e.g., Update 15) to function.
SQL Server Instance Corruption: WinCC relies on a specific "WinCC" instance of MS SQL Server. If this instance was not installed correctly or was left over from a previous, incompatible version of WinCC, the application will fail to launch.
Invalid or Missing Licenses: While the error text focuses on the application, it often accompanies license-related checks. An incorrect or damaged license in the Automation License Manager can trigger this. PC Environment Issues: a basic application could not be started wincc 75
Computer Name: The computer name must not contain special characters or underscores.
User Groups: The logged-in user must be a member of the local "SIMATIC_HMI" user group.
Network Status: In WinCC 7.5 SP2, the terminal bus adapter must be connected to a network (switch or router) for certain components to initialize. Step-by-Step Troubleshooting
Run Reset_WinCC: Close all WinCC windows and run the Reset_WinCC.vbs script (typically found on the desktop or in the WinCC installation folder) to clear stuck processes.
Verify Compatibility: Use the Siemens Compatibility Tool to ensure your specific Windows build number is supported by WinCC 7.5 SP1/SP2.
Install Latest Updates: Check SiePortal (Siemens Support) for the latest Update (Upd) for your version of WinCC 7.5. Many "application could not be started" bugs are resolved in cumulative updates.
Check SQL Services: Ensure the SQL Server (WinCC) service is running in Windows Services (services.msc).
Reinstall Cleanly: If the error persists, you may need to uninstall WinCC and the MS SQL Server instance entirely before performing a fresh installation. Ensure you are not installing via RDP (Remote Desktop) or with an active virus scanner. 5? Possible causes for "Reset_WinCC.vbs" - SiePortal
Shut down winCC. 2). On the desk top there is an icon labelled something like "reset winCC". 3). Siemens SiePortal Possible causes for "Reset_WinCC.vbs" - SiePortal
Shut down winCC. 2). On the desk top there is an icon labelled something like "reset winCC". 3). Siemens SiePortal
WinCC 7.5 / "A basic application could not be started" message
| Step | Action | Success Rate |
| :--- | :--- | :--- |
| 1 | Run WinCC as Administrator (Properties > Compatibility) | 40% |
| 2 | Disable UAC via Registry (EnableLUA = 0) | 70% |
| 3 | Start SQL Server service (MSSQL$WINCC) | 15% |
| 4 | Turn off Windows Controlled Folder Access | 20% |
| 5 | Re-register COM controls (regsvr32) | 30% |
| 6 | Repair Siemens Common Applications | 25% | A locked-down Windows 10/11 IoT or Server installation
If you have tried all steps above and the error still appears, the final resort is an in-place upgrade repair of WinCC 7.5 (run Setup.exe > Repair) or a full Windows reinstallation. However, in 95% of real-world cases, disabling UAC and running as administrator solves the problem instantly.
Disclaimer: Always ensure you have a full project backup and system restore point before modifying registry or security settings. Siemens WinCC is a registered trademark of Siemens AG.
The "A basic application could not be started" error in WinCC 7.5 is a frequent stumbling block often tied to deep-seated configuration issues rather than just a missing file
. Here is a review of why this happens and how to fix it based on community consensus from Siemens SiePortal and technical forums. Siemens SiePortal Common Root Causes SQL Server Corruption
: This is the most notorious culprit. If the MS SQL instance for WinCC is installed incorrectly or has leftover data from a previous version, WinCC Explorer will fail to launch. OS Incompatibility
: Running WinCC 7.5 on unsupported versions of Windows 10 (like certain Business builds) or missing critical Service Packs often triggers this generic error. Network Adapter Issues
: In WinCC V7.5 SP2, the terminal bus adapter must be active and connected to a switch/router; otherwise, the startup may hang. User Group Permissions : The logged-in Windows user must be a member of the local SIMATIC_HMI user group. Troubleshooting Checklist
WinCC 7.5 / "A basic application could not be started" message
The error message "A basic application could not be started"
in WinCC 7.5 (often followed by "please check your software license") typically indicates a deep-seated communication failure between WinCC and its underlying SQL Server instance, or a critical software incompatibility.
Because this error is notoriously difficult to clear, troubleshooting usually follows a specific escalation path: 1. Initial Quick Fixes
Before diving into a full reinstallation, try these common "reset" procedures: Reset_WinCC.vbs WinCC 7
Locate this script (usually in the WinCC installation directory or via a desktop shortcut) and run it to clear stuck processes. Restart your PC immediately afterward. Check User Rights: Ensure your current Windows user is a member of the "SIMATIC HMI" local user group. Verify Computer Name:
WinCC and SQL Server are extremely sensitive to computer names. Ensure your PC name has no special characters or underscores ( 2. Verify Compatibility and Updates
Compatibility mismatches are a leading cause of this error in newer Windows environments. Operating System Version: If you are running Windows 10 22H2 with WinCC 7.5 SP2, Siemens documentation often specifies that you (or the latest available) for it to function correctly. Software Coexistence: Ensure you don't have conflicting software like WinCC Professional
(TIA Portal) installed alongside WinCC V7.5, as they share resources and often clash. Siemens Compatibility Tool:
Cross-reference your exact Windows build number and WinCC version on the Siemens Compatibility Tool 3. Advanced Troubleshooting
If the error persists when trying to open a specific project: Possible causes for "Reset_WinCC.vbs" - SiePortal
The error "A basic application could not be started" in WinCC 7.5 typically indicates an environmental conflict, such as software incompatibility, incorrect user permissions, or a corrupted SQL server instance. 🛠️ Key Troubleshooting Steps
Verify OS Compatibility: Use the Siemens Compatibility Tool to ensure your Windows build (e.g., 22H2) is fully supported by your specific WinCC 7.5 SP/Update version.
Check User Permissions: Ensure your Windows user is a member of the "SIMATIC HMI" and "Administrators" groups.
Run Reset_WinCC: Execute the Reset_WinCC.vbs script located in the WinCC \bin directory to clear hung processes and reset the application environment.
Check Computer Name: Confirm your computer name contains no special characters or underscores, as these can interfere with SQL Server instance registration.
Update Software: Install the latest updates for WinCC (e.g., Update 15 for SP2) and ensure Microsoft Edge is up to date, as older versions can cause SQL communication failures.
WinCC 7.5 / "A basic application could not be started" message
If the project is configured to communicate with a PLC (AS) but the communication driver (e.g., SIMATIC S7 Protocol Suite) is missing, incorrectly configured, or the S7OIEH components are broken, the runtime may fail to initialize the connection layer.