Jump to content


Photo

Immunet Service Disables At Startup

version 6.04.10.585

  • Please log in to reply
12 replies to this topic

#1 bitscooper

bitscooper

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 22 September 2017 - 10:23 AM

Hello,

 

 

After the latest upgrade to 6.04.10.585, i did start to get annoying messages that my AV is  disabled at startup.

If i look in the immunet application everything seemed to be fine, but when i look in services the immunet service is disabled.

 

When i do a manual start the service is working fine again, but every restart the issue surfaces.

 

Are more people experiencing this?

 

System is W10pro x64.

 

 

 

 

 



#2 trujax

trujax

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 23 September 2017 - 03:05 AM

I get something similar.  I often need to restart the service several times before it works.  After enabling Verbose notifications, I also get that the self protection driver is not loaded properly.   

 

I am Win10 Home.  



#3 P36L4

P36L4

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationAustralia

Posted 23 September 2017 - 04:11 AM

Yep, this is exactly my problem too - after a system restart the AV needs to be manually started (win7)


Edited by P36L4, 23 September 2017 - 04:11 AM.


#4 ritchie58

ritchie58

    Staff Member

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

Posted 23 September 2017 - 04:58 AM

There are times when Immunet doesn't launch properly at the first boot-up. From experience I have had to re-start more than once to get Immunet to launch properly.


* Immunet Global Forum Moderator *


#5 P36L4

P36L4

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationAustralia

Posted 23 September 2017 - 06:14 AM

Hmm, I did some more tests:

 

1) The problem appears when the system has been powered off

 

2) Then manually starting the service shows me this attachment - looks like a problem with the signature or why is it asking me for permission to start Cisco? Note the Don't show me again box is not checked hence the repetitive auto start problem?!

 

3) Now I checked that box and after another sys pwr off/on the auto start seems to work now (at least for me)

 

Hope it stays that way and maybe this helps others?

Attached Files


Edited by P36L4, 23 September 2017 - 06:14 AM.


#6 ritchie58

ritchie58

    Staff Member

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

Posted 23 September 2017 - 06:20 AM

One of the first things I did after installing Win 7 a few years ago was to "turn off the Windows UAC" as that seemed to create more problems than making me feel more secure.


* Immunet Global Forum Moderator *


#7 P36L4

P36L4

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationAustralia

Posted 23 September 2017 - 06:48 AM

I have no problems with the 7 UAC but interesting which implications can hit software not specifically coded for it :blink:



#8 ritchie58

ritchie58

    Staff Member

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

Posted 23 September 2017 - 06:55 AM

Yeah, that's why I was never happy with how Mircosoft's UAC program's code distinguished between good & possibly malicious programs. Not properly recognizing valid SHA256 and MD5 checksum for the program(s). It almost seemed like a random, hit or miss, approach. 


* Immunet Global Forum Moderator *


#9 bitscooper

bitscooper

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 23 September 2017 - 09:17 PM

​This seems like a serious bug. It happens on different occasions, with different results and different systems too.

Personally i did not experience this on W7, because i tried before i posted here.  I assumed it had something to do with W10 and his boring updates.

I​



#10 P36L4

P36L4

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationAustralia

Posted 23 September 2017 - 10:58 PM

The biggest issue is there is no visual indication the service is running or stopped... - it certainly would be helpful when the tray icon would change colour hence green for running and red for stopped. I wonder how many people do realise their AV does not work coz the service is stopped?!



#11 bitscooper

bitscooper

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 24 September 2017 - 12:10 AM

The biggest issue is there is no visual indication the service is running or stopped... - it certainly would be helpful when the tray icon would change colour hence green for running and red for stopped. I wonder how many people do realise their AV does not work coz the service is stopped?!

W10 gives notification about this via "action center", this is how i discovered it. But your comment is a good point. Besides whatever action from windows, immunet should warn as well. My suggestion would not be for the tray icon to change color, because i assume many users have hidden it, but a pop-up from the tray...can't miss that one.



#12 ritchie58

ritchie58

    Staff Member

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

Posted 24 September 2017 - 05:08 AM

Immunet did have the ability to let you know it has launched properly when the little pop-up cloud notification would appear. That's if you had the Cloud Notifications turned on located in the Notification Settings tab of course. Unfortunately with the newest 6.0.4 build the cloud notification feature doesn't seem to be currently functional. I have disabled this setting until this minor bug is fixed.


* Immunet Global Forum Moderator *


#13 P36L4

P36L4

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationAustralia

Posted 30 September 2017 - 01:52 AM

I recently (last week) did a clean 7-install due to the cCleaner malware and since then no more (status) stopped problems.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users