Sudden appearance of SNMP errors in Event Log

I have suddenly started seeing these EvntAgnt/ SNMP errors, arising at Startup, in the EL. Screenshots attached.

This is W10 Pro 1909 (18363.1082), and I very recently installed updates KB4576484 and KB4574727, on 9/9/20. The errors seem to have arisen since then.

In Services, SNMP Service is set to Auto and is running when I check after Startup, and SNMP Trap is set to Manual and not running. If I stop SNMP and restart it, the same errors are logged i.e. it's not just at startup.

Oddly, if I go to Settings>Apps>Optional Features, SNMP is offered as "Add a Feature" although it's already running as a service.

I have been through sfc and the usual diagnostic routes, and I can't think of any new software installed that would use SNMP anyway. If I look at Procexp, when running SNMP service is using port 161 or 162 (one of the other).

Any help on this welcome. Do I need SNMP servies, and if so, under what circumstances, or can I just set it to Manual in Services?

Simple Network Management Protocol (SNMP) is a way for different devices on a network to share information with one another. It allows devices to communicate even if the devices are different hardware and run different software.

FreeBooter said:

Simple Network Management Protocol (SNMP) is a way for different devices on a network to share information with one another. It allows devices to communicate even if the devices are different hardware and run different software.

Thanks for your reply. I'm reasonably familiar with what SNMP does, but I can't quite work out why it has started to produce errors, or indeed what it is doing in this particular setup. It's not running on any of my other W10 Home (2004) machines.

I have looked again at the "Add a Feature", and it appears that SNMP is listed there with an "Uninstall" option. The question then is whether I should uninstall it from there, presuming that it can be added back if needed, and that's why I'm keen to pin down its precise function vis a vis software in my system. I've tried tracing it through netstat, but that doesn't tell me enough to drill down to the essentials.

Ghot said:

According to Black Viper's website... The SNMP service doesn't normally come installed on Windows 10 Home or Pro.



Black Viper’s Windows 10 Service Configurations – Black Viper | www.blackviper.com

I think it's available to install in both Pro and Home, in the Apps>Features screen, which in later W10 releases has apparently superseded the SNMP "enable" option which used to be in Control Panel>Programs>Windows Features.

What I can't understand is why it is now enabled/running (not instigated by me) as a Service, and why these errors, which I have never seen in the EL on this system before? If it's another piece of non-MS software that needs it, it very hard to see what, and I haven't added anything recently, in the time since the errors appeared. My laptop running 2004 is also quite a close mirror of my desktop, on which these errors appear, and if apps on one need SNMP, then it would be reasonable to think that it would be the same on the other; but it's not.

If it can be uninstalled via Apps>Features, it would be good to know what the effect might be, but I guess the test would be to set the service to Manual and see what happens then.

The SNMP event log agent has attempted to look for the end of a logfile, but it has received error 122 (insufficient buffer).
Your eventlog files may be corrupt, or the agent may not have been able to allocate enough memory to accomodate the eventlog.
You can clear event logs to see error comes back use the batch script i have attached to clear event logs.