Jump to content

Immunet 6.2.0.10768 Errors


Recommended Posts

Hi,sorry to bother you,but I've installed 6.2.0.10768,I've installed what it should be the latest Immunet version 6.2.0.10768

But I have these issues: 

- 0 People displayed on the cloud

- and some process's errors

My O.S is W10x64 with all the latest updates.

Thanks in advance for your time and replies.

CropperCapture[13].jpg

CropperCapture[14].jpg

CropperCapture[15].jpg

Link to comment
Share on other sites

Guest Wookiee
1 hour ago, Muspellheim said:

same issue, as well as detecting immunet setup file as Clam.Win.Trojan.Generic-6619287-0 :)

immunet.png

We are aware of this and are investigating.

Link to comment
Share on other sites

Guest Wookiee
8 hours ago, Cipollino said:

Hi,sorry to bother you,but I've installed 6.2.0.10768,I've installed what it should be the latest Immunet version 6.2.0.10768

But I have these issues: 

- 0 People displayed on the cloud

- and some process's errors

My O.S is W10x64 with all the latest updates.

Thanks in advance for your time and replies.

CropperCapture[13].jpg

CropperCapture[14].jpg

CropperCapture[15].jpg

The process blocked, try turning the 'blocking' option off.

 

 

we notify and block the process which try to access protected processes ( Winlogon.exe ,lsass.exe, etc.). Once the SPP rule is triggered, the notification is reported on couple of conditions and one them is when “process is not clean and not signed. “

Link to comment
Share on other sites

@Wookiee 

I've already done that,but thanks anyway for suggesting it,but the "process issue" is still kicking.

I can report this strange behavior too,the two processes are blocked after 2 minutes I've started my computer,at that precise moment the [0 people on Cloud] flash for like 1ms.

I have no idea if this could be of any help.

Edited by Cipollino
Link to comment
Share on other sites

31 minutes ago, FreelanceJavaDev said:

the problem seems to be with the auto update mechanism, if you uninstall and then reinstall from a freshly downloaded version it still says 0 cloud users, but all those errors are gone and it works correctly. 

I've to say that's exactly what I did but the 2 process's errors that I have,they persist.

Link to comment
Share on other sites

The reason a fresh install works where as an upgrade doesn't for the 0 cloud users is because NEW installs goes to a newer cloud env,  that eventually everyone will be pushed to.
Upgrades don't. It's something we plan on fixing.

 

Link to comment
Share on other sites

2 hours ago, Wookiee said:

The reason a fresh install works where as an upgrade doesn't for the 0 cloud users is because NEW installs goes to a newer cloud env,  that eventually everyone will be pushed to.
Upgrades don't. It's something we plan on fixing.

 

I just did a fresh installation (deleted the previous Immunet, with geek uninstaller) but the 0 cloud users is here again^.

Edited by Cipollino
Wrong placement of my reply inside a quote.
Link to comment
Share on other sites

27 minutes ago, Cipollino said:

I just did a fresh installation (deleted the previous Immunet, with geek uninstaller) but the 0 cloud users is here again^.

Yes, the 0 cloud users is being looked into by the dev's- it is working for some- not everyone

Link to comment
Share on other sites

38 minutes ago, evjlsrain said:

for your information, v6.0.8 is still working flawlessly and doesn't have 0 cloud user issue. Its signatures are fully intact

Where can I get the link for that version,please.

I'll use it,till they fix the new one,then,obviously I'll move to it.

Thanks in advance for your reply.

Link to comment
Share on other sites

On 9/10/2018 at 11:41 PM, Wookiee said:

Yes, the 0 cloud users is being looked into by the dev's- it is working for some- not everyone

but is there any problem with the 0 cloud users? Are we unprotected? Do we have to switch to a previous version, or just wait for that fix?

Link to comment
Share on other sites

Just now, Aris said:

but is there any problem with the 0 cloud users? Are we unprotected? Do we have to switch to a previous version, or just wait for that fix?

yes there is. I'm a malware tester and I can see 0 cloud problem leaves users unprotected from less than a week old malwares (ClamAV offline engine is disabled). It could still detect old malwares but quite limited

 

I highly recommend to temporarily switch to the older version because at least it works

Link to comment
Share on other sites

1 minute ago, Wookiee said:

The message is just not updating. You aren't unprotected.

yes but I'm just partially protected. I trust my test because when I performed tests between v6.0.8 and v6.2

6.2 detected nothing while 6.0.8 detected most of the malwares (a few days old)

I tried to execute the malwares that 6.0.8 detected but 6.2 missed. 6.2 failed to protect and the VM was encrypted by a ransomware (which was detected by v6.0.8)

which means 6.2 doesn't fully protect users

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...