In Feedback, many, many people asked to see that put back in.... But I agree it should drop out if for some reason people want to turn Defender off.
Maybe it should be an option in Defenders Group Policy settings. Anyway the solution was posted at Post #529 friend.
I hate to say it but but we won't know until the final bits hit(Probably this week). There is a lot of talk both ways but they are opinions and the cat won't come out and confirm lol.
May not be the drives themselves, could be controller and/or ram problems...the two times I had something similar happen it was intermittent and a bear to track down...once I had a motherboard controller failing, in another incident it was a DIMM with a single bad chip. Ram problems can cause data being read/written to corrupt, etc. I've seen no such problems here with 10586 as of yet. In another incident I can recall, I once kept getting a bsod crash which Windows pinned on the gpu driver--but turned out it was caused by a failing hard drive, believe it or not! Component-based crashes are like dominoes--one goes down in a crash and takes several other things with it--and often Windows identifies a component somewhere in the middle of the stack instead of the actual cause of the problem. Intermittents are the worst especially because the cause may not be logically related to the symptom.
Thanks, but I don't care to see the line removed from context because I'm one of the ones who asked for it to be put back in... I like the feature because I use Defender exclusively, and I got tired of having to open it up and do a custom scan just to test a single file or directory. I also did more feedback on Defender in which I asked for several options to be put back into the program--like limiting the cpu-time Defender can have while working--they do all of that automatically now, but I still like the manual options best. If I wanted automatic & mindless I'd be running OS X...
Looks like he has a hard drive problem. Use CrystalDiskInfo to check the health status of the HDD and it should be clear. I had a failing HDD exhibited similar problem: can not delete/copy files once in a while.
So people in 10586 will get an big update, i mean it could be a new build, the next divisible build by 16 it's 10592. Or the string can be changed by an kb? I'm ~not that smart~ when it comes to MS.