To avoid encountering this error in the future:
| 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% |
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 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. a basic application could not be started wincc 75
WinCC 7.5 / "A basic application could not be started" message
The error "A basic application could not be started" in WinCC 7.5 usually indicates an issue with the SQL Server (WINCC) software compatibility licensing services Immediate Troubleshooting Steps Check SQL Server Services SQL Server Configuration Manager or Windows Services ( services.msc SQL Server (WINCC)
If "Server Not Available" persists, try changing the "Log on as" setting for the SQL Server Agent (WINCC) Network Service and restart the service. Run Reset WinCC Navigate to the WinCC installation directory (typically C:\Program Files (x86)\Siemens\WinCC\bin Run the script CCCleaner.exe Reset_WinCC.vbs and restart your PC. Verify User Groups Ensure your Windows user is a member of the SIMATIC_HMI local user group. Compatibility & Environment Fixes
WinCC 7.5 / "A basic application could not be started" message
How to Fix "A Basic Application Could Not Be Started" in WinCC 7.5
If you are working with Siemens WinCC V7.5, encountering the error message "A basic application could not be started. Please check your software license" can be a major roadblock. This error typically triggers when you try to open the WinCC Explorer or activate a project. 1. Verify License Status
The most common culprit is a missing or incompatible license. WinCC 7.5 requires specific "RC" (Runtime and Configuration) or "RT" (Runtime) licenses. The Fix: Open the Automation License Manager (ALM). Check if your licenses are visible and "OK."
Ensure you haven't upgraded to WinCC 7.5 while still holding a 7.4 license; Siemens licenses are version-specific.
Right-click your license and select Check to ensure it isn't corrupted. 2. Reset the WinCC Project (CCCleaner) To avoid encountering this error in the future:
Sometimes, background processes from a previous session don't close properly, preventing a new "basic application" from launching. The Fix: Close WinCC and all SIMATIC software.
Open your Windows search bar and type "CCCleaner" (Reset WinCC).
Run the tool. It will terminate all lingering WinCC processes and clean up the temporary runtime environment. Restart your computer and try opening the project again. 3. Check SQL Server Instance
WinCC 7.5 relies heavily on Microsoft SQL Server (WinCC instance). If the SQL service isn't running, the WinCC Explorer cannot initialize. The Fix: Press Win + R, type services.msc, and hit Enter. Find SQL Server (WinCC).
Ensure the status is Running. If it is stopped, right-click and select Start. Also, ensure the SQL Server Browser service is running. 4. Simatic Shell Configuration
If you are working in a client-server architecture, a misconfigured Simatic Shell can cause initialization failures. The Fix: Go to This PC or File Explorer. Find Simatic Shell in the navigation pane. Right-click it and select Settings.
Ensure the correct network adapter is selected (the one physically connected to the PLC or server network). 5. Windows Updates and Compatibility
WinCC 7.5 has strict compatibility requirements regarding Windows 10/11 builds and .NET Framework versions.
The Fix: Check the Siemens Compatibility Tool online to ensure your Windows "Build" number (e.g., 22H2) is officially supported by WinCC 7.5. If a recent Windows update broke the link, you may need to repair the WinCC installation via the Control Panel. 6. Folder Permissions | Step | Action | Success Rate |
If your WinCC project folder was moved or copied from another machine, the "basic application" might fail because it doesn't have permission to write to the project database. The Fix: Right-click your project folder. Go to Properties > Security. Ensure the "SIMATIC HMI" user group has Full Control.
Still stuck? If none of these steps work, the issue might be a corrupted project file (.mcp). Try creating a brand new project. If the new project opens, your original project database may need a manual attach/detach in SQL Management Studio.
Based on Siemens support documentation and real-world experience, this error often stems from:
WinCC needs elevated rights to write to protected system folders.
⚠️ Re-enable UAC after troubleshooting for security.
If you want to debug this manually:
Would you like a PowerShell script that acts as a simple watchdog for this specific WinCC error?
WinCC depends on:
If these are disabled or corrupted, basic applications fail to start.