The Installer Is Already Running.

[ViperGeek]

Environment: Windows 7 64-bit running on an Intel platform (Lenovo ThinkPad T400).

 

Earlier this week, I got a friendly notice that the Immunet 3.0.8 update was available. Like a good user, I immediately double-clicked the toolbar icon and selected Update. The latest update downloaded, passed validation, then began to install. Almost instantly, I received a pop-up stating "The installer is already running.":

 

 

I checked all tasks and processes running on the system, but found no Immunet installers. So I rebooted. Same error. I then decided to take the strong arm approach and uninstall Immunet 3.0.5 completely. After rebooting, I tried installing from a freshly downloaded installer. Same error.

 

I tried attaching my immpro_install.log, but the forum doesn't permit uploading this kind of file.

 

How do I proceed from here? I've tried running the installer /S and with /S /remove 1, but I still cannot install the latest version of Immunet without the installer assuming >1 copy of the installer is running.

 

Thanks for any help and suggestions you can provide. I feel "naked" without Immunet running on my Windows PC.

 

- Dave

[nwarshawski@sourcefire.com]

Hi Dave,

 

This is really strange! There are a few things that may be going on here. Sometimes, an install will queue itself until after a reboot, or there may be Immunet leftovers preventing a fresh install. I'd like you to try a few things.

 

First would be to check Programs and Features for Immunet 3.0, and uninstall it if it's there. Next would be to also check for Suze Orman or Trusted ID Secure Scan, if you've ever had those, and uninstall that as well.

 

Next would be to look at your Services (Windows key, type services). If you see Immunet 3.0 or any other Sourcefire/Immunet services, make sure they're stopped.

 

Finally, check your msconfig (Windows key, msconfig, enter) boot settings and look for any Immunet artifacts there. Ensure there are none, or that they're disabled, and restart.

 

After the restart, check your processes for agent.exe and your services for Immunet 3.0. Neither should be there.

 

Wait a bit so that its clear that no Immunet installs are queued. Download an installer from

http://download.immunet.com/push/immunet/ImmunetSetup.exe

and run it once. Don't bother with the silent options because that will only keep information from us.

 

Hopefully, this works! If it doesn't, let us know and we'll keep at it!

[ViperGeek]

First would be to check Programs and Features for Immunet 3.0, and uninstall it if it's there. Next would be to also check for Suze Orman or Trusted ID Secure Scan, if you've ever had those, and uninstall that as well.

Thanks for the rapid response, Nick.

 

I confirmed that no Immunet, Sourcefire, Suze Orman, or Trust ID apps are installed under Programs and Features.

 

Next would be to look at your Services (Windows key, type services). If you see Immunet 3.0 or any other Sourcefire/Immunet services, make sure they're stopped.

I scanned all Services on my system and nothing starts with Immunet or Sourcefire. It looks like the uninstall ran very cleanly.

 

Finally, check your msconfig (Windows key, msconfig, enter) boot settings and look for any Immunet artifacts there. Ensure there are none, or that they're disabled, and restart.

 

After the restart, check your processes for agent.exe and your services for Immunet 3.0. Neither should be there.

I looked through all tabs and options of msconfig and there are no references to Immunet or Sourcefire. Ctrl-Shift-Esc shows no agent.exe instances.

 

Wait a bit so that its clear that no Immunet installs are queued. Download an installer from

http://download.immunet.com/push/immunet/ImmunetSetup.exe

and run it once. Don't bother with the silent options because that will only keep information from us.

 

Hopefully, this works! If it doesn't, let us know and we'll keep at it!

No joy. I get the exact same error message. It almost feels like there's a Registry key or temp file floating around somewhere, possibly with the wrong permissions. I am in the Administrators group, but I have seen odd protections that even fustigate admins.

 

Thanks again for your help.

 

- Dave

[nwarshawski@sourcefire.com]

Another thing to do before an install would be to manually remove C:\Documents and Settings\All Users\Immunet or in Win7 C:\users\all users\immunet and any files in the directory. (After an uninstall)

 

Nick

[ViperGeek]

Another thing to do before an install would be to manually remove C:\Documents and Settings\All Users\Immunet or in Win7 C:\users\all users\immunet and any files in the directory. (After an uninstall)

Thanks Nick. The folder was there, but after deleting it, I still get the same error.

 

- Dave

[nwarshawski@sourcefire.com]

Hi Dave,

We're looking into this and will get back to you as soon as possible. Thanks for the heads up!

Nick

[nwarshawski@sourcefire.com]

Here's an idea. Please download Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Attempt an install

Run Process Explorer as admin and Ctrl+F search for BaseNamedObjects\P

Look for anything that ends with that search, as in, ends with just a P.

To help us out, could you highlight and copy any process that contains it, with the following columns visible: User Name, Description, Company Name, Image Path, Window Title, Window Status, Session, Command Line and Autostart Location. Then paste it in a reply here!

 

If this exists within another process or another installer, it would be the reason why an install fails.

If you find a process with it, shut that down and an install should go through.

 

Nick

[ViperGeek]

Here's an idea. Please download Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Attempt an install

Run Process Explorer as admin and Ctrl+F search for BaseNamedObjects\P

Look for anything that ends with that search, as in, ends with just a P.

To help us out, could you highlight and copy any process that contains it, with the following columns visible: User Name, Description, Company Name, Image Path, Window Title, Window Status, Session, Command Line and Autostart Location. Then paste it in a reply here!

 

If this exists within another process or another installer, it would be the reason why an install fails.

If you find a process with it, shut that down and an install should go through.

ABSOLUTELY BRILLIANT! You definitely earned your gold Tech Support star for today!

 

I actually run (and am a big fan of) Process Explorer during startup. I searched for handles with the substring "BaseNamedObjects\P" and sure enough, a program I run constantly, called PidginPortable -- a PortableApps version of Pidgin -- uses a Mutant named \Sessions\1\BaseNamedObjects\P. Shutting down PidginPortable allowed the installation to run flawlessly.

 

Thank you very much for your help, Nick! I don't know how you pulled that one out of your magic bag of tricks, but you nailed it.

 

- Dave