DIFFUS

A Basic Application Could Not Be Started Wincc 75 Best ((install)) -

The error "A basic application could not be started. Please check your software license" in WinCC 7.5 often indicates a deeper issue than just a missing license. It typically signals a conflict between WinCC, its underlying SQL Server instance, or the Windows operating system version. Top Troubleshooting Steps

Check Windows Compatibility: WinCC 7.5 has strict compatibility requirements. For instance, WinCC 7.5 SP2 on Windows 10 Pro 22H2 often requires Update 15 or higher to function correctly. Use the Siemens Compatibility Tool to verify your specific OS build.

Update Microsoft Edge: An outdated version of Edge can interfere with the SQL Server installation used by WinCC. Updating Edge to v86.0.622.56 or higher via the browser's "About" menu can sometimes resolve startup errors.

Run Reset_WinCC: Navigate to the WinCC Bin folder and run Reset_WinCC.vbs. This script terminates all hanging WinCC processes. Restart your PC immediately afterward and try opening the project again.

Verify User Groups: Ensure your Windows user account is a member of the "SIMATIC HMI" and "Administrators" local groups.

Clean SQL Reinstallation: If the error persists, the SQL instance may be corrupted. Users often find success by completely uninstalling WinCC and the manual removal of all MS SQL Server components before reinstalling. Community Insights on Fixes

Many users on Siemens SiePortal have found that this error often stems from incompatible software "residue" or specific system configurations.

“If you have any WinCC software installed previously... Try to reinstall windows from zero to avoid problems.” Siemens SiePortal

“My actual problem was I installed WinCC 7.5 SP2 on Windows 10 Pro 22H2. If you follow the note... you should install update 15 for WinCC 7.5 SP2 then solved.” Siemens SiePortal Critical System Checks a basic application could not be started wincc 75 best

Computer Name: Ensure your computer or server name contains no special characters (including underscores), as this can break the SQL instance installation.

Software Conflicts: Do not have WinCC V7 and WinCC Professional (TIA Portal) installed on the same partition, as they are often incompatible.

Are you attempting to create a new project or open an existing one when this error appears?

The error "A basic application could not be started, please check your software license" in WinCC 7.5 typically points to a conflict between your Windows version and the WinCC Service Pack (SP), or an issue with the Microsoft SQL Server instance used by WinCC. Common Solutions

Check Windows Compatibility: Ensure your Windows version matches your WinCC 7.5 SP level. For example, users on Windows 10 Pro 22H2 often need WinCC 7.5 SP2 Update 15 or higher to resolve this specific startup error. You can verify this using the Siemens Compatibility Tool.

Verify Computer Name: Ensure your computer or server name does not contain special characters or underscores. Special characters can cause the SQL instance to install incorrectly, triggering this "basic application" error during startup.

Run Reset_WinCC.vbs: Try running the reset script located on your desktop or in the WinCC installation folder. This often clears stuck background processes that prevent a fresh application start.

Check License via ALM: Open the Automation License Manager (ALM) and ensure your license (RC for configuration or RT for runtime) is correctly activated and visible. If the license is missing or invalid, the "basic application" will fail to initialize. The error "A basic application could not be started

Avoid RDP for Installation: Installing WinCC via a Remote Desktop (RDP) connection or with an active antivirus can result in incomplete file registration. If the issue persists, a clean reinstallation on the local machine with antivirus disabled is recommended. Advanced Troubleshooting

If the above steps fail, users in the Siemens Support Forum suggest checking for software conflicts, such as having WinCC Professional and WinCC V7.x installed on the same machine, which are often incompatible.

Have you checked the Automation License Manager to see if your license is listed as "OK"?

WinCC 7.5 / "A basic application could not be started" message

The error "A basic application could not be started" in WinCC 7.5 typically indicates issues with software compatibility, licensing, or corrupted project registration. Primary Troubleshooting Steps

Verify OS Compatibility: Ensure your version of Windows 10/11 is compatible with WinCC 7.5 SP1/SP2. Users have reported this error when running WinCC on unsupported Windows builds (e.g., Windows 10 22H2 without necessary updates).

Run Reset_WinCC: Use the built-in reset tool to clear hanging processes. Close all WinCC applications.

Navigate to C:\Program Files (x86)\Siemens\WinCC\bin (or similar path) and run Reset_WinCC.vbs or use CCCleaner.exe -terminate via command line. Fix 4: Check the Windows Event Viewer for

Check Software Licenses: This error is frequently tied to missing or invalid licenses. Open the Automation License Manager (ALM) and confirm you have a valid WinCC RC (Release/Configuration) or RT (Runtime) license active.

Validate SQL Server Instance: WinCC relies on a specific SQL instance. Ensure the ...\WINCC instance exists and is running in the SQL Server Management Studio. If the SQL server was installed incorrectly or the computer name contains special characters (like underscores), WinCC may fail to start. Advanced Fixes

WinCC 7.5 / "A basic application could not be started" message

Fix 4: Check the Windows Event Viewer for Hidden Clues

The "basic application could not be started" message is generic. Windows Event Viewer will tell you exactly which application failed.

How to do it:

  1. Press Win + X and select Event Viewer.
  2. Go to Windows Logs > Application.
  3. Look for Error events with the source "Application Error" or ".NET Runtime" or "SideBySide" at the exact time you tried to start WinCC.
  4. Common findings:
    • "Faulting module: KERNELBASE.dll" → Indicates a missing system update or corrupted VC++ Redistributable.
    • "Faulting module: SQLSERVR.exe" → SQL Server died. Reinstall SQL instance.
    • "0xc000007b" error → Architecture mismatch (32-bit vs 64-bit DLL conflict).

Action: Once you identify the failing module, download the relevant update from Microsoft or Siemens Support.

1. Check Windows Services (Most Common Fix)

The Basic Application relies on specific Windows services. Verify they are running.

5. Last Resort Actions

  1. Complete WinCC 7.5 reinstallation (after full uninstall including SQL Server instances)
  2. Restore Windows to a previous restore point (if error started after software/driver change)
  3. Test on a clean virtual machine – if it works there, your OS environment is corrupted

9. Check for Software Conflicts

2. Common Root Causes (WinCC 7.5 Specific)

| Cause Category | Specific Issue | |----------------|----------------| | Windows Permissions | WinCC runtime services lack administrator rights or UAC blocks processes. | | Antivirus / Firewall | Real-time scan blocks RTMessages.exe, PdlRt.exe, or CCEServer.exe. | | License Malfunction | Missing or corrupted license for the basic runtime (e.g., RT 128/512/1024). | | Project Corruption | Damaged .mdf / .ldf database files or inconsistent project configuration. | | SQL Server Issues | SQL Server 2016/2019 instance for WinCC not running or blocked. | | Windows Updates | Recent .NET or VC++ redistributable updates breaking WinCC dependencies. | | Multi-User Conflicts | Another WinCC runtime or demo project already active. |