NSIS 3.01 Built Installer Crashes When Running Installer

Hi,

I have a client with the following hardware setup:

Windows 10 Education Edition
Intel i5-3450 cpu 3501 MHz 4 core
16GB Memory
AMI f10 bios

The nsis installer I have built will run for approximately 1-2 seconds then just terminate without any error/warning message. I have checked both the application and system event log but nothing logged to indicate the cause. I have confirmed the client is running the installer as an administrator and sufficient space is available on the hard drive to install the application.

I have identified the line in the installer script that appears to cause the unexpected termination of the installer:

File /r ".\Application\*.*"

I have run the install on my pc and a number of others without any problems. I guess the installer is terminating because of an exception is there any way I can capture the exception in the script to log the cause and hopefully get to a fix?

Are you setting the output directory first? (http://nsis.sourceforge.net/Docs/Cha...tml#setoutpath). When a file command fails, usually it's because it can't write to that location (permissions or policies). What's the output directory? Also, this one or two seconds before it's closing, are you just doubleclicking the installer and touching nothing and it crashes one to two seconds later, or is it when it starts the install (entering the instFiles page)?

Usually hardware doesn't matter because NSIS is a full software based program (as opposed to using hardware accelerated code).

The crash happens once the installer starts to copy files, the output path is

c:\program files (x84)\RobApp\

The strange thing is that some of the files are copied over.

Are you sure "program files (x84)" is the correct name of the folder? You should be using $PROGRAMFILES.

Perhaps this is an anti-virus program terminating the installer because of its behaviour.

Sorry I gave the literal path string yes I'm using $PROGRAMFILES

My guess is that some AV/security software has injected into the process. You could try running Process Monitor and look at the stack of the last few events before the crash. It should go: your.exe > kernel32 > ntdll > ntoskrnl for the file operations.

Originally Posted by Anders View Post

My guess is that some AV/security software has injected into the process. You could try running Process Monitor and look at the stack of the last few events before the crash. It should go: your.exe > kernel32 > ntdll > ntoskrnl for the file operations.

Thanks I will give that a go.