Loading

Java

Skip Feed
  1. InstallAnywhere 2026 LaunchAnywhere causes incorrect Java Swing DPI scaling

    We are testing migration of an existing Java Swing application from InstallAnywhere 2018 SP1 to InstallAnywhere 2026 R1.

    Environment:

    • Windows 11, high-DPI / multi-monitor setup
    • Java 11, 64-bit
    • Tested OpenLogic OpenJDK 11.0.31 / 11.0.32
    • Graphical LaunchAnywhere launcher

    With IA 2026, the installed application starts successfully, but the entire Swing UI is rendered significantly too small. Some dialogs become unusable because controls/buttons are clipped.

    I isolated the issue to LaunchAnywhere:

    • IA 2026 generated
    • .exe
    • → UI is too small
    • Same installed application, same bundled JRE, started directly with
    • java.exe
    • using equivalent classpath/system properties → scaling is correct
    • Running from Eclipse with the same Java version → scaling is correct
    • Application-specific
    • sun.java2d.uiScale
    • works when started directly with Java, but does not behave correctly through the IA 2026 launcher
    • Existing IA 2018 SP1 / Java 11.0.9 LaunchAnywhere launcher scales correctly

    I compared the LaunchAnywhere properties between the 2018 and converted 2026 projects and they are essentially identical.

    I also tested

    lax.highdpi.scaling.override.system=true

    and

    false

    ; neither resolved the issue.

    Ideally, we want LaunchAnywhere to leave DPI/scaling handling to Java/AWT, which works correctly when the application is started directly with

    java.exe

    .

    Is there a LaunchAnywhere DPI-awareness / Windows manifest setting in IA 2026 that controls this behavior? Has anyone encountered this?

    Expand Post

  2. InstallAnywhere 2018 Build 5868 – is this Base or SP1?

    We are using InstallAnywhere 2018 on Windows. Help → About shows:

    InstallAnywhere 2018 – Build 5868

    How can I confirm whether this is the original 2018 release or 2018 SP1?

    We are investigating because our existing Java 11.0.8/11.0.9 VM Packs work correctly, but VM Packs created with newer Java 11 versions (11.0.22 and 11.0.32) cause the generated installer to terminate during startup.

    I see InstallAnywhere 2018 SP1 available in our Product and License Center and understand that SP1 added Java 11 support.

    If Build 5868 is the original release, is it safe to install 2018 SP1 over it, or should it be installed separately?

    Thanks.

    Expand Post

  3. Title: FEKO 2022.1 InstallAnywhere launcher fails with “Windows error 2” on Windows 11 (Win11 26200)

    I’m trying to install Altair FEKO 2022.1 on Windows 11, but the installer consistently fails at launch with a “Windows error 2 occurred while loading the Java VM” / InstallAnywhere launcher failure.

    System details

    • OS: Windows 11 (Build 26200)
    • Java: Bundled OpenJDK 11.0.15 (Corretto 11)
    • FEKO installer size: ~2.87 GB (fully downloaded)
    • Running from local extracted folder (not network drive)
    • Virtualization-based Security (VBS): Enabled
    • App Control for Business: Enforced

     

    What I have tested so far

    The installer extracts successfully and contains all expected components:

    • InstallerData
    • folder is present and complete (~2.87 GB total package)
    • resource\jre\bin\java.exe
    • exists and runs correctly
    • InstallAnywhere launcher classes are present (com/zerog/lax etc.)

     

    Expand Post

  4. LaunchAnywhere Error: Windows error 2 occured while loading the Java VM

    After updating java version and creating new vm pack i am getting below error:

     

    LaunchAnywhere Error: Windows error 2 occured while loading the Java VM

     

    Already verified i have proper environemt variables for java_home and path

    Expand Post

End of Feed
5 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
6 Posts

Related Topics

    Loading
    Java