Hey there, let's tackle this frustrating Pentaho freezing issue you're dealing with—especially since it's popping up across both your personal machine and company server, and only affects versions 7.1+. Let's start with some troubleshooting steps you might have missed, then break down the key version differences that could be driving this behavior.

Missing Troubleshooting Checks #

Here are some angles you haven't covered yet that might uncover the root cause:

• Conflicting background tools/security software: Your hunch about app interception is spot-on. If your company allows it, temporarily disable EDR/antivirus tools (especially those monitoring Java processes) and try launching Spoon again. Also, check Task Manager for leftover Pentaho/Java processes—kill any stragglers before restarting spoon.bat. For the remote desktop server, verify if there are virtualization restrictions (like limited hardware acceleration for Swing apps) that might block newer Pentaho versions.
• Test with a clean user profile: Corrupted config files in your user directory can break newer Pentaho builds. Launch spoon.bat with the parameter:

  spoon.bat -Duser.home=C:\temp\pentaho-test-profile
  

  This uses a fresh, temporary profile—if Spoon works here, your original user config is the culprit.
• Windows system update rollback: Recent Windows KB patches can interfere with Java runtime behavior. Check if both machines had updates installed around the time the issue started, and try rolling back the most recent ones (if permitted) to test.
• Display scaling fixes: Pentaho 7.1+ updated its high-DPI screen support, which can cause freezing on 4K displays or systems with scaling >100%. Try adding this parameter to spoon.bat:

  -Dsun.java2d.dpiaware=false
  

  Or temporarily set Windows display scaling to 100% before launching Spoon.
• Verbose logging for deep debugging: Enable detailed logging to see exactly where Spoon is freezing. Modify spoon.bat to add these Java arguments:

  -verbose:gc -verbose:class -Dpentaho.logging.level=DEBUG
  

  Run Spoon again, then check the generated spoon.log and console output for errors like failed class loads, blocked GC cycles, or permission denials—this can pinpoint the exact bottleneck.
• Proxy and auto-update checks: Newer Pentaho versions automatically check for updates or attempt default repository connections on launch. If your company uses a proxy, add these parameters to spoon.bat:

  -Dhttp.proxyHost=your-proxy-server -Dhttp.proxyPort=your-proxy-port
  

  If you can't access Spoon's settings to disable auto-updates, edit the pentaho.xml config file (in your user's .pentaho folder) to turn off automatic update checks manually.

Key Differences Between Pentaho 7.0 & 7.1+ Versions #

The jump from 7.0 to 7.1 introduced several critical changes that could trigger your freezing issue:

• Swing UI engine upgrades: Pentaho 7.1 updated its underlying Swing components to a newer version, which includes improved rendering but can clash with outdated graphics drivers or remote desktop hardware acceleration. 7.0 used a more mature, stable (but outdated) Swing stack that's less likely to hit these compatibility snags.
• Stricter Java security policies: Newer versions enforce stricter JAR signature validation and security permissions by default. If any bundled or third-party Pentaho JARs have invalid signatures, or your system blocks certain Java permissions, this can cause UI loading to hang indefinitely. 7.0 had looser default security settings that avoided these blocks.
• Automatic repository connection attempts: Unlike 7.0 (which launched without trying to connect to a repository), 7.1+ automatically attempts to connect to a default repository on startup. If there's a network timeout, permission issue, or proxy block here, the UI will freeze while waiting for the connection to resolve.
• GC and memory management changes: Pentaho 7.1+ switched to G1GC as the default garbage collector (replacing 7.0's ParallelGC). While G1GC is more efficient for most cases, it can cause unexpected freezes on systems with limited memory or specific hardware configurations—even if you adjusted total memory allocations.
• Third-party dependency updates: The 7.1+ releases upgraded dozens of core libraries (Apache Commons, Spring, Hibernate, etc.). These newer library versions might conflict with existing system-level drivers or software installed on your company server, leading to runtime deadlocks.

内容的提问来源于stack exchange，提问作者Yuriy T.