Immunet Install Crashes Windows 7 X64

[warp-9.9]

I am using whatever the current version offered on the site is. I run ImmunetSetup.exe, it connects to the internet, and downloads the 64-bit version. Before installation can complete, the system blue screens. My RAID driver file, ahcix64s.sys is mentioned on the blue screen. I use this driver to connect to SATA Boot/System disks in AHCI mode, and also a data array in RAID-5 mode. After reboot, Immunet is not installed in the appwiz.msc, although there are some files in "C:\Program Files\Immunet", although nothing useful, no installation logs, etc. Also note, there is no Immunet in my Start Menu -> All Programs. I do not even know if your diagnostic tool was installed. What explicit command (exe and arguments) should I run at the command prompt? If the exe even got installed, that is.

 

http://download.immu...mmunetSetup.exe

 

HTTP/1.1 200 OK

Content-Disposition: attachment; filename=ImmunetSetup.exe

Content-length: 477896

Content-Type: application/exe

Date: Sun, 17 Mar 2013 00:09:53 GMT

Last-Modified: Thu, 08 Nov 2012 19:49:01 GMT

Server: Apache/2.2.17 (Fedora)

Connection: keep-alive

Length: 477896 (467K) [application/exe]

[ritchie58]

Hi warp, is there a listing for Immunet in Programs & Features? Is Immunet's System Tray icon launching? Open Task Manager and see if the processes iptray.exe and agent.exe are running. If so, Immunet was installed. The cmd commands to manually start and stop immunet are:

 

to stop: net stop immunetprotect

 

to start: net start immunetprotect

[Francis]

Hi warp,

 

The commands Ritchie posted will certainly do the trick; if the service is not found then it's not installed. If you'd like more details you can check the install logs by going to the temp directory (enter %TEMP% into any file browser) and looking for a file called "immpro_install.log". You can also send this file to support@immunet.com (also with a note referring to this forum thread) and we'll see if we can figure out what's going wrong. Thanks,

 

- Francis

[warp-9.9]

Although 6 months have passed since the initial post -- the version has gone from 3.0.10 to 3.0.12, the installer file size from 4.5 MB to 16 MB -- the same exact problem occurs: instant BSOD crash during install.

 

I never even bothered to reply because of frustration with the response. You are asking basic questions which I already answered, suggesting commands which do not apply, and referencing files that have no useful information, all while completely avoiding the problem: BSOD DURING INSTALLATION! I have gotten different BSODs during installation, one was a BAD_POOL something, with no drivers mentioned. The other error was related to my AMD x64 RAID driver.

 

System drivers are all up to date. There are some driver bugs whereby if I copy large amounts of data from SSD to RAID array, or create large amounts of data on the RAID array (~500MB or more at once), the system will BSOD with the ahcix64s.sys driver. The only solution is to never use AMD based chipsets (or CPUs), Western Digital HDDs, or Patriot SSDs, as none of the companies ever update their firmware to address the problem. Noting this, and creating files more slowly to avoid this flaw, my system will otherwise happily run stable for weeks or months at a time. Never has an installer crashed my system. I frequently update all software, from nVidia GeForce driver bundles to Java JDK to Mozilla apps, everything in between. None of them crash my system.

 

Hi warp, is there a listing for Immunet in Programs & Features? Is Immunet's System Tray icon launching? Open Task Manager and see if the processes iptray.exe and agent.exe are running. If so, Immunet was installed. The cmd commands to manually start and stop immunet are:

 

to stop: net stop immunetprotect

 

to start: net start immunetprotect

 

appwiz.msc == "Programs & Features", which I initially said, it is NOT LISTED THERE. There is no ImmunetProtect service, it does not exist. services.msc == "Services", shows a BitDefender service with a description of "scan", referencing "C:\Program Files\Immunet\tetra\scan.dll". That is all. And after reboot (because of IMMEDIATE BSOD during installation), this service is not even running. It is set to manual. Also, although redundant, I will answer: there is no agent.exe or iptray.exe running. That would assume that the program completed installation, which it did not, which I already said.

 

There is a partial installation, such that the some files are extracted to disk, but they are never set up to run.

 

The command line to run that I asked about, was in reference to any support or diagnostic tools which were mentioned on the website as part of troubleshooting process, such as ipsupporttool.exe. However, that may or may not apply at this point.

 

Hi warp,

 

The commands Ritchie posted will certainly do the trick; if the service is not found then it's not installed. If you'd like more details you can check the install logs by going to the temp directory (enter %TEMP% into any file browser) and looking for a file called "immpro_install.log". You can also send this file to support@immunet.com (also with a note referring to this forum thread) and we'll see if we can figure out what's going wrong. Thanks,

 

- Francis

 

It is premature to confirm that these other commands will do the trick, because they do not even apply to the problem.

 

The install log "C:\Users\UserName\AppData\Local\Temp\immpro_install.log" has no useful information. Except perhaps for multiple things related to "ca*" functions, which fail to do something or other. I am assuming it's Certificate Authority related, and responsible only for the SSL handshake to the open HTTPS connections?

 

The only other useful piece of information I can find: If I quickly hit Details button during install, the very last word mentioned before the BSOD is "Trufos", upon which the system immediately BSODs.

 

I will send to you the immpro_install.log. All I know, is that no matter what, a user space program should never have the ability to instantly crash a system. Something is wrong with your installer. I want to help improve that situation if possible.

 

Scanning the forum again, I'll recheck these steps:

 

0. As far as I know, my computer is not infected. I have scanned with Spybot Search & Destroy, ClamWin, Avira, MS Security Essentials. Nothing malicious loaded in RAM, or in system files. There are some false positives I know about, tucked away inside archives. They are not active.

 

Ok, a few things:

1) Can you check if c:\program files\immunet exists? If it does please try and delete it.

2) Start -> search all programs and files -> enter "%temp%" (without quotes, with percent symbols). Windows explorer will open to your current temp data path (something like C:\Users\Owner\AppData\Local\Temp). Look for a file called immpro_install.log and delete it if it exists.

3) Download http://download.immu...mmunetSetup.exe and http://download.immu...-64.exe. These are Immunet's installers (for 64bit). Try scanning both of them with each of your AV products and see if there are any detections.

4) Disable all your other AV programs (MS Security Essentials, superantispyware, and Norton)

5) Now try installing Immunet

6) If Immunet crashes again, open the %temp% dir again, and see if it contains a new immpro_install.log - if it does please email this file to me at support@immunet.com with the subject "For RobT: forum thread ****" and I'll take a look at it.

 

 

Edit notes:

 

[1] + \tetra

[2] + LISTED

[3.1] + Known System Problems

[3.2] + Broken Install notes

[3.3] - Closing rant comments

[4] - Typos

[5] + 6 Months, 2 minor versions, same problem

[6.1] + Next steps

[6.2] - RobT steps, Fix URL typo, remove other forum #

 

[ritchie58]

Hello again warp. Sorry to hear you're still encountering issues. Something that may cause a partial install is if another antimalware/security program (maybe even your firewall) is interfering or blocking/sandboxing some of the install files while they're being downloaded from the servers by the bootstrapper installer or during the install process itself. Have you tried to "completely disable" all other security programs before running the bootstrapper? Also check your firewall to see if nothing is being blocked during the install process too.

[Jose]

Hi warp,

 

I have sent you an email with some information I would require to see if we can fix this issue.

 

Thank you for your patience.

 

-Jose

[warp-9.9]

It's been a while, over a year since I first wrote, and 6 months since last wrote. Got side-tracked but didn't forget this. Did another try, today with most recent installer, same result, instant crash/BSOD. Something in the installer triggers an instant BSOD issue with this combo of mainboard/chipset/hard drive setup. ASUS Sabertooth 990FX R1 and R2 boards (AMD 990FX/SB950 chipsets) have been used, AMD FX-8150 and FX-8350 CPUs have been used, 3 x WD VelociRaptor 500GB 10k RPM (WD5000HHTZ) drives used (data disks with installer on RAID5 setup on ports 1-3), two independent instances of Win7x64 OS on different SSDs on SATA ports 5-6 in RAID/AHCI mode (not part of any RAID, just independent disks). Often the BSOD refers to ahcix64s.sys, the AMD RAID driver. Using most current version. Have used every version from the one released with board to newest released by AMD, same result. It's probably a bug in the chipset, the driver, or HDD firmware, but the disks work 99% of the time. Once in a while under heavy load (defined as many files with small (less than 1MB) reads, or reads/writes, or a few large files with large reads/write (several dozen or hundread MBs), sometimes trigger a deadlock (requiring hard reset), which sometimes proceeds to BSOD (same). However, this installer triggers the error 100% of the time. If I could understand this specific trigger, maybe I could take that info back to hardware makers and get them to fix the bug. But I doubt that would ever happen, or such a blatant thing would have been fixed by now, in the 3 years since the hardware was released. Probably the best thing is to avoid triggering the bug in first place.