Strange 'nmap' behavior after recent EA App / BF6 update — an interference?

PerkyflyNCE​ 

Thanks for following up and owning the root cause -- that clarification helps a lot.

For anyone reading this later: EA app / Battlefield do not install networking drivers or packet-filter components that would selectively affect CLI tools like nmap while leaving Zenmap functional. Zenmap invokes the same nmap engine, so a driver-level or kernel-level conflict would impact both.

The behavior described lines up with Windows IPv6 / transition-tunnel configuration changes (Teredo / 6to4 / ISATAP + adapter-level IPv6 disablement), which can break raw socket operations and also cause unrelated symptoms like SMTP rejection.

In short: this wasn’t related to the EA app, Battlefield, or anti-cheat -- it was a local network stack configuration issue that happened to surface around the same time.

Appreciate you posting the resolution; it’ll save someone else a lot of time. :)