HOW TO COMPLETE DISABLE IMMUNET

[Polin79]

During live streaming I need to complete disable Immunet because I have had some problems with NGINX server: could kindly suggest me how to complete temporary disable immunet on Windows 10?

Thanks

Paolo

[ritchie58]

Hi Paolo,

Unfortunately there is no easy way to completely disable Immunet temporarily.  

I suppose you could go into 'Settings' & manually turn off the cloud engines and the ClamAV module but that would leave your computer vulnerable to infection as long as these settings remain disabled.

What type of problems are you having? Is Immunet quarantining any files? It might be you just have to create a custom Exclusion rule or two.

[John Graham]

Hi Paolo,

You could do what I do: Services->Immunet 7.5.0->Stop

Task manager->Immunet Tray Client->End process Tree.

Notes:

01 - You cannot stop the "Immunet Security Connector Monitoring Service 7.5.0" service.

02 You might want to heed the advice above "but that would leave your computer vulnerable to infection as long as these settings remain disabled. " So you need to enable the service and start the tray Client as soon as you are connected to the NGINX server. Also advisable to do a scan after you are done.

03 - Personally, I don't use Anti Virus programs - it's like locking the barn door after the horse has bolted, meaning, a virus needs to be absolutely detected before a signature can be generated. Heuristic analysis is just guesswork although script based viruses (like the famous "ILOVEYOU" and Anna Kourniko) are detected. Using a dedicated frontend IDS/HIPS (a thin client is all you need as it operates "headless").

04 - You need to determine the port you are using to connect to the NGINX server - it may be blocked by your firewall not by Immunet. An easy way of determining that would be to temporarily disable the Immunet service as above and see if you can connect. If not, then it is your firewall - Windows Firewall is not the greatest and complicated to set up with rules and schedules. The best firewall was AtGuard but it was made by WRQ (later acquired by Norton, rebranded and bloated as NIS) which fit on a floppy (1.44 Mb) and had the 3 main rules of firewallling - application/language/protocol/port/direction (example: Browser (specific like Firefox.exe)/HTML/TCP/80/Incoming-outgoing or Browser (specific)/HTTPS/TCP/8080/incoming-outgoing or (for the old MS/IBM NetBEUI) All/All/All/137-139/incoming-outgoing).

Hope this helps.

JG

Edited August 28, 2022 by John Graham
Recollected Firewall name (Atguard) and company (WRQ)