What am i doing wrong in terms of extraction of Inno-based setup archive?

[anderlli0053]

Hello!

I've a manifest request to fulfill; I need to download This EXE setup and extract it.. I have scanned it with Universal Extractor 2, which also says that the EXE is INNO SETUP MODULE:

------------------ Exeinfo PE ------------------

Inno Setup Module 5 SFX - [ v.(5.5.7) [ 5.5.9 Unicode ]  ] - Delphi 2009 - www.innosetup.com - *Mode : Lzma

try InnoExtractor v5.3 GUI ( 2018 ) - www.havysoft.cl - or -
    Inno Setup Unpacker v0.49 -> http://innounp.sourceforge.net

------------------ PEiD (ext) ------------------

Nothing found [Overlay] *

----------------- PEiD (hard) -----------------

Borland Delphi 6.0 - 7.0 [Overlay]

--------------------- TrID ---------------------

 30.8% (.EXE) Win32 Executable (generic) (4508/7/1)
 14.1% (.EXE) Win16/32 Executable Delphi generic (2072/23)

---------------- Unix File Tool ----------------

PE32 executable for MS Windows (GUI) Intel 80386 32-bit

------------------ MediaInfo ------------------


[General]
Format                  MZ
Format profile          Executable / Intel i386
File size               368 MiB
Encoded date            UTC 2016-04-06 14:39:04

I have tried with innounp tool and it sucessfully extracted the archive with the following command innounp.exe "iFinD_Setup_v1.10.12.384.001.exe" -x -dTESTEXTRACTDIRECTORY and the executables run after the extraction, but while i am trying to do the same in Scoop with something like this:

"Expand-InnoArchive \"$dir\\iFinD_Setup_v1.10.12.384.001.exe\" -Removal",
"Remove-Item \"$dir\\*,*\" -Force"

It literally "extracts" the EXE into its segments, like .bss , .data, .idata , .itext , [0], ..... Which of course is not right.. and even less usable in its state of segments...

I don't understand what am i doing wrong? Is there alternative method in Scoop? It is surely INNO Setup, because it extract like normal with manual innounp command, written above and the UniversalExtractor reports it as such...

[anderlli0053]

Nevermind.. I've actually figured it out myself after spending all afternoon, when i came back from work.... I forgot to set/write the "innosetup": true in the manifest.. then it worked perfectly...