2.0.0.353

• Added Application_Trace_Results.log as a short, plain-language Trace report with
  separate Failures, Warnings and Passes sections and one-line explanations for each
  captured application target. Trace now opens this report first while retaining the
  detailed Application_Portability_Report.log and Application_Trace_Summary.log.
• Corrected the plain-language Trace report so Windows-blocked write-capable requests
  are short WARN entries rather than portability FAIL entries. Their operation, result,
  process and target are shown; FAIL is reserved for X-Launcher configuration or
  runtime failures, including the related INI section and key when available.
• Changed plain-language Trace PASS entries to show the most specific matching INI
  setting, including automatic Options, Environment paths, Junctions and general
  FileSystem roots. Removed the launcher-action target count from the simple report;
  launcher-only activity remains available in the advanced report.
• Separated blocked write attempts from the plain-language Trace warning count and
  labelled them BLOCKED instead of WARN. Repetitive access-denied targets in the
  Windows DriverStore are condensed into one summary while the advanced report
  retains every individual target.
• Excluded Windows-managed NTFS volume metadata such as C:$LogFile from the
  plain-language Trace portability warnings while retaining it in a dedicated
  advanced-report section for diagnostic evidence.
• Added generic Trace classifications for Windows-owned system changes and
  clustered installer or driver-package staging. The simple report condenses
  these separately from portability warnings, while the advanced report retains
  every individual target. No application or process names are hardcoded.
• Kept every unmanaged registry write in Trace WARNINGS. Generic SYSTEM
  classification now applies only to Windows-owned files/folders and installer
  staging, so registry activity is never hidden solely because of its path.

v2.0.0.346

It should be fine to use as it is fully backwards compatible with existing setups. Please make a backup or use a copy of your portable app before using this version of the launcher.
There is only one breaking change:

• MultipleIstances was a typo in the INI and in the source code, this has been corrected, but without supporting the typo, so any older config's require an alteration to correct the typo within the INI file. You MUST now use MultipleInstances.

Other than that, everything else should work exactly as before, but hopefully without the previous issues that plagued the last release.

Here is a shortlist of additions and changes:

X-Launcher64 v2.0.0.346 - Changes since v1.5.7.20

• Updated X-Launcher to a modern native 64-bit build for Windows 8 and later.
• Improved application launching, process detection, shutdown handling and exit-code reporting.
• Corrected RunWait and RunAfter behaviour, including RunAfterStopOnFailure.
• Added safer file and folder operations, wildcard handling, path validation and temporary-folder deletion.
• Improved portable profile handling and support for localized Windows shell-folder names.
• Added FixLocalAppData and FixTemp for easier portable environment configuration.
• Corrected Configuration Probe environment-name validation so standard names such as PROGRAMFILES(x86), names with spaces and custom variables are accepted; only Windows-invalid names receive a specific reason.
• Corrected normal log output so FixAppData records the full portable APPDATA path instead of only its folder name.
• Clarified Configuration Probe reporting for recursive DirRemove, empty-only |e and invalid |o usage without changing runtime deletion behaviour.
• Changed Configuration Probe to report an already-absent DirRemove target as NOT USED instead of FAIL in Functions, FirstRunOperations and RunAfter; missing copy and move sources remain failures.
• Added protected Lib cleanup modes: |e removes empty descendants while preserving Lib, and a trailing separator removes contents while preserving the target; direct removal of Lib, Bin, Root and other protected paths remains blocked.
• Reworked registry portability, restoration, recovery and registry-view selection.
• Modernized Java runtime discovery and optional download handling.
• Added Configuration Probe, Application Trace and isolated Full Test diagnostics.
• Changed Configuration Probe report filenames to use the .log extension.
• Added optional Process Monitor capture and clearer diagnostic and portability reports.
• Improved configuration-file rewriting while preserving supported encodings and line endings.
• Corrected the MultipleInstances setting name.
• Restored automatic splash-image sizing and corrected splash, tray and language behaviour.
• Modernized x64 Windows API calls, build metadata and the regression test suite.
• Added optional junction and symbolic-link creation with safe automatic cleanup or an explicit persistent * flag.
• Changed Configuration Probe, Full Test, Application Trace, and regression-suite
  result label/value separators from colon to equals for consistent diagnostic output.
• Changed every X-Launcher-generated readable diagnostic report from .txt to .log:
  Application Trace Summary, Application Portability Report, and Full Test Report.
• Changed completed native Trace runs to open Application_Portability_Report.log;
  Application_Trace_Summary.log remains the fallback when analysis is unavailable.
• Changed remaining Application Portability Report fields from colon separators to
  key= value formatting for clearer syntax highlighting and scanning.
• Changed Debug=true .dbg line prefixes from timestamp : message to
  timestamp = message for consistent key-value syntax highlighting.
• Refined visible portability-report keys to Application Root PID, Launcher Root PID,
  ParentPID, CommandLine and INIcoverage while retaining Process Monitor's original
  internal Parent PID and Command line detail-field names for compatibility.
• Manual completely reworked.

1.5.7.20

Updated the original X-Launcher source code to 64bit.
The only changes made were format and a slight adjustment to the Splash so you can tell the difference between the old 32bit and new 64bit versions.

Here's some previous history:

• 05.08.2025 - Updated: v 1.5.7.14:
  Changed Splash Screen slightly. Just so you know you are using the x64 version.

• 06.08.2025 - Update: v 1.5.7.15:
  Fixed - Previous version was compiled with UPX enabled. Doing so disables the ability to use tools like ResourceHacker to change the icon with AutoIT compiled EXE's.

• 06.08.2025 - Update: v 1.5.7.20:
  Fixed - SplashScreen Timeout wasn't being read from INI file.