Jump to content


Photo
- - - - -

Immunet 3.0.5 Beta Available


  • Please log in to reply
20 replies to this topic

#1 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 02 November 2011 - 06:14 AM

Hi everyone, the Immunet 3.0.5.7512 Public Beta is now available! The installer below can be used for new installations and upgrades from all prior 2.x.x and 3.0.x versions:

http://download.immu...etBetaSetup.exe

Please note this beta will require a full uninstalled before re-installing with an official Immunet release version.

I'd like to thank everyone for their patience with our recent release schedule and slow responses to forum queries. As you may have already heard we are working very hard towards our upcoming Enterprise product, and we have good news - we have not forgotten out consumer users and are incorporating as many of our new enterprise features back into the consumer version of our product:

* Cloud engines now perform much more through scanning of PDF, SWF, and MS Office documents. These types of files are used extensively to spread macro virus` and trojan horse type malware, and we've come up with a much better way to scan them than was possible in previous versions.
* Compatibility updates. We've made a few changes to help us improve compatibility when running applications that deal with large files, such as bit torrent clients, VMware images, photoshop/photo-editing software, etc.
* Bug fixes & enhancements to our installer as we begin laying the groundwork to upgrade 1.0 users into directly to 3.0.5.
* Performance updates! I know I say that every release, but this time were so happy with our performance gains that we've decided to turn blocking mode back on by default. So if you've previously used Immunet and normally run in with blocking mode turned off, please turn it back on and give it another try. We are especially excited to hear any feedback our users have here.

Reporting Issues:
If you have any feedback please post it to this thread. If you think you've found a bug please include a description of the problem, instructions to reproduce it, and any relevant screenshots.
  • Doocculsinc and bxvxxKK88 like this

#2 Guest_Mature_*

Guest_Mature_*
  • Guests

Posted 02 November 2011 - 10:21 AM

This really is a long time wait~But still congrats to you guys :) And I'd like to ask about multiple-language version,how come you hardly publish beta in none-English?

#3 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 02 November 2011 - 11:36 AM

Cool! Always happy to help beta test a new version especially where a performance enhancement is concerned. Thanks guys!

* Immunet Global Forum Moderator *


#4 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 02 November 2011 - 01:32 PM

I'm getting an error code when trying the updater. Here's what it says: Initialization Failed with code: 404There may be a server update issue. Please wait and try again. It does seem to be connecting to the server though because I then get some of the usual messages: Checking for definition updates - Latest updates already installed. Right after installation I created new allow rules with Comodo Firewall because of the new checksum and checked to make sure agent.exe & iptray.exe had internet access which they do. So no problem there. Let me know if you want me to send in a diagnostic report.

* Immunet Global Forum Moderator *


#5 Guest_Mature_*

Guest_Mature_*
  • Guests

Posted 02 November 2011 - 08:57 PM

I'm getting an error code when trying the updater. Here's what it says: Initialization Failed with code: 404There may be a server update issue. Please wait and try again. It does seem to be connecting to the server though because I then get some of the usual messages: Checking for definition updates - Latest updates already installed. Right after installation I created new allow rules with Comodo Firewall because of the new checksum and checked to make sure agent.exe & iptray.exe had internet access which they do. So no problem there. Let me know if you want me to send in a diagnostic report.



same here,and I find that browsing Internet with opera isn't smooth as it used does

#6 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 03 November 2011 - 04:41 AM

Just tried the updater again. Still getting the same 404 error code first but I did just receive several definition updates that downloaded and installed with no problems. So the updater is working. Sorry to hear you're having an issue with your Opera browser Mature. I haven't noticed any discernible difference with Mozilla Firefox.

* Immunet Global Forum Moderator *


#7 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 04 November 2011 - 08:30 AM

I have a question. Comodo Firewall was asking me if I wanted to allow creport.exe internet access using TCP Source Port 51430 and Destination Port 80. At first I didn't know what it was since I never encountered it before. After looking into it further I did find creport.exe is the Immunet 3.0 Crash Reporter located in the Immunet 3.05 folder in Program Files. After finding out it was an Immunet process I did allow it access. Is this something to be concerned about? Or is that process suppose to phone home on occasion normally? The program itself seems to be running just fine except for the minor 404 updater bug. Some feedback on this would be appreciated. Regards, Ritchie...

* Immunet Global Forum Moderator *


#8 Millard

Millard

    Employee

  • Administrators
  • 294 posts

Posted 04 November 2011 - 02:18 PM

I have a question. Comodo Firewall was asking me if I wanted to allow creport.exe internet access using TCP Source Port 51430 and Destination Port 80. At first I didn't know what it was since I never encountered it before. After looking into it further I did find creport.exe is the Immunet 3.0 Crash Reporter located in the Immunet 3.05 folder in Program Files. After finding out it was an Immunet process I did allow it access. Is this something to be concerned about? Or is that process suppose to phone home on occasion normally? The program itself seems to be running just fine except for the minor 404 updater bug. Some feedback on this would be appreciated. Regards, Ritchie...


There are two answers for creport.exe. It's Crash Reporter that gives us a dump in the field to find issues and prioritize bugs based on that, so the sending of the crash information isn't something to worry about. However, the reason it is running is something to worry about because that means a crash occurred. I'll talk to Rob when he gets in, but I believe there is a crash fix in or coming.
--Millard

#9 Millard

Millard

    Employee

  • Administrators
  • 294 posts

Posted 04 November 2011 - 02:39 PM

404 error is fixed. There is a configuration file for updating to the next version that was missing.

#10 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 04 November 2011 - 02:59 PM

Ok, thanks for the input Millard. Glad to hear the 404 error has been corrected and the info on the reporter.

* Immunet Global Forum Moderator *


#11 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 05 November 2011 - 04:06 AM

Thanks everyone for the heads up on the 404 errors.

Richie: the crash I was seeing would manifest when I opened the history and tried to delete a previously quarantined files. The Immunet interface would show a loading message for ~2 minutes, then pop up a message saying "Immunet 3.0 must be connected to the cloud to....". At that point, if I checked the task manager I would see agent.exe was no longer running. Did you try something something similar to this? If not, please check your C:\program files\Immunet\ directory for a file with a .dmp extension - this is the file that creport.exe tries to upload if there is a crash. Creport should delete the .dmp file once it's been successfully uploaded; if you see any .dmp files in your Immunet directory please let me know.

Mature: Can you check your Immunet settings and if blocking mode is turned on, can you try turning it off and see if this improves your Opera performance?

#12 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 05 November 2011 - 10:20 AM

I know what triggered creport.exe. It was Emsisoft's Mamutu (silent install) downloading and trying to install components to upgrade from 3.0.0.19 to 3.0.0.20. "Everything" slowed to a crawl during that process but nothing entirely crashed including Immunet. At least I don't think Immunet crashed but I could be wrong on that. After upgrading a re-boot was necessary. Upon re-boot, that is when I got the firewall alert for creport. I looked and could not find any dmp extensions in the 3.0.5 folder so it must have been sent.

* Immunet Global Forum Moderator *


#13 Guest_Mature_*

Guest_Mature_*
  • Guests

Posted 05 November 2011 - 01:23 PM

Thanks everyone for the heads up on the 404 errors.

Richie:  the crash I was seeing would manifest when I opened the history and tried to delete a previously quarantined files.  The Immunet interface would show a loading message for ~2 minutes, then pop up a message saying "Immunet 3.0 must be connected to the cloud to....".  At that point, if I checked the task manager I would see agent.exe was no longer running.  Did you try something something similar to this?  If not, please check your C:\program files\Immunet\ directory for a file with a .dmp extension - this is the file that creport.exe tries to upload if there is a crash.  Creport should delete the .dmp file once it's been successfully uploaded; if you see any .dmp files in your Immunet directory please let me know.

Mature:  Can you check your Immunet settings and if blocking mode is turned on, can you try turning it off and see if this improves your Opera performance?



I've tried turning off the blocking mode but it doesn't make any better,and I also find that Immunet has lots of I/O operation,when I run some applications I can here my hard drive "buzzing" which sounds hurt~ BTW I was running Immunet along with Webroot SecureAnywhere Beta v8.0.0.66,maybe it has something to do with my weird performance.   ps: maybe you guys can refer WRSA for some good stuff,like the tiny size and various customize settings,especially the smooth experience is excellent.   Mature

#14 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 06 November 2011 - 06:07 AM

I have noticed a change with the updater. Definition updates download and install much quicker. Nice improvement!

* Immunet Global Forum Moderator *


#15 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 07 November 2011 - 09:53 PM

Hi Richie, I wasen't able to reproduce exactly what you ran into with Mamutu, but I did notice it writes a lot of temp sqlite journal files to disk and Immunet scans each one. Please add an exclusion for c:\program files\mamutu and this should prevent your computer from locking up the next time Mamutu updates.

#16 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 07 November 2011 - 10:25 PM

Hi Mature, I had a quick look at WRSA today too. Please add exclusions to Immunet for C:\Program Files\Webroot\ and C:\ProgramData\WRData. WRSA should also get an exclusion to prevent it from scanning C:\program files\Immunet

#17 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 1,927 posts
  • LocationOil City, Pa. U.S.A.

Posted 08 November 2011 - 06:42 AM

Hi RobT, I did have Mamutu's Program Files in Immunet's Exclusion List prior to the upgrade event. Normal daily updates I have no problem with. It was upgrading to a newer version that I believe activated creport.exe. I don't think this will be a serious issue for users however as Emsisoft rolls out a major upgrade for Mamutu "very infrequently."

* Immunet Global Forum Moderator *


#18 Guest_Mature_*

Guest_Mature_*
  • Guests

Posted 09 November 2011 - 04:03 PM

Hi Mature, I had a quick look at WRSA today too.  Please add exclusions to Immunet for C:\Program Files\Webroot\ and C:\ProgramData\WRData.  WRSA should also get an exclusion to prevent it from scanning C:\program files\Immunet



RobT: I did what you told me to do but seems problem was still there,so I tried add opera's folder to exclusion turns out it works :) add this path to exclusion would solve the lag thing with opera:
C:\Documents and Settings\Administrator\Local Settings\Application Data\Opera
I didn't look into exactly what folder that causes the problem,but I think the massive I/O operation maybe relates to opera's cache files Mature

#19 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 11 November 2011 - 12:46 AM

Thanks Mature. I don't want to excluding a browser's app dir (at least, not with the release version of Immunet) - this would make the browser more vulnerable to drive-by-download type attacks. I'll see if I can figure out anything else we can do to address this though.

#20 RobT

RobT

    Advanced Member

  • Administrators
  • 241 posts

Posted 11 November 2011 - 12:50 AM

Thank you guys very much for your participation in this Beta. We've released 3.0.5.7515, and it's available via http://download.immu...mmunetSetup.exe - please make sure to uninstall your beta version before re-installing with the latest.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users