Joliet_tech

I finally got "Incorrect Ethernet Packet" IDS exception to work. I had to set the Direction in the rule to "Both" and presently doing it by detected IP address; after verifying the IP address is associated with a Win Store connection.
Sure hope Eset figures out what the problem here is proto. 
-EDIT- Forget any exceptions. When I set direction to Both I started seeing blocked Google server connections appearing whose IP addresses were never seen before.
Appears to me something serious is borked in IDS detection.

Thank itman for all the advice and information.  But I have more then one ip address to block.  I'm not very computer savvy so I turned my wifi back on and wait to see if this gets corrected by Eset.

I am also starting to lean toward Port 0 usage by Microsoft as the possible culprit.
This would not be the first instance I had in that regard using Eset. I believe in ver. 11, Eset changed something in this regard. My ISP for reasons beyond me does ICMPv6 pinging against my router; probably for connectivity purposes. My Win firewall event log was expanding a phenomenal rate  from block activity related to this. That plus Eset's firewall wizard showed the same  phenomenal counts. I resolved this one by just creating firewall rules to allow the activity for the IPv6 IP addresses involved.

Disabling Network Attack Protections (IDS) on the PC being accessed has addressed the issue of accessing the fileshare quickly and allowing access to the app hosting machine (screenshot reflects my PC which has IDS still enabled, but is initiating the access).
I need guidance what disabling the IDS affects and what is my risk if I leave it disabled.

Unblocking these "Incorrect ethernet packet" errors (and there were many, DNS, DHCP, Microsoft Publication Service (there were multiple of these), and  Akami) the network file share works, but they are extremely slow.  Other network apps that look for the hosting PC listener and resolve the access criteria is still failing.  I have disabled the firewall which did not seem to help. 

I am also having this issue and now I am unable to share files on the network.  This occurred after the most recent windows 10 update on 4-9-19.