DialogOS安装失败（错误代码20）技术求助

I’ve run into this exact unpacking issue before with Java-based installers and newer JDK versions—let’s get this sorted out for you.

First, let’s break down what’s going wrong from your log:

[0:777] could not create unpack process

The root cause here is that JDK 15 no longer includes the unpack200.exe tool that DialogOS’s installer relies on to unpack its runtime JAR. This tool was deprecated in JDK 11 and removed entirely in JDK 14, so the installer can’t find it to create the unpack process.

Here are the most reliable fixes, ordered by ease of use:

1. Switch to a Compatible JDK Version (Recommended) #

The simplest fix is to use a JDK version that still includes unpack200.exe. LTS versions like JDK 8 or JDK 11 work perfectly here.

• Grab a free, open-source build (you don’t need to uninstall your JDK 15—we’ll just temporarily set the default)
• Open Command Prompt as Administrator, then run these commands to set the JDK path:

  setx JAVA_HOME "C:\Path\To\Your\Downloaded\JDK"
  setx PATH "%JAVA_HOME%\bin;%PATH%"
  

• Restart your computer, then launch the DialogOS installer again. This should let the installer find the unpack200.exe it needs.

2. Manually Unpack the Runtime JAR (Advanced) #

If you don’t want to switch JDK versions, you can handle the unpacking yourself:

• From your log, navigate to the temp folder: C:\Users\verag\AppData\Local\Temp\e4jC3AB.tmp_dir1604922288
• Copy the i4jruntime.jar.pack file to a machine that has JDK 8/11 installed
• On that machine, open Command Prompt, navigate to the file’s location, and run:

  unpack200.exe -r "i4jruntime.jar.pack" "i4jruntime.jar"
  

• Copy the newly created i4jruntime.jar back to the temp folder, replacing the packed file. Then resume or restart the DialogOS installer.

3. Run the Installer as Administrator #

Occasionally, permission restrictions can block the installer from creating processes. Right-click the DialogOS installer executable, select Run as administrator, and try installing again. This might resolve the issue if permissions were the problem instead of the JDK version.

If none of these fixes work, share the full log file from C:\Users\verag\AppData\Local\Temp\i4j_nlog_12.log and I’ll help you dig deeper.

内容的提问来源于stack exchange，提问作者vera