fing.agent service constantly needs to be restarted

Often when I open Fing Desktop the network report is stuck with 5 pending checks and 'see all devices' opens with a blank page.  To fix this I close Fing Desktop, restart the fing.agent service and reopen Fing Desktop.
Why does the service keep needing to be restarted?
Fing says the network is not active but there are no other symptoms of it being an issue.
Here is a fing agent log:
ERROR 2020/12/18 12:55:08.110 === fing agent 2.4.0 - www.fing.io ===
ERROR 2020/12/18 12:55:11.718 NetworkWirelessAvailableDetails | Error encountered. Code: 1062 
ERROR 2020/12/18 12:55:11.719 NetworkWirelessAvailableDetails | Error encountered. Code: 1062 
ERROR 2020/12/18 12:55:11.719 NetworkWirelessAvailableDetails | Error encountered. Code: 1062 
ERROR 2020/12/19 08:05:34.725 Error: unable to create the capture session: \Device\NPF_{73A1369D-74A1-4526-8B52-9F42142D5CD3}: failed to set hardware filter to non-promiscuous mode
ERROR 2020/12/19 08:51:21.850 Error: unable to create the capture session: \Device\NPF_{73A1369D-74A1-4526-8B52-9F42142D5CD3}: failed to set hardware filter to non-promiscuous mode
ERROR 2020/12/19 09:34:03.970 Error: unable to create the capture session: \Device\NPF_{73A1369D-74A1-4526-8B52-9F42142D5CD3}: failed to set hardware filter to non-promiscuous mode
ERROR 2020/12/19 09:56:00.775 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 09:44:52.846 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 11:44:04.744 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 12:47:04.173 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 13:50:03.596 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 14:53:03.047 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 15:56:02.480 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 16:59:01.916 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 18:02:01.378 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 19:05:00.648 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 20:07:59.993 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 21:10:59.400 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 22:13:58.817 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/21 23:16:58.232 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 00:19:57.691 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 01:22:57.134 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 02:25:56.585 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 03:28:55.985 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 04:31:55.303 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 05:34:54.714 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 06:37:54.145 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 07:40:53.578 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 09:34:53.266 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 10:37:52.712 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 11:40:52.153 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 12:43:51.523 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 13:46:50.864 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 14:49:50.266 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 15:52:49.677 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 16:55:49.102 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 17:58:48.595 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 19:01:48.041 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 20:04:47.474 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 21:07:46.936 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 22:10:46.261 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/22 23:13:45.627 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 00:16:45.025 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 01:19:44.449 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 02:22:43.890 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 03:25:43.357 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 04:28:42.784 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 05:31:42.242 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 06:34:41.646 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 07:37:40.964 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 08:40:40.338 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 09:43:39.794 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 10:46:39.202 Unable to discover ethernet network 192.168.1.0/24 since it's not active
ERROR 2020/12/23 10:58:50.689 === fing agent shutdown requested
ERROR 2020/12/23 10:58:50.689 TcpServer service shutdowning..
ERROR 2020/12/23 10:58:50.691 TcpServer service terminated
  

Answers

  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,761
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    Hi @RedFlanker

    With the new version 2.4.1, we have replaced winPcap with NpCap. As I can see your fing agent is still outdated 2.4.0.


    I would like you to follow these steps and the issue should be resolved.  

    -> Uninstall WinpCap using Revo(if possible)  

    -> Disable the Npcap driver service and then uninstalled the program. To disable NpCap:  
    1 Run this command as an admin: sc.exe config npcap start= disable  
    2 Uninstall Npcap  

    -> Reboot your device to safe mode with networking  

    ->Download and install new Fing desktop version and then open it.  

    -> Reboot to normal mode and then check if it works for you.  


    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    Hi @Robin,
    Thanks for your reply
    I had already uninstalled WinpCap prior to this.
    I followed your instructions but Fing is still showing the agent as 2.4.0.  (BTW the sc.exe command should be 'disabled' not 'disable')
    Any other suggestions?

  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,761
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    Hi @Robin,
    Thanks for your reply
    I had already uninstalled WinpCap prior to this.
    I followed your instructions but Fing is still showing the agent as 2.4.0.  (BTW the sc.exe command should be 'disabled' not 'disable')
    Any other suggestions?

    Is it still providing the same error?
    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    @Robin,
    I get the same error in the fing agent log - 'ERROR 2021/01/05 13:57:39.769 === fing agent 2.4.0 - www.fing.io ===', but so far I have not had to restart the service which is the main thing.  FYI I have also upgraded npcap to the latest version (1.10) - I thought it might jog the fing.agent into updating itself.
    So long as I do not have the issue of restarting the service I am happy though. Fingers crossed it will not happen again
    Robin_from_Fing
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    Hi @Robin,
    Although it has been a while since my last comment, unfortunately I am still regularly having to restart the service to get the fing desktop to function correctly.  I have followed your instructions for uninstalling and reinstalling a few times but to no avail.  I have noticed that although the fing desktop installed is the latest offering on the website and shows as 2.4.1, the fingagent.exe shows version 2.4.0 when the properties are viewed in windows:

    I ensured that this file did not exist prior to the installation so it can only be added during installation.  If this is the issue then how is it that I am getting this previous version of the service file?
  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,761
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    thanks @RedFlanker

    With the new version 2.4.1, we have replaced winPcap with NpCap. I would like you to follow these steps and the issue should be resolved.  

    -> Uninstall WinpCap using Revo(if possible)  

    -> Disable the Npcap driver service and then uninstalled the program. To disable NpCap:  

    - Run this command as an admin: sc.exe config npcap start= disabled  
    - Uninstall Npcap  

    -> Reboot your device to safe mode with networking  

    ->Download and install new Fing desktop version and then open it.  Link: https://www.fing.com/products/fing-desktop-download-windows

     -> Reboot to normal mode and then check if it works for you.  

    I will be looking forward to your reply.  

    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    @Robin,
    Thanks for your prompt reply.  Those are the instructions that you gave me earlier in the thread and they are the ones that I have followed every time I have reinstalled.  I do not have WinPCap installed and I am just using the npcap installed by fing.  I come back to my question as to why the service is still version 2.4.0 if that is not the correct version for fing 2.4.1?
  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,761
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    @Robin,
    Thanks for your prompt reply.  Those are the instructions that you gave me earlier in the thread and they are the ones that I have followed every time I have reinstalled.  I do not have WinPCap installed and I am just using the npcap installed by fing.  I come back to my question as to why the service is still version 2.4.0 if that is not the correct version for fing 2.4.1?
    I can confirm after investigating Fing agent will still be 2.4.0 even if you are using Fing desktop 2.4.1. If you are still facing issue, can you let me know if you are using any Firewall or Antivirus?
    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    Robin said:
    I can confirm after investigating Fing agent will still be 2.4.0 even if you are using Fing desktop 2.4.1. If you are still facing issue, can you let me know if you are using any Firewall or Antivirus?
    I am afraid this is still happening.  I use the latest versions of Kaspersky Total Security alongside Malwarebytes Premium.

    When I have to restart the service I get an error saying that the service did not respond although it does stop and once restarted all is fine for a while.

  • Robin_from_Fing
    Robin_from_Fing Administrator, Fing Team Posts: 4,761
    250 Answers 2500 Comments 500 Likes 100 Awesomes
    admin
    I am afraid this is still happening.  I use the latest versions of Kaspersky Total Security alongside Malwarebytes Premium.

    When I have to restart the service I get an error saying that the service did not respond although it does stop and once restarted all is fine for a while.

    I believe your Antivirus might be creating issues with the Fing desktop. Can you please disable Antivirus or go to safe mode with networking and then use the Fing desktop under safe mode only and then check if the issue persists?
    Robin (Admin at Fing)
    Getting Started? Please refer to Community guidelines & Community User Guides. HAPPY POSTING!!!
  • RedFlanker
    RedFlanker Member Posts: 7
    Name Dropper First Comment Photogenic
    @Robin,
    Sorry, no, I cannot do that.  Currently it manifests itself at random when I open Fing after a day or 2 and need information from it.  I am not prepared to run in safe mode for days or indeed to disable anti-virus for days.  I think that it is safe to say that I will have to either deal with Fing needing to have the service restarted every time I want to use it or find an alternative solution to monitoring my network.  Kaspersky and Malwarebytes are mainstream products and if Fing cannot work with them then I think that it is time for me to find a solution that can work with them, sadly