shut down WinCC projects properly before turning off the computer. Ensure your user account has Windows Administrative rights.
"A basic application could not be started" in WinCC 7.5 often indicates a mismatch between the software version and the Windows operating system, or issues with user permissions and required background services Quick Fixes to Try First Run as Administrator : Right-click the WinCC Explorer shortcut and select Run as Administrator to ensure all processes have necessary permissions. Reset WinCC : Go to the WinCC installation folder (e.g., C:\Program Files (x86)\Siemens\WinCC\bin Reset_WinCC.vbs . Restart your computer afterward. Verify User Groups : Ensure your Windows user account is a member of both the Administrator SIMATIC HMI local user groups. Common Root Causes and Solutions
By following these steps, you should be able to overcome the "basic application could not be started" error in WinCC 7.5 and successfully launch your project.
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. a basic application could not be started wincc 75
Do you have or TIA Portal also installed?
: In Windows 10 version 20H2, an outdated Microsoft Edge browser can interfere with SQL Server installation. Update Edge to version 86.0.622.56 or higher. Licensing & User Rights
To resolve the "A basic application could not be started" error in WinCC 7.5, follow these step-by-step troubleshooting guides: shut down WinCC projects properly before turning off
Uninstall (specifically the WINCC instance). Restart the computer.
Navigate to the WinCC installation directory: C:\Program Files (x86)\Siemens\WinCC\bin . Run Reset_WinCC.vbs as Administrator and your PC. Update WinCC :
Troubleshooting: "A Basic Application Could Not Be Started" in WinCC 7.5 Reset WinCC : Go to the WinCC installation folder (e
The most frequent cause for WinCC 7.5 is running an older Service Pack on a newer Windows 10 release (like 21H2 or 22H2).
If the above steps fail, you may have a corrupted SQL instance. As suggested on Reddit/PLC and Siemens forums , a complete reinstallation is required.
Corrupted runtime files are a prime suspect.
Often, a service gets stuck in “Starting” or “Stopping” state.
