WinCC 7.5 uses specific versions of SQL Server (e.g., SQL Server 2014 or 2017 Standard/Express). If the SQL instance WINCC is stopped, disabled, or corrupted, WinCC cannot start its basic data applications.
The error “A basic application could not be started” in WinCC 7.5 is a generic but solvable issue. Do not let the vague wording intimidate you. In 90% of cases, the fix is administrative privileges or a path correction. In more stubborn cases, the SQL Server service or antivirus is the culprit.
By systematically working through this guide—checking permissions, verifying SQL, cleaning the LZH cache, and inspecting Event Viewer—you can pinpoint the exact “basic application” that is failing and restore full functionality to your Siemens WinCC 7.5 environment.
Final Pro Tip: Always keep a copy of the Siemens Installation Logs (%TEMP%\SIEMENS.log). If all else fails, Siemens Technical Support will ask for this file to identify the missing application component.
Have a different variation of this error? Let us know in the comments. For urgent industrial production stops, contact Siemens Industrial Support with your WinCC version and Windows build number.
The error "A Basic Application Could Not Be Started" in WinCC 7.5 typically indicates a corrupt installation, missing updates, or software incompatibilities rather than just a simple licensing issue. This "basic application" often refers to the SQL Server or the WinCC Project Manager failing to initialize. Immediate Troubleshooting Steps A Basic Application Could Not Be Started Wincc 7.5
Check Software Compatibility: Ensure your version of Windows (e.g., Windows 10 22H2) is compatible with your WinCC version. You may need to install a specific service pack or update, such as Update 15 for WinCC 7.5 SP2, to resolve stability issues on newer Windows builds.
Run Reset Tool: Use the reset_wincc.vbs tool located in the WinCC installation directory and then restart your computer to clear hung processes.
Verify User Permissions: Always start WinCC with the same user account used during the initial installation to avoid permission-based startup failures.
Check Windows Event Viewer: Look for Event ID 10010 (DCOM registration timeout) or other errors under Windows Logs > Application to identify if the SQL server failed to respond. Advanced Solutions
Reinstall SQL Instance: If the SQL server instance was not installed correctly, the project manager cannot start. Some users recommend uninstalling both WinCC and the SQL instance entirely, then reinstalling them. Ensure your computer name does not contain special characters (like underscores), as this can break SQL installations. WinCC 7
License Verification: Although the error message often mentions licensing, verify your license status in the Automation License Manager. If the license is missing or invalid, WinCC may fail to open existing or new projects.
Network Check: If your PC is not connected to a network, the project may take a very long time to open or fail if it cannot find the terminal bus. Ensure your network cards are correctly ordered and functional.
For official guidance and specific patches, visit the Siemens SiePortal Support Forum or use the Siemens Compatibility Tool to verify your software environment.
Are you attempting to open an existing project or create a new one when this error appears?
Blog Title: Fixing the Frustration: Resolving “A Basic Application Could Not Be Started” in WinCC 7.5 Have a different variation of this error
Published by: The Automation Journal Reading Time: 4 minutes
There are few things more stressful in an automated production environment than clicking on your WinCC Runtime icon and being greeted by a vague, brick-wall error message instead of your HMI.
If you are using SIMATIC WinCC 7.5 (or 7.4/7.3), you have likely encountered the dreaded dialog box: “A basic application could not be started.”
What does “basic application” even mean? As frustrating as it is, this error is usually a sign of a specific system conflict rather than a corrupt project. Let’s break down what causes this and, more importantly, how to fix it.
If running WinCC 7.5 in a VM: