Same here as
@rtwjunkie , I have four endpoints in my home that all use MBAM Premium fully enabled and I enabled Defender scans as well. No issues.
I also have several systems (physical and virtual) that only rely on Microsoft Defender, which has definitely improved a lot in the past several years.
All systems are updated to 2004, I started with my main system on day one of release. I push this update out through my home-lab managed WSUS server for all but one system which I have yet to upgrade from Win 10 Home so it isn't domain joined and I decided to leave it looking at MS public update servers to compare experiences with what I authorize via WSUS.
The last time I had an issue with MBAM, it was fixed quickly with an update and honestly I'd have to check but I want to say that was 2-3 years ago. Everyone's experience will be different, but overall I've had good luck with Windows 10 2004 and Webroot SecureAnywhere, BitDefender, MBAM Premium, MBAM Free, Microsoft Defender both solo and combined with previous solutions, and also disabled and left disabled once a third-party solution was deployed.
I surely can't knock Defender anymore, nor will I. While it isn't as thorough as other solutions, its pretty damn good. Mixing that with good habits, using DNS filtering for your LAN devices (OpenDNS, Quad9, Cloudflare, etc.), and utilizing some additional management, I use pfSense (I built a cheap PC which works great) with pfBlockerNG (for IP and domain filtering)and Snort (IPS for WAN, IDS for LAN) along with OpenDNS for Home that my pfSense and DC's point to for DNS, for example.
What I do has proven to be very effective, but I also am a sysadmin by trade too so I love doing this stuff. Simplifying it for more basic end-users, I believe having two AVAM (Anti-Virus / Anti-Malware) solutions on your systems is a good idea as no one solution is perfect but combining solutions especially with more cores, GB's of RAM and SSD's is perfectly acceptable IMHO. Then setup your router to use secure DNS instead of ISP DNS, I usually start with OpenDNS (208.67.222.222 and 208.67.220.220), then quad9 (9.9.9.9), sometimes I'll add Google as a public less secure just in case the secure options are having issues (8.8.8.8). Set your DHCP on your router to use the router as the DNS server. This is pretty effective, fairly simple to do, with no additional management.
You can take it to the next level pretty easily by going to OpenDNS and create a free home account to do more management of what content and domains you want to block or allow for your WAN IP, some routers can check-in directly with OpenDNS, some can't and you'll need to use a small agent on a PC in your LAN. Just looking at OpenDNS uses their default domain list, having the option to use that AND add your own whitelist/blacklist is quite nice. Filtered DNS makes a difference and is worth the time and effort, which ultimately ends up being very low effort and can show you what DNS requests coming from your home are being blocked...the Home (Free) edition doesn't track by LAN IP, just your public WAN IP. You have to pay if you want more features...but what it offers for free is more than enough to help many homes hunker down and deal with lower DNS poisoning risks along having some free and easy content/access filtering to go alongside your AVAM solution(s). MBAM's domain filter works pretty good as well, alongside these solutions makes it easy to crank things up even further. Webroot is pretty good as well IMHO.
Windows 10 2004 has continued to perform great with these kinds of measures being taken, and I expect future versions to continue that. If we start talking about VPN's and road-warrior DNS bleed issues, that's a slightly different matter, but really unrelated to this. But if you're working remotely and have an SSL-VPN client setup on your Windows 10 system and notice that sometimes your queries for office-side resources by hostname don't work, then it is relevant. I still see that a lot. But again, that's not really related to OS security and AVAM solutions, just worth mentioning.