InstallAware

Hello
A customer told me that he has problems with InstallAware Setup on some PCs.
The is a process net.exe and net1.exe which stopps the installer routine. When he kills the process in the taskmanager
the setup will proceed.
I have no idea what net.exe or net1.exe is, I do not use this in my MSI code
Is this an part of InstallAware?

Have you any idea?
regards
Hans

Dear Hans,

For what I know, the Net.exe Utility component is a command-line tool that controls users, groups, services, and network connections.

Doing a quick google search i found the following link, maybe you can found it useful.
http://forums.techguy.org/virus-other-malware-removal/698767-please-help-net-exe-net1.html

Hope this helps you.

Regards

Dear Francesco,
thank you.

What I want to know is:
InstallAware itself or some build in features do not use "net.exe" or "net1.exe?

Because I do not know why this is in the taskmanager while installing the software.
I do not call such a exe in my MSI code

Could it be that some plugins of InstallaWare do this?

regards
Hans

Dear Hans,

for sure an InstallAware package doesn't call those processes, if a third party plugin does the same ... honestly I don't know.

Of course, official IA plugins don't.

PS.
I suggest to you also to verify if any Antivirus software runs some strange process.

Regards

Just a quick guess: does the installer in any way involve any handling of services?

One common use for net.exe is to restart a service, for example:
net stop spooler
net start spooler

If the service has dependencies ("spooler" in this example) net.exe will prompt with a yes/no question and this will result in two instances of net.exe (one of the named "net1") showing up in taskmanager. If there is no console for I/O (hidden window for example) the process will hang.

If your installer somehow need to do something related to services a hanging net.exe might cause your installer to a hang.

The net.exe may be a result from a login script or something?

This is just a guess from my side. If it turns out to be something like this that causes your problem, make sure that whatever uses net stop/start uses the "/y"-switch.