KNIME Analytics Platform 5.12 on Windows 11 closes after selecting workspace — same executable wo...

Hello,

I am using KNIME Analytics Platform 5.12.0 (LTS, build v202606180846) on Windows 11 Pro.

Problem: When I launch KNIME normally from the Windows Start menu and select an existing workspace, the application appears briefly and then closes without a visible error message. I need to regain reliable access without losing existing workflows, settings or saved execution results.

What we have established:

  • The KNIME executable is signed by KNIME AG and runs successfully in controlled tests; its file contents have not changed.

  • Using the same executable with a dedicated launcher ini, fresh private Eclipse -configuration, private -data workspace and -consoleLog, KNIME starts successfully.

  • In a further controlled test, KNIME opened a private copy of an already-saved workflow and displayed its cached result. It closed normally. No nodes were executed, reset or saved.

  • Available KNIME logs and Windows Reliability Monitor information have not revealed a clear fatal error explaining the ordinary launch failure. The relevant Eclipse .metadata/.log was not available for that failed launch.

  • Static comparisons identified differences in dynamic Eclipse configuration, user home and temporary directories. No cause or corruption has been demonstrated. The exact effective Start-menu launch parameters remain unknown.

Could you recommend the shortest safe way to diagnose and restore normal launching?

  1. Which startup arguments, environment details or Eclipse/KNIME logs should we capture to distinguish workspace, profile/configuration and installation issues?

  2. Is there a non-destructive way to rebuild startup configuration without deleting the original .metadata, workflows or saved outputs?

  3. Would extracting a clean KNIME 5.12.0 Windows ZIP into a separate directory and testing it with a fresh workspace be an appropriate next step?

We can provide redacted startup commands and relevant log excerpts if useful, but cannot share the underlying private workflows or data.

Thank you.