Skip to main content

FAQ

1. How to Display in Fullscreen​

After opening the exe, there are several ways to enter fullscreen mode:

  • Press F11 to enter fullscreen
  • Press F11/ESC to exit fullscreen when in fullscreen mode
  • Check the "Fullscreen" option during packaging to automatically enter fullscreen at startup

2. Project File Loading Failure Issue​

Problem: Some files in the packaged project randomly fail to load

Solution: This issue is usually caused by the packaged project being too large, resulting in excessive decompression time after exe startup, causing browser file loading timeout. Recommendations:

  • Packaged files should not exceed 1GB
  • Use installer form for packaging
  • Check the "Improve Stability" option in advanced settings

3. Icon Creation​

Recommended Approach:

  • It's recommended to use png or jpg images as icons, the software will automatically process the images to ensure the icon can adapt to different sizes
  • If you need to use ico format, it's recommended that the icon resolution be 256256 and include multiple layers (128128, 6464, 3232, 16*16)

4. XP System Compatibility Issue​

Problem: When opening the exe on XP, a prompt "Invalid 32-bit application" appears

Solution: This is because the packaged exe does not support XP system. If you need to support XP, you can contact us for customization.

5. Kernel Selection Recommendations​

Choose the appropriate kernel based on different scenarios:

Chrome Kernel Applicable Scenarios:

  • Websites using newer H5/WebGL technologies
  • Need to maintain consistent display effects across different systems
  • Projects with high compatibility requirements

IE Kernel Applicable Scenarios:

  • Projects sensitive to package size
  • Simple static page display
  • Traditional web pages that don't require new features
  • Old web pages that need compatibility

6. Precautions for Packaging Large Files​

When packaging larger projects:

  • Use installer form instead of portable version
  • You can check the installer split package option
  • It's recommended to check the "Improve Stability" option in advanced settings
  • It's recommended to use Chrome kernel to improve stability

7. How to Protect Packaged Content​

To better protect packaged content, it's recommended to:

  • Check the "Disable Debugging" option to prevent the use of F12 debugging tools
  • Use the activation code feature in encryption settings
  • You can set usage count or day limits
  • It's recommended to use network verification feature

8. Performance Optimization Recommendations​

How to improve the running performance of packaged EXE:

  • Don't check unnecessary feature options
  • Compression options will affect startup speed, please choose according to your needs
  • You can use caching mechanism to improve loading speed

9. Cannot Close Program Properly After Clicking Close Button?​

Typical Symptoms​

  • No response when clicking the close button in the upper right corner / Need to click multiple times to exit
  • Window closes but process remains (visible in Task Manager)
  • Tray or resource usage still exists, logs not fully written to disk

Root Cause​

The most common reason is that the beforeunload event is registered in the page and intercepts the normal unload process through the following blocking statements:

window.addEventListener('beforeunload', function (e) {
    /*business logic*/
    e.preventDefault();
    e.returnValue = '';
    return '';
});

These statements tell the built-in browser "the page needs to prevent exit", causing the outer EXE close process to be delayed or blocked.

  1. If no forced prompt/confirmation is needed: Delete the three lines of code that block unloading (preventDefault / returnValue / return)
  2. If cleanup needs to be performed before exiting (save, report, release resources):
    • Keep the listener but remove blocking statements; only do very short synchronous operations
    • Or migrate to the onQuit API provided by the packaging tool
  3. Avoid executing long-running asynchronous tasks in beforeunload (may be forcibly terminated)
window.HTMLPackHelper.onQuit = () => {
    // Your business logic
    // return false: don't close the program after processing
    // return true: close the program after processing
    return true;
};