This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Error installing the wireshark2.2.5 installer from NSIS

0

alt text

Im using a 64bit Machine but im not able to install

asked 07 Apr '17, 03:53

DhanuShalz's gravatar image

DhanuShalz
36101115
accept rate: 100%

Did you verify that the operating system is 64bit as well? Maybe you're running a 32bit OS on 64bit hardware...

(07 Apr '17, 03:56) Jasper ♦♦

alt text

(07 Apr '17, 04:12) DhanuShalz

Is this an official release version or your own built installer?

(07 Apr '17, 04:26) grahamb ♦

my own built installer

(07 Apr '17, 04:28) DhanuShalz

Can you try with the release version?

(07 Apr '17, 05:50) grahamb ♦

i downloaded the 2.2.5 installer and i was able to install it!

but the installer one which i have built im not able to install!

(07 Apr '17, 06:11) DhanuShalz

As you have seemingly managed to build Wireshark is there any chance you can go back to your 3 "open" Wireshark 2.2.x questions (here, here and here) and mark the answers which have helped you as "Accepted" by clicking the checkmark icon by the appropriate answer.

This helps others to see which answer solved the question.

(07 Apr '17, 06:41) grahamb ♦

sure i would that

(07 Apr '17, 06:43) DhanuShalz
showing 5 of 8 show 3 more comments

One Answer:

0

It would appear that you've broken something when creating your own installer.

For a 64 bit build of Wireshark the NSIS installer checks the running platform with the code in packaging\nsis\x64.nsh.

There haven't been any reported issues with this x64 detection and it's running in the release version that does work, so somehow you've built an installer that is unable to correctly detect it's running on an x64 platform.

Did you build the installer from the same build command prompt with the same environment variable settings as used for the build?

answered 07 Apr '17, 06:37

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

yeah, built from the same command prompt and the same environment variables were used! @grahamb

(07 Apr '17, 06:46) DhanuShalz

NSIS version?

(07 Apr '17, 07:46) grahamb ♦

upgrading NSIS to latest version resolved my issue! @grahamb

(13 Apr '17, 08:13) DhanuShalz