#StackBounty: #java #windows #launch4j #winrar #izpack Unable to run self-extracting installer – Unable to access jarfile C:UsersRay…

Bounty: 100

I have a Java application, the Izpack installer is wrapped with launch4j64bit and then bundled as a self-extracting ZIP, created with WinRAR 5.20 using a method as described in an answer on How do I make a self extract and running installer?

It works, for me and most customers, but recently a few customers have reported errors like this:

Unable to access jarfile C:UsersRayAppDataLocalTempRarSFX0install.jar

I am unable to reproduce this error.

What could be causing this problem? Is it related to a Windows updates?

There is a only a problem with self-extracting version, a regular .zip file that users have to extract themselves works fine.

When I run the self-extracting archive it self-extracts correctly. So we have this folder structure:

  • a folder JVM64,
  • a file install.jar,
  • a file setup.exe and
  • a file setup.ico.

But for users having a problem it only extracts JVM64:

 Volume in drive C has no label.
 Volume Serial Number is A663-4CEF

 Directory of C:UsersgcdrAppDataLocalTemp

14/08/2018  21:40    <DIR>          .
14/08/2018  21:40    <DIR>          ..
14/08/2018  21:40    <DIR>          RarSFX0
               0 File(s)              0 bytes

 Directory of C:UsersgcdrAppDataLocalTempRarSFX0

14/08/2018  21:40    <DIR>          .
14/08/2018  21:40    <DIR>          ..
14/08/2018  21:40    <DIR>          JVM64
               0 File(s)              0 bytes

I found for one user that disabling Norton AntiVirus allowed installation.
Now I use to submit each new version to Norton whitelist, but that option has gone.

Why could this be? Could there be some restriction with files called install.jar?


Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.