I don't think that's true. I never run any manual scans, and I can see in Task Scheduler how long the scheduled scans take: no time at all (these are not Ye Olde AV scans that run an hour). Yet, if you run your PC a day or five and then look at the Details tab with CPU Time sorted, you'll see that msmpeng.exe is WAY, WAY up the list. What's doing that can only be one thing: real-time protection. Almost every single thing you touch on the system is appraised by Defender, so it's death by a thousand cuts. It just makes everything a little bit slower, the CPU time most certainly adds up, and it's unrelated to manual or scheduled scans (in my case). It may be better in this dept than most (not all) 3rd-party AV, but then it does less than all of them too, and has worse results than most of them, so it pretty much stands to reason. But regardless, the resources it takes are not nothing.
Today I went back to build 10049 had some serious issues with build 10056 !! Too bad I realy liked the build but what ever up to the next release
I apologize, sorry about that. My bad. I had never really looked into the languages before regarding these builds. Thank you both for correcting me on that. Cheers!
Taken from [link, put http in front] ://ms-vnext.net/Win10labs/ [link] All the builds leaked so far (other than the official preview ones) are EAP Drop (Early Partner Drop). So far after 10056 no EAP Drops. So now we can know when a new Leak would happen.