WinCC v7.5 SP2 Basic Application Not Started: License Error Fix

Problem Summary

A fresh SIMATIC WinCC V7.5 SP2 installation on a workstation running Microsoft Windows 10 Business reports the following dialog immediately after creating or opening a project in WinCC Explorer:

"A basic application could not be started. Please check your software licenses."

The installer completes without error, the license file imports cleanly into the Automation License Manager (ALM), and the ALM Check command returns a green status. Despite all of these indicators being healthy, WinCC refuses to load its base components and displays the dialog above on every Explorer launch. This article documents the root cause, the diagnostic procedure, and the resolution options for engineering and commissioning teams who encounter the symptom.

Affected Versions and Environment

Root Cause: Unsupported Windows 10 Edition

WinCC V7.5 SP2 performs a hard validation of the host operating-system edition during the startup phase of WinCC Explorer. The check runs before any licensed subsystem is loaded and is independent of the ALM license state. The authoritative source for the supported-OS matrix is the WinCC V7.5 SP2 readme / delivery release, published as Siemens Support Entry 109783852.

Microsoft Windows 10 Business is positioned as a value-priced SKU targeted at small and medium organizations. It is excluded from the WinCC V7.5 SP2 compatibility matrix together with other non-enterprise SKUs such as Windows 10 Home, Windows 10 S, and Windows 10 Pro Education. The supported set typically includes Windows 10 Pro, Windows 10 Enterprise (SAC), Windows 10 Enterprise LTSC, and Windows 10 IoT Enterprise on the engineering-station side, and matching Windows Server SKUs on the runtime / server side.

Why ALM Check returns green

ALM validates only the cryptographic integrity of the license file, the binding between the license key and the machine fingerprint, and the not-expired condition. It does not evaluate the host OS against an application allow-list. A green ALM Check therefore proves that the license blob is well-formed; it does not prove that WinCC will load on this OS edition.

Startup decision flow

Diagnostic Procedure

Work the four diagnostic steps in order. Each step is independent and produces evidence that you can attach to a service ticket.

Step 1 - Confirm the exact Windows edition

1. Press Win + R, type winver, press Enter.
2. Capture a screenshot showing the Edition, Version (for example 22H2) and OS Build (for example 19045.xxxx).
3. Cross-reference the recorded edition against the WinCC V7.5 SP2 readme. If the edition is not on the supported list, the dialog is by design and the OS is the root cause.

The winver dialog is the most reliable evidence because the Windows UI sometimes masks the underlying SKU in other dialogs. You can also verify programmatically with PowerShell:

Get-ComputerInfo | Select-Object WindowsProductName, WindowsEditionId, OsBuildNumber, WindowsInstallationType

Compare WindowsEditionId against the supported set. Common values and their compatibility with WinCC V7.5 SP2:

Step 2 - Validate the Automation License Manager state

1. Start > Siemens Automation > Automation License Manager.
2. Locate the WinCC license in the right-hand pane. Right-click > Check. A green icon confirms cryptographic integrity.
3. Right-click > Show Properties. Confirm the following fields:
     • Validity: expiry date in the future.
     • Type: matches the purchased variant (Single, Floating, or Upgrade).
     • Target system: matches the host hardware fingerprint.
4. If the license is flagged as Defective, re-download the license file from the Siemens License Key Web portal and re-import via License Key > Install (or drag-and-drop into the ALM window).

A green ALM Check combined with an unsupported OS confirms the exact symptom documented in this article.

Step 3 - Verify the WinCC services

WinCC V7.5 SP2 depends on several Windows services that are installed by the WinCC setup. Two of them must be in a Running state before any project can be opened:

Open services.msc, scroll to the entries above, and verify each. If the message-router service is missing entirely, the WinCC installation has been corrupted and must be repaired via Control Panel > Programs and Features > SIMATIC WinCC V7.5 SP2 > Repair. This is independent of the OS edition issue, but both conditions can coexist on a freshly-imaged station.

Step 4 - Query the Siemens Compatibility Tool

The Compatibility Tool on the Siemens Industry Online Support portal accepts the WinCC article number, the exact Windows edition string from Step 1, and the OS build number. It returns one of three statuses:

• Released - the combination is officially supported.
• Released with restrictions - supported, but specific components or behaviors are restricted.
• Not released - the combination is not supported. A Not released status for WinCC V7.5 SP2 on Windows 10 Business is the official confirmation of the root cause.

Save the Compatibility Tool report alongside the winver screenshot. Both are needed when escalating to Siemens Technical Support.

Resolution Options

Choose exactly one of the following resolutions. Do not combine them.

Option A - Upgrade the Windows edition in place (preferred)

Microsoft provides an in-place edition-upgrade path that converts Windows 10 Business to Windows 10 Enterprise (or Pro) without reinstalling applications or migrating user profiles. The WinCC installation, the project files, and the ALM license binding all survive the upgrade because they are bound to the hardware fingerprint rather than to the Windows product key.

1. Open Settings > Update & Security > Activation.
2. Click Change product key.
3. Enter a valid Windows 10 Pro or Windows 10 Enterprise product key. The key must be valid for the existing activation infrastructure (KMS, MAK, or retail).
4. Confirm the upgrade. Windows will reboot one or more times.
5. After reboot, run winver and confirm the new edition.
6. Launch WinCC Explorer and confirm the dialog no longer appears.

Option B - Move the project to a supported host

Use this option when the engineering station hardware is locked to Windows 10 Business by corporate policy and Option A is not available.

1. Identify a target workstation or VM that runs a supported edition (Windows 10 Pro, Enterprise, or IoT Enterprise) on the same Windows version and build as listed in the WinCC V7.5 SP2 readme.
2. On the original host, export the license: in ALM, right-click the WinCC license > Export. Choose a secure storage location. The exported file is a .zip containing the .lic blob.
3. On the new host, install WinCC V7.5 SP2 and the matching ALM version. The ALM version on the new host must match or exceed the source.
4. Transfer the project folder (*.mcp, subfolders, GraCS, Library, PRT) using a method that preserves NTFS ACLs if the project uses Windows authentication. robocopy /MIR /SEC is recommended.
5. Import the license on the new host: ALM > License Key > Install. If the new hardware fingerprint differs from the source, the source license must first be marked defective in the License Key Web portal before it can be re-activated on the new hardware.
6. Open the project in WinCC Explorer on the new host. Run Project > Compiler > Check All to confirm the transfer was clean.

Option C - Use a hypervisor with a supported guest

When neither the host hardware nor the corporate image policy allows an edition change, deploy a Type-2 hypervisor (Hyper-V, VMware Workstation, or VirtualBox) on the Windows 10 Business host and run a supported Windows edition in the guest. WinCC validates the guest OS, not the host OS, so this configuration is fully supported as long as the guest edition and build are on the WinCC V7.5 SP2 matrix. Pass-through of USB license dongles works over the hypervisor's USB redirection.

Option D - Clean install on a supported Windows edition

If the workstation is being replaced as part of a hardware refresh, image the new host with a supported Windows edition, install WinCC V7.5 SP2, and transfer the project and license using the steps in Option B. This is the most reliable long-term path because it eliminates the possibility of residual unsupported components.

Verification

After applying Option A, B, C, or D, perform the following checks before declaring the case closed:

1. winver shows an edition present in the WinCC V7.5 SP2 readme matrix. Capture a screenshot for the commissioning sheet.
2. Launch WinCC Explorer. The license dialog must not appear.
3. Create a new test project via File > New and confirm the wizard reaches the Finish step.
4. Activate the project. Runtime should start and the standard graphics should render without further license errors.
5. Open ALM and re-run Check on the WinCC license. The result must still be green.
6. Restart the engineering station. Re-open the project. Runtime must auto-start (if so configured) without prompting.
7. Re-run the Siemens Compatibility Tool and archive the resulting Released certificate with the project documentation.

If the dialog reappears after a Windows feature update, the OS edition may have been silently changed by the update or by an IT policy push. Re-run Diagnostic Step 1 to confirm the edition.

Related Failure Modes with the Same Dialog

The dialog string "basic application could not be started" can mask several other failure modes. Use the matrix below to triage before assuming this article's root cause.

Preventive Recommendations

• Run the Compatibility Tool query against the exact Windows edition string (not just the major version) before commissioning any new WinCC engineering or runtime station. Save the resulting Released certificate with the project's FAT/SAT documentation.
• Document the Windows edition, version, and OS build on the commissioning sheet. Windows feature updates can silently change the SKU on volume-licensed machines, and the change may not be visible in standard desktop diagnostics.
• Maintain a golden image of a known-good engineering station so a corrupted WinCC installation can be replaced in minutes. Include ALM and the license file in the image so a re-image restores the licensing state too.
• Store ALM license receipts, the License Key ID, and the License Key Web portal credentials in a secure password manager. Re-downloading the license from the portal is the fastest path to recovery when the local copy is lost.
• Schedule a quarterly review of the Windows edition on every WinCC station. Hardware refreshes and re-imaging cycles often land on a different SKU than the original, especially on machines provisioned by a separate IT department.
• For multi-user environments, prefer floating licenses on a dedicated license server running Windows Server 2016 or 2019 Standard / Datacenter. This isolates licensing from individual engineering workstations and reduces re-licensing work when a workstation is re-imaged.

License Life-Cycle Background

WinCC licensing is managed by the Automation License Manager (ALM), which ships with WinCC V7.5 SP2 and is shared across the SIMATIC product family. A license moves through four lifecycle states:

1. Available - the license key exists in the customer's License Key Web portal but has not been activated on any hardware.
2. Active - the license has been activated on a specific hardware fingerprint via ALM and is consumable by WinCC on that host.
3. Defective - the license has been marked as damaged or unusable in the portal, and a fresh download is required to reactivate.
4. Expired - the validity date in the license file has passed. This applies to trial licenses and to subscription licenses; perpetual licenses do not enter this state on their own.

When WinCC cannot find an Active license that matches the project type, it runs in non-licensed mode. In non-licensed mode, most runtime functions are disabled and a watermarked banner is displayed. The TIA Portal documentation describes this behavior in more detail under Licensing STEP 7 and WinCC. Note that the dialog documented in this article is raised before the non-licensed mode check; it indicates that WinCC never reached the license-consumption phase.

FAQ