As you are able to connect in Safe Mode with Networking there's no need to post your ipconfig /all.
I don't know what MSF32 is but create a restore point then right click on MSF32 and select Uninstall then click on Action/Scan for hardware changes - although I don't think it is relevant to connectivity as you can connect in Safe Mode with Networking unless it's causing an IRQ conflict in Normal mode where it would be loaded.
If its a missing driver, then Windows will reinstate it.
When you can get a connection in Safe Mode with Networking but not in Normal mode, it's either your AV program, an infection or something in your Startup items in msconfig - I use Norton 360.
Can you do a manual check for updates for ESET - sometimes a buggy Definitions update can block connectivity.
If you don't have the free version of MBAM installed, boot up into Safe Mode with Networking and download and run it.
https://www.malwarebytes.org/ - Decline the Pro version free trial.
If it's still a no go in Normal mode then perform a clean boot.
In a clean boot all your Startup items and non-MS services are disabled except your AV program as that will reinstate itself, so if you get a connection in the clean boot - it won't be ESET that's blocking but if you still cannot connect, that would normally point to your AV and a reinstall of it may be needed.
Re-enable ESET before checking for Definition updates and leave enabled for the clean boot.
Just looking at yours specs in your opening post - do you not have a wireless card fitted ?