What you're seeing at the end is the program "unpack200" unpacking LimeWire's jar files. We build the installer with highly compressed files that allow the installer size to be a half of what it used to be. Unpack200 is somewhat resource and CPU intensive, so it may appear as if things have stalled while it is unpacking the files.

If you go to the directory C:\Program Files\LimeWire while LimeWire is installing, you'll see it initially places a bunch of "<name>.jar.gz" files, and during the "Finishing installation" phase, these get erased and turned into "<name>.jar" files.

Does the installer stall for you after all the files have been converted from .gz to .jar, or during that process? Also, does the progressbar in the 'Finishing Installation' ever move forward?

We'd like to solve any problems with the new installer. Thanks very much for letting us know about this. Any help you can give would be great.