Installer problem?

I am using Windows Server 2016, and this problem has been for a while for each new build of Elements installer: always complaining that unzip.exe has stopped working, towards the end of the installation process.

Any heads up?

Weird. I never have seen this, or had anyone else report it. If you Choose “Debug”, do you get any indication of why its crashing? I don’t even think we use unzip.exe (but maybe InnoSetup does, internally…)

From Windows Event View, I found this:

Application: unzip.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at System.IO.__Error.WinIOError(Int32, System.String) at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean) at System.IO.FileStream…ctor(System.String, System.IO.FileMode, System.IO.FileAccess) at System.IO.Compression.ZipStorer.Open(System.String, System.IO.FileAccess) at Unzip.Program.Main(System.String[])

I found the cause of the problem: it happens, when the following two options are UNCHECKED:

  • Cocoa platform support
  • Java platform support

I don’t use Cocoa and Java - so I unchecked them to save disk spaces, which lead to the reported problem above.


1 Like

Hmm. can you get the command line for unzip.exe, from task Manager? I domino see how unchecking these could cause this — but 'll also try, here.

Doesn’t repro here, even with those two unchecked :frowning:

Here is what I did to replicate the problem:

  1. Uncheck Cocoa platform support, and uncheck Java platform support.
  2. Run the installer (, Windows Server 2016

The problem happens at the step “Registering Remobjects Oxygene and Silver CodeDom”, and the missing file being complained is “Remobjects.Elements.Templates.Toffee.vsix”.

Hope this helps.

Logged as bugs://E25176.

bugs://E25176 was closed as fixed.

Since we couldn’t reproduce this, and just applied a blind fix, id appreciate of you can let me know if this is fixed in 2653 for you, come Friday. thanx! :pray:t3:

Thank you for the update. Will try.

1 Like

I confirmed that 2653 fixed this.

:raised_hands:t3: thanx!