kwk1

If you are using Eset's Home or office network protection mode, all your local network devices are Trusted. As such, there really is no reason to disable SSDP service since Eset will allow all that type network traffic.

If you are using Eset's firewall Public network protection, the only trusted device on your network is the device where Eset is installed on. Eset;s default firewall rules for inbound SSDP traffic; i.e. UDP protocol port 1900, only allow this traffic for trusted network devices.
To stop this blocking activity from occurring, there are the following options:
1. Switch Eset network protection mode for your network to "Home or office network."
2. Disable the Win SSDP service. This is the option I employ since I use Eset's Public network protection.
3. Disable UDP on your router if it exists and is enabled. What is occurring is the router is allowing other devices on your network "to discover" your device for connectivity purposes.

I think you should be fine but if your unsure you could try it.

That is exactly running the troubleshooter wizard. Sometimes I've seen stuff blocked but what Marcos is saying is if you've had no issues its best not to go in there and unblock anything. That area is designed so if you find your having problems with something not working you can go in there and see if anything if maybe being blocked and unblock it.
You should be fine but it's hard to know exactly why something is being  blocked. 
I did find at one point when using the public network setting in Eset a lot of stuff was blocked in the network troubleshooter that wasn't when switched to home but some do recommend using public. The link below explains how to check and change this setting 
https://support.eset.com/en/kb3754-change-network-connection-firewall-setting-in-eset-windows-home-products
As for the browser control part unsure about this. If it happens again see if you can get a screenshot of the actual message