Resolving LOGO! Soft Comfort V8.4 Silent Install Failure

David Krause14 min read
Other TopicSiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Resolving LOGO! Soft Comfort V8.4 Silent Install Failure

LOGO! Soft Comfort V8.4 (LSC V8.4) is the engineering software for the Siemens LOGO! 8 logic module family. Engineers frequently report that the V8.4 installer advances through the wizard up to the End User License Agreement (EULA), then closes silently without installing, logging an error, or generating a Windows Event log entry. This article documents the verified root cause, the licensing model that drives the failure, the supported mitigation paths, and the platform constraints you must satisfy before reinstalling.

Engineering notice: The failure described is not caused by a missing dependency on the host PC. The root cause is a licensing/install-mode mismatch: the publicly distributed package is an upgrade installer, not a full install. Attempting to apply it on a machine without a qualifying prior installation results in a silent, undocumented exit at the end of the wizard.

1. Problem Details

1.1 Symptom Signature

The defect presents with a deterministic signature that is highly recognizable in field reports:

  1. User launches LSC84.exe (or extracted MSI bootstrapper) from the Siemens download ZIP.
  2. Setup initializes, the splash screen renders, and the install wizard opens normally.
  3. The wizard advances through Welcome, License Agreement (EULA), User Information, and Setup Type.
  4. After accepting the EULA and clicking Next (or at the Install step), the wizard process exits.
  5. No error dialog, no MSI error code, no %TEMP% log file, and no Windows Installer event is recorded in Event Viewer → Application.
  6. Subsequent checks confirm that LSC V8.4 has not been added to Programs and Features; the installation directory (C:\Program Files\Siemens\LOGOComfort_V8.4 or the 64-bit equivalent) does not exist; the desktop shortcut and Start menu entries are absent.

1.2 Environment Footprint

The failure has been independently observed on at least two distinct host platforms per report, ruling out host-specific corruption. The typical affected environment is:

Component Reported Configuration Relevance
Operating system Windows 10 (1909–22H2), Windows 11 (21H2–23H2) Supported per LSC V8.4 release notes
Java Runtime Various (JRE 8uXX through JRE 11) Required by LOGO! Web Editor (LWE) bundled with LSC
Existing LSC None, or version 8.3.0 / 8.2.x / 8.1.x / 8.0.x Determines install path allowed
Acquisition ZIP from Siemens Industry Online Support (SIOS) Distribution channel determines package type
User account Local administrator Required for setup.exe elevation

1.3 Distinguishing the Failure

Three failure modes are commonly confused with this one. Confirm the symptom pattern before applying any remediation:

Failure Mode Exit Behavior Evidence Root Cause
V8.4 silent exit after EULA Wizard closes without dialog No MSI log, no Event Viewer entry, no installed files Upgrade-only package applied to non-qualifying host (this article)
MSI error 1603 / 1622 Wizard closes with a dialog MSI log in %TEMP%, Event Viewer MSI Installer entry 10403, 1013, 1015 Antivirus block, corrupted MSI cache, permission conflict
.NET Framework prerequisite failure Wizard closes early, before EULA Setup requires .NET 4.x dialog never appears Missing .NET Framework 4.7.2 or 4.8
JRE detection failure (LWE) Wizard completes; Web Editor feature missing LWE folder absent after install Java not on PATH or wrong architecture

2. Root Cause Analysis

2.1 Licensing Model: Upgrade vs. Full Install

Siemens distributes LSC V8.4 in two distinct SKU categories. The package the engineer downloaded from SIOS is, by design, a Service Pack / Upgrade installer intended to update an existing, licensed installation of an earlier LSC version on the same host. The installer performs a hard precondition check against the Windows Installer product code of an already-present LSC version.

When the precondition is not satisfied, the bootstrapper does not raise a user-facing error. It silently tears down the transactional install and returns to the desktop, leaving the user with no diagnostic trail. This behavior is consistent with the design intent of minimizing false-positive error reports for users who intentionally chain installers.

Official confirmation: Siemens Support has documented that V8.4 is published as an upgrade only. There is no separate public download for a full V8.4 install media; a full version must be purchased as boxed media or via a Siemens license portal. The V8.4 Demo is a separate SKU and runs with reduced functionality for evaluation.

2.2 Affected Versions and Builds

The V8.4 release track follows the convention 8.4.x, with the current SP being V8.4.1 as published in the firmware/service-pack bundle (SIOS entry ID 109975995). All 8.4.x packages behave identically with respect to the silent-exit symptom when applied to a host without a prior qualifying install:

Version Package Type on SIOS Target Host Standalone Install?
LSC V8.0 Full / Upgrade LOGO! 8 (6ED1052-x series) Yes (full media available)
LSC V8.1 Full / Upgrade LOGO! 8 Yes
LSC V8.2 Full / Upgrade LOGO! 8 Yes
LSC V8.3 Full / Upgrade LOGO! 8 (BM, TDE) Yes
LSC V8.4 (base) Upgrade only on SIOS LOGO! 8.4 (6ED1052-1xK08-0xA0, 6ED1055-0xK08) No (silent exit if no prior install)
LSC V8.4.1 (SP1) Upgrade only on SIOS LOGO! 8.4 No (silent exit if no prior install)
LSC V8.4 Demo Demo (SIOS 109826921) Any Windows host meeting prerequisites Yes — functional with restrictions

2.3 Why Java Is Not the Problem

The Java Runtime Environment (JRE) is a runtime requirement of the LOGO! Web Editor (LWE), which is bundled with LSC. The LWE is a Java Web Start application invoked from the LSC installation. LSC itself does not require Java for setup or for the core ladder/FBD editor. Installing Java will not change the silent-exit behavior, because the install is aborted before the LWE prerequisite check is reached.

2.4 Install-Time Prerequisite Stack

Before assuming a licensing mismatch, verify the host meets every prerequisite that LSC V8.4 enforces prior to the EULA step:

Prerequisite Minimum Recommended Validation
OS Windows 7 SP1 (32/64) Windows 10 21H2 / Windows 11 22H2 winver
.NET Framework 4.5 4.7.2 or later (4.8 on W10) regedit HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
Disk space 250 MB 500 MB Get-PSDrive C
RAM 1 GB 4 GB+ Task Manager
Display 1024×768 1920×1080 Settings → Display
Java (LWE only) JRE 8u201 JRE 8u401 / OpenJDK 11 LTS java -version
Browser (LWE only) Edge / Chrome / Firefox ESR Chrome 110+ —

3. Solution Paths

Three sanctioned paths recover a working V8.4 environment. Choose based on your licensing, hardware target, and intended use.

3.1 Path A — Install Prior Full Version, Then Upgrade to V8.4 (Recommended for Licensed Users)

This path matches Siemens' design intent and yields a clean, fully licensed V8.4 install with no demo restrictions.

  1. Obtain a prior full version. Acquire LSC V8.3 (or any earlier full version such as 8.2 / 8.1) on physical media from Siemens, or via the license portal if your organization holds a current license. The boxed DVD is the most reliable source; ISO images are sometimes available through your Siemens distributor.
  2. Pre-validate host. Confirm Windows 10/11 is fully patched; install .NET Framework 4.8 via Windows Update or the .NET 4.8 offline installer. Disable third-party antivirus temporarily during setup, as aggressive HIPS/real-time scanning has been observed to silently abort the LSC bootstrapper.
  3. Install the prior full version. Run the V8.3 setup as Administrator. Verify success by launching LSC and confirming Help → About reports the expected build.
  4. Close LSC and any background services. Terminate LogoComfort.exe, LogoComfortService.exe, and any Java processes in Task Manager.
  5. Apply the V8.4 upgrade. Extract the SIOS ZIP, right-click Setup.exe, and select Run as administrator. Accept the EULA. The upgrade should now complete and present a confirmation dialog at the end.
  6. Apply V8.4.1 SP1. If you require SP1 (recommended; includes bug fixes for TDE project transfer and the energy counter FB), run the upgrade package from SIOS entry 109975995 in the same manner.
  7. Re-enable antivirus and add an exclusion for C:\Program Files\Siemens\LOGOComfort_V8.4\ and C:\Users\<user>\AppData\Local\Siemens\.

3.2 Path B — Install LSC V8.4 Demo (Evaluation, Training, Lab Use)

The LOGO! Soft Comfort V8.4 Demo is a separately distributed evaluation package that installs on a clean host. It is appropriate for engineers building test programs, students, or anyone who needs to author and simulate LSC programs without a license. It is not appropriate for production deployment.

  1. Download the Demo ZIP from SIOS entry 109826921.
  2. Extract to a writable directory (avoid C:\Program Files\code> at this stage; use %USERPROFILE%\Downloads\LSC84_Demo\).
  3. Right-click Setup.exe → Run as administrator.
  4. Accept the EULA. The Demo setup does not perform the upgrade-precondition check, so it completes successfully on a clean host.
  5. Launch LSC. Help → About will identify the build as LOGO!Soft Comfort V8.4 Demo with a 30-day evaluation banner and the following functional restrictions:
    • Print and PDF export watermarked
    • Project save uses a non-proprietary format
    • No online connection to LOGO! hardware for program transfer (offline simulation only)
    • No code export to SD card via LSC

3.3 Path C — Migrate to LSC V9 (Long-Term Recommendation)

For new deployments, especially those targeting the LOGO! 8.3 / 8.4 (6ED1052-1xK08 and 6ED1055-0xK08) BM modules and the LOGO! CMR (6GK7142) communication variants, LSC V9 is the current shipping version. V9 introduced support for the LOGO! 8.3 (FS:05) hardware, expanded cloud connectivity, and the updated LOGO! Web Editor V2. Projects created in V8.x are forward-compatible with V9 with one caveat: UDFs (User-Defined Functions) and some library macros from V8.4 are silently upgraded and may require manual re-validation in V9.

  1. Verify hardware compatibility on the Siemens LOGO! product page. LOGO! 8 BM units with FS:04 and earlier require an upgrade to FS:05 to interoperate with LSC V9.
  2. Download the LSC V9 installer (available as both full media and a functional trial on SIOS).
  3. Install side-by-side with V8.4 if needed for project migration; LSC supports parallel installations in C:\Program Files\Siemens\LOGOComfort_V9\ and ...\LOGOComfort_V8.4\.
  4. Open each V8.4 project in V9, validate the FBD, and re-link any custom UDFs.

4. Verification

After applying any path, run the following verification sequence to confirm the install is healthy and the runtime can communicate with the LOGO! hardware you intend to program.

  1. Filesystem check. Confirm C:\Program Files\Siemens\LOGOComfort_V8.4\LogoComfort.exe exists and reports a version of 8.4.x.x in file properties → Details.
  2. Service registration. Open services.msc and verify the Siemens LOGO! Soft Comfort Service is present and set to Manual (the service starts on demand when a connection to a LOGO! device is opened).
  3. Program launch. Launch LSC, choose File → New, and place a simple FBD (e.g., a digital input → counter → output). The simulation (Tools → Simulate) should activate without a license prompt for unlicensed users in Demo mode.
  4. Web Editor check (optional). From LSC, choose Tools → Connect to LOGO! Web Editor. If a Java dialog appears requesting permission, your JRE installation is correctly recognized. If the Web Editor fails to launch, re-check java -version and ensure a 32-bit JRE is present if you installed LSC as 32-bit.
  5. Hardware connection (if licensed). Connect a LOGO! 8.4 BM (6ED1052-1xK08-0xA0 or later) via Ethernet. In LSC, choose Tools → Ethernet → Connect and enter the device IP. The transfer should complete within ~5 seconds for a small program.
  6. Log file check. Inspect C:\Users\<user>\AppData\Local\Siemens\LOGOComfort_V8.4\Logs\ for any error entries on startup. A clean install produces a single INFO entry on first launch.

5. Diagnostic Matrix: Symptom → Action

Observed Symptom Likely Cause Diagnostic Action
Wizard closes silently after EULA, no log Upgrade installer on a clean host Check Programs and Features for any prior LSC Use Path A (install prior version) or Path B (Demo)
Wizard reports MSI 1603 / 1622 AV block, permission, MSI corruption %TEMP%\Logo*.log, Event Viewer → Application Disable AV, clear %TEMP%, re-run as Admin
Wizard aborts before EULA with .NET dialog Missing .NET 4.x Check regedit for NDP\v4\Full Install .NET 4.8 offline, reboot, retry
Install completes; LSC crashes on launch Incomplete prior upgrade, file lock Windows Application event 1000 / .NET Runtime 1026 Uninstall all LSC versions, clean AppData\Local\Siemens, reinstall from Path A
Install OK; Web Editor cannot find Java Wrong-arch JRE or no JRE java -version Install 64-bit JRE 8u401 (for 64-bit LSC) or 32-bit JRE 8u401 (for 32-bit LSC)
Demo runs; cannot transfer to LOGO! Demo restriction Help → About reports Demo Acquire a full license and install via Path A
V8.4 transfer to LOGO! 8.3 FS:05 fails with error 0xE0010007 Version mismatch LSC Help → About vs BM firmware Update BM firmware to V8.4.1, or downgrade LSC to V8.3 if hardware is locked
V8.4 installed on Windows 11 24H2 hangs at splash Compatibility flag missing Task Manager shows LSC not responding Set compatibility to Windows 10 in EXE properties, disable Core Isolation

6. Hardware Compatibility Reference (LOGO! 8.4 Target Devices)

The V8.4 software release aligns with the LOGO! 8.4 (FS:05) hardware. Confirm your BM or TDE module order number is supported before deploying V8.4 projects:

Module Order Number (MLFB) Minimum FW Recommended FW Notes
LOGO! 8.4 BM 24CE 6ED1052-1CC08-0BA0 V8.4.0 V8.4.1 24 V DC supply, 8 DI / 4 DO (relay), Ethernet
LOGO! 8.4 BM 230RCE 6ED1052-1MD08-0BA0 V8.4.0 V8.4.1 115/230 V AC supply, 8 DI / 4 DO (relay), Ethernet
LOGO! 8.4 BM 12/24RCE 6ED1052-1MD08-0BA0 V8.4.0 V8.4.1 12/24 V DC, 8 DI / 4 DO (relay)
LOGO! 8.4 TDE 6ED1055-0MH08-0BA0 V8.4.0 V8.4.1 Text Display, Ethernet
LOGO! CMR2020 6GK7142-7BX00-0AX0 FW 1.5+ FW 2.1+ 4G/GPS router, V8.4 supports SMS relay FB
LOGO! 8.3 (FS:04) BM 6ED1052-1xK07-0xA0 Older V8.3 compatible Use LSC V8.3 if hardware not upgradeable

7. Best Practices to Avoid a Recurrence

  1. Document the install chain. Maintain a README in your engineering share that records the exact LSC version, the hardware FS level, and the date of the last successful transfer.
  2. Preserve offline installers. Store the V8.3 full media (or ISO) on a write-protected network share. The V8.4 upgrade will be unusable without it.
  3. Check SIOS frequently. Subscribe to the LOGO! Product Support RSS or the Siemens Industry Online Support notification for the firmware/service-pack bundle (entry 109975995 for V8.4.1).
  4. Standardize Java. For machine builders deploying multiple PCs, deploy a single JRE version (recommended: 8u401 or 11.0.22 LTS) via Group Policy. Mixing JRE 8 and 11 on the same image can break LWE.
  5. Antivirus exclusion list. Add the LSC install and data paths to your endpoint protection policy. Real-time scanning of the AppData\Local\Siemens tree causes intermittent transfer errors with BM firmware V8.4.x.
  6. Document the license portal credentials. If you purchase through the Siemens license portal, store the activation keys in your organization's password vault. Lost keys cannot be re-issued without a re-purchase.

8. When to Open a Siemens Support Request

If Path A or Path B fails after exhausting the diagnostic matrix, open a ticket via the Siemens Industry Online Support portal. Provide:

  • Product tree selection: Automation Technology → Industrial controls → LOGO! Logic module → LOGO! 8 → LOGO! Soft Comfort
  • Exact build of the installer ZIP (filename, size, SHA-256 if available)
  • Output of msinfo32 (System Summary → OS Name, OS Version, System Manufacturer, System Model)
  • Output of reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release
  • Any logs captured by setting Logging in C:\Users\<user>\AppData\Local\Siemens\LOGOComfort_V8.4\LogoComfort.ini to verbosity=4 before re-running setup
Support response time: Siemens treats LOGO! support as a standard-bus product, not a premium one. Expect initial human response within 1–3 business days. Severity 1 (production stoppage due to inability to commission) is not formally recognized for LOGO! — set expectations with management accordingly.

9. Related Siemens References

FAQ

Why does the LOGO! Soft Comfort V8.4 installer close silently after the EULA?

The V8.4 package distributed on Siemens Industry Online Support is an upgrade installer. It performs an internal precondition check for an existing prior LSC install. If no qualifying version is detected, the bootstrapper terminates the install silently with no dialog and no MSI log. Install a prior full version first, or use the V8.4 Demo package for evaluation.

Where can I download a full standalone LOGO! Soft Comfort V8.4 install?

Siemens does not publish a public download for a full V8.4 install. Purchase a full license and obtain the installer on physical media (DVD) from your Siemens distributor or via the Siemens license portal. Alternatively, download the V8.4 Demo (SIOS 109826921) for evaluation; it installs on a clean host with functional restrictions.

Does LOGO! Soft Comfort V8.4 require Java?

Java is required only for the bundled LOGO! Web Editor (LWE) component. The core LSC FBD editor and online transfer to LOGO! hardware do not use Java. If you do not need LWE, Java can be omitted; however, installing JRE 8u401 (or OpenJDK 11 LTS) on the host is the supported configuration and prevents LWE feature degradation.

Can I run LSC V8.3 and LSC V8.4 side-by-side?

Yes. LSC supports parallel installation of different major/minor versions. LSC V8.3 installs to C:\Program Files\Siemens\LOGOComfort_V8.3\ and V8.4 to ...\LOGOComfort_V8.4\. Each maintains its own service registration and project file association. You can pin file types per version if needed via File → Properties → Open With.

Should I upgrade to LOGO! Soft Comfort V9 instead of V8.4?

If your hardware is the LOGO! 8.3 FS:05 BM (6ED1052-1xK08-0xA0) or the LOGO! CMR 6GK7142 series, V9 is recommended and adds the LOGO! Web Editor V2 with cloud integration. V8.4 remains the stable target for LOGO! 8.4 FS:04 deployments and is a sufficient engineering environment for most current installations. For new projects, default to V9.

Back to blog