I am using Universal Extractor 1.6 beta with the current innounp pnpacker.

When attempting to extract some installers of Inno Setup type with Universal Extractor, the process halts and prompts:
How can Universal Extractor be made to finish the extraction?

The installers in question must be password protected to prevent extraction.

The extraction can only be finished if you enter the correct password.

Is there a way of working around the password protection or a way of acquiring the password when the password is not known?

Wouldn't that be illegal???

I do not believe so.

Those files are encrypted files. You have to use the password to actualy decrypt the file. I could use it for Nero Lite if I wanted it

A similar thread from another forum is similar to this one:

http://forums.winamp.com/printthread.php?threadid=293900

If the installer can continue its installation without prompting the user for a password, it should use the password itself during runtime. If the password is used during runtime it should be able to be captured.

I remember from a thread I read (although I do not remember where) that Inno Setup compares hashes, and the installer's hash or hash comparison can be modified to allow extraction to complete. I did not know how to actually accomplish such a thing.

I found the thread that seems to have found a way around the pssword protection (although I am still uncertain if it applies to installers that do not prompt for password during normal install process). The thread may be found:

http://forum.exetools.com/showthread.php?t=9137

What should be done to get around the password?

Ascii2, as the other forum members have noted, Inno Setup provides the ability to encrypt installers using the optional encryption module found here:
http://www.innosetup.com/isdl.php#crypt

In order to decrypt the installer (necessary for extraction), the proper password must be specified. By default, as you've obviously noticed, innounp can't support encrypted installers.

However, the post that you linked to looks like it may provide a way to work around it. I'd be interested in investigating it for the next version of UniExtract. I recommend adding your suggestion to the feature request thread to make sure I don't forget about it.

I have added the feature request to the MSFN Feature Request thread at http://www.msfn.org/board/Universal-Extrac...tu-t124535.html .

There is also another issue with UniExtract - it does not work with innounp 0.23.
Simply refuses to recognize the packer ...