A Basic Application Could Not Be Started Wincc 7.5 -

"A Basic Application Could Not Be Started" in WinCC 7.5 usually indicates a failure in the software's communication with the underlying SQL database or a mismatch between the software and the operating system version 🛠️ Core Solutions To fix this, follow these steps in order: Check Windows Compatibility : Ensure your Windows version matches the Siemens Compatibility Tool

. For example, WinCC 7.5 SP2 often requires specific updates (like Update 15) to run on newer Windows 10/11 builds. Update Microsoft Edge

: An outdated Edge browser can break the WinCC basic installation. Open Edge, go to Help and feedback > About Microsoft Edge , and let it update automatically. Run Reset_WinCC : Navigate to the WinCC installation folder (usually C:\Program Files (x86)\Siemens\WinCC\bin CCCleaner.exe Reset_WinCC.vbs to clear hung processes. Check Computer Name : Ensure your PC name does contain special characters or underscores (

), as this prevents the SQL instance from installing correctly. 🔍 Advanced Troubleshooting

If the basic fixes don't work, investigate these deeper technical issues: 🗄️ SQL Server Issues Service Status

: Verify that the "SQL Server (WINCC)" service is running in Windows Services.

: In SQL Server Configuration Manager, try changing the "Log on as" setting for the SQL Server Agent (WINCC) to Network Service Database Corruption

: If you recently copied the project from a CD/USB, ensure the files are not "Read-Only". 🛡️ Installation Integrity Disable Antivirus

: Real-time protection (like Windows Defender) can block critical files during installation.

: Siemens recommends installing WinCC locally rather than via Remote Desktop (RDP) to ensure all components register correctly. Clean Reinstall

: If you had a previous version of WinCC (like V7.4) or WinCC Professional from TIA Portal installed, they can conflict. A clean OS reinstall is often the most reliable path to a working environment. 🔑 License Verification

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

To resolve the error "A basic application could not be started"

, try the following troubleshooting steps derived from community consensus and Siemens support discussions: 1. Verification of Compatibility and Updates Match OS and WinCC Versions A Basic Application Could Not Be Started Wincc 7.5

: Ensure your Windows version is strictly compatible with your WinCC 7.5 Service Pack. For instance, users on Siemens Support Forums found that installing

for WinCC 7.5 SP2 was necessary for compatibility with Windows 10 Pro 22H2. Check Microsoft Edge

: An outdated Edge browser can interfere with SQL Server installations used by WinCC. Update Edge to at least v86.0.622.56 or higher. 2. Software and License Checks Validate Licenses : Verify that a valid WinCC RC (Runtime & Configuration) RT (Runtime) license is visible and activated in the Automation License Manager (ALM) Identify Incompatibilities

: Conflicts often occur if multiple WinCC versions (e.g., WinCC V7 and WinCC Professional) are installed on the same machine. User Permissions : Ensure you are running WinCC with the same user account used during the initial installation. Siemens SiePortal 3. System Fixes Run "Reset-WinCC" Reset_WinCC.vbs

tool (found in the WinCC installation directory) to clear stuck processes and then restart your PC. Clean the Project Directory : Some users reported success by deleting the CPL directory within their project folder. Check SQL Instance Name : Ensure your computer name does not contain special characters underscores

, as these can cause the underlying MS SQL Server instance to fail. 4. Advanced Recovery Run Security Controller : If updates don't work, execute the Security Controller tool to re-apply necessary security settings. Fresh OS Installation : If the error persists after multiple re-installs, the Siemens community

often recommends a clean Windows installation to remove residual registry or SQL conflicts. Siemens SiePortal If you'd like, I can help you identify which Service Pack (SP) you should be on if you tell me your current Windows OS build

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

"A Basic Application Could Not Be Started" in WinCC 7.5 typically indicates a conflict between the software, the SQL Server instance, or underlying Windows security settings Immediate Troubleshooting Steps Run Reset_WinCC : Close all WinCC applications and run the Reset_WinCC.vbs

tool (typically found in the WinCC installation directory) to clear stuck processes, then restart your PC. Verify User Groups : Ensure your Windows user is a member of the local "SIMATIC HMI"

user group. You must have administrative rights to perform this. Check for Special Characters : Ensure your Computer Name does not contain underscores (

) or other special characters, as these can cause the internal SQL instance to fail. Update Microsoft Edge

: On Windows 10 (version 20H2 or later), an outdated Edge browser can interfere with the SQL Server installation used by WinCC. Update Edge via the "About Microsoft Edge" menu and reboot. Configuration & Compatibility SIMATIC Shell Simatic Shell "A Basic Application Could Not Be Started" in WinCC 7

in Windows Explorer, right-click "Settings," and ensure the correct network adapter is selected. For WinCC 7.5+, verify that "Remote Communication" is enabled if working in a distributed system. Install Latest Updates

: Many users resolve this by installing the latest Service Packs (e.g., SP2) and subsequent Updates (e.g., Update 15 for SP2) to address compatibility with newer Windows 10/11 builds. Disable Security Conflicts : Temporarily disable Windows Defender

or third-party antivirus during a repair installation to ensure all components register correctly. Advanced Recovery

If the issue persists, the SQL Server instance may be corrupted. Reinstall SQL & WinCC : Uninstall WinCC and the SQL Server (WinCC)

instance separately. Clean the registry of leftover SQL entries before reinstalling WinCC. Sector Size Issue (Windows 11)

: If using Windows 11, verify that your drive's physical sector size is not greater than 4KB using fsutil fsinfo sectorinfo c: . If it is higher, you may need a registry fix for ForcedPhysicalSectorSizeInBytes to allow SQL Server to run.

Detailed requirements for distributed systems are available at Siemens Industry Online Support registry path for the Windows 11 sector size fix or help checking your compatibility

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

The error "A Basic Application Could Not Be Started" in WinCC 7.5 often stems from software incompatibilities, incorrect installation of SQL Server, or missing updates. Immediate Troubleshooting Steps

Run Reset_WinCC.vbs: Use this script in the WinCC "Bin" folder to terminate stuck processes and restart the system.

Verify SQL Server: Ensure the SQL Server (WINCC) service is running. An incorrectly named computer (containing special characters like underscores) can cause the SQL instance to fail during installation.

Check Operating System Compatibility: Use the Siemens Compatibility Tool to ensure your specific Windows build matches your WinCC version.

Example: WinCC 7.5 SP2 on Windows 10 Pro 22H2 often requires Update 15 or higher to function. corrupted project files or graphics

Update Microsoft Edge: An outdated Edge browser on Windows 10 (version 20H2) can disrupt the SQL Server installation used by WinCC.

Clean Temporary Files: Delete the CPL directory and .ENV file in your project folder if you recently switched Windows users. System Requirements & Configuration

User Rights: Ensure your Windows user is a member of the required Siemens user groups (e.g., SIMATIC HMI).

Avoid RDP/Antivirus during Install: Installing via Remote Desktop or with an active virus scanner can result in missing files.

Project Conversion: If you are opening an older project, you may need to use the Project Migrator.

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

7. Check the WinCC Diagnostics Log

For advanced users:

Step 7: Register DLLs and OCXs Manually

Corrupted COM registration can cause the “basic application” loader to fail.

Virtualized Environments (VMware/Hyper-V)

If running WinCC 7.5 in a VM:

Step 6: Clear the Project Cache (Rebuild LZH)

Sometimes the compressed project archive is the problem.

  1. Close WinCC Explorer completely.
  2. Navigate to your project folder (e.g., C:\WinCC_Prj\MyProject\).
  3. Find the folder named lzh (or LZH).
  4. Delete or rename this folder (e.g., lzh_old).
  5. Re-open WinCC Explorer. It will automatically rebuild the LZH archive from source files.
  6. Try to start the Graphics Designer or Runtime again.

3. Incomplete Installation or Missing Redistributables

If the Visual C++ Redistributables, .NET Framework, or Siemens prerequisites are not correctly installed, the Windows API calls fail.

Summary

This error appears when launching or running a WinCC (TIA Portal / WinCC Professional) 7.5 runtime or project and the runtime fails to initialize. Causes include licensing/activation issues, corrupted project files or graphics, missing or incompatible runtime components, permission problems, or environment mismatches (OS, .NET, Visual C++ runtimes).