This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
This error typically appears immediately upon attempting to activate a project via the WinCC Explorer or the Simatic Shell. It suggests that the core components required to host the runtime (graphics, tags, or database connections) have crashed or timed out before the user interface could even render.
WinCC 7.5 SP2 requires specific updates to run on modern Windows 10/11 versions.
WinCC v7.5 relies on the daemon to constantly validate authorization rings. If the ALM service crashes or becomes corrupted during a Windows Update, the licensing system returns a generic block. Furthermore, accessing a development station through a default Windows Remote Desktop Protocol (RDP) connection automatically restricts standard USB dongle or soft-license handshakes, triggering this error.
Try reopening the project. WinCC will compile a fresh, uncorrupted version of the file. 5. Check Windows User Group Memberships a basic application could not be started wincc 75 best
Reset or disable the SIMATIC WinCC TM Naming Service if unneeded. Database Reset Run built-in diagnostics scripts Use Reset_WinCC.vbs to safely drop stuck database hooks. 🔍 Root Causes Explained 1. Invalid or Broken License Handshakes
Never manually delete files within the SQL data folders (
: Download and install the latest available Update (e.g., Update 15 for SP2) for your specific WinCC 7.5 version .
This utility resets the WinCC environment, clears temporary project data, and resolves corrupted registry entries. This public link is valid for 7 days
Locate the file Reset_WinCC.vbs in the WinCC \Bin folder. Run it to terminate hanging processes and reset the environment, then restart your PC.
Troubleshooting WinCC 7.5: Resolving the "A Basic Application Could Not Be Started" Error
"A basic application could not be started" typically points to issues with software compatibility, missing updates, or corrupted SQL Server instances Quick Fixes to Try First Run Reset_WinCC : Close all WinCC applications and run Reset_WinCC.vbs
The SQL service WinCC did not start correctly, preventing database access. Can’t copy the link right now
In WinCC V7.5 (including SP1 and SP2), this issue often stems from broken SQL database links, corrupted projects, incorrect Windows security settings, or missing runtime components.
Ultimate Troubleshooting Guide: Fixing the WinCC v7.5 "A Basic Application Could Not Be Started" Error
The user running WinCC is not part of the SIMATIC HMI group.