Hi All, Does anyone know of any way to decrypt/decompile an installer? I built an installer with Installshield.

1. Installshield 6 7 Script Decompiler
2. Installshield Installation Information Delete

I used 7-zip to extract the contents, but the only.DLL or.EXE I see in the contents appears to be an icon resource ('Icon.853F67D50E7E.exe'). When I try to decompile it in ILSpy I get this diagnostic: 'This file does not contain a managed assembly.' The rest of the files do not seem to have extensions. Aug 04, 2013  sid - installshield 6/7 script decompiler v1.0 written by sn00pee introduction-sid is designed to decompile installshield.inx scripts created with installshield 6 or 7. Additionally it allows the user to take a few changes to the code and patch the script. Features: - decompiles every.inx script file - automatically detects IS standard.

By accident, I deleted all the source for the installer. Not sure if there's any tool that could reverse back the whole directory? I can unzip the Data1.cab file, but I could only get to some of the files, and some are still encrypted. Plus I lost all the custom actions. I still need to reuse the installer files and structure for future installer.

So I don't have to build everything again. I don't need source code, because I have that backed up, but I want all the dll, exe, custom actions, windows components (with the right version), also the structure of the ism file. Any suggestions? Thanks in advance!!

Contents. About Currently NSIS installers cannot be fully decompiled. The installer itself doesn't provide any method to extract files or the script without installation. It is the developer's choice whether the source code and/or the files for the installer are available to the public or not. Extraction Tools There are, however, external tools that allow this:.

Since version 4.42may 2006 supports decompressing NSIS installers. Since version 9.34 Jun 2014 7-zip is also able to extract the compiled scriptcode.

Installshield 6 7 Script Decompiler

The decompression plug-in InstallExplorer is also available for TotalCommander. Beside the files it'll create the file 'script.bin' compiled scriptcode.For use without the TotalCommander the is a good option. Well since Feb 2014 InstExpl suffers from problems naming file names and dirs correctly that were created with NSIS 3. That's because the implementation was slightly changed so names like $INSTDIR, $PROGRAMFILE. Inside strings are not expanded correctly. Decompilers. Since version 9.34 Jun 2014 it'll extract.beside the files of the setup.

the compiled script code to a file named NSIS.nsi. or NSIDis NSIDis is a open source Python script that'll help you to nearly fully recover your NSIS-installation scripts. Its state is currently alpha - and so not very user friendly and stable.

NRS is a set of Python librairies used to unpack and analysis NSIS installer's data. It also has an IDA plugin used to disassembly the NSIS Script of an installer. Protection against Decompilers As a general note to software developers, you should use a plugin like if you need to protect certain files in your installer. Or if ya in the mood for compiling the NSIS have a look into nsis-3.xx-src Source exehead fileform.h.

Mixing up the order of the enum with all the EW. a little bit as recommend in the Comment. It will mess up decompilers output that expect these tokes to be in the standard order. Or shift or enlarge the.reloc section in the PE-header by 0x400. = 7) operators changed because the old 7 ( bneg) is implemented using ^.

Installshield Installation Information Delete

3.03 r6926 Added (SHR) operator (parm3 13) EWSETFLAG. 3.02 r6841 alterregview can be KEYWOW6432KEY in 64-bit stubs. EWSHELLEXEC.

3.02 r6839 Parameter count changed. Parm4 is SHELLEXECUTEINFO.fMask and SEEMASKNOCLOSEPROCESS is set for ExecShellWait.

EWDELREG. 3.02 r6871 ent.offsets4 can also contain (shifted) KEYWOW64xxKEY bits. EWWRITEREG. 3.02 r6829 ent.offsets5 is REGMULTISZ for WriteRegMultiStr.