Two lessons to be learned from this fiasco:

1) Never have routine scheduled full AV scans, particularly if nothing is broke. They just look for trouble, and soon enough find it. My default WD scan is the Quick scan, which in this debacle did not cause any problems.

2) The value of routine scheduled WD (or any other AV) scans of any type must be questioned when all is well. If your real time resident protection didn't detect anything, it is unlikely an on-demand scan will find anything but false positives.

I can confirm that my WD did a full scan tonight without problems, so it seems that the WD updates did the fix.

Question: Does anyone using WD for Win10 know how to disable a daily scheduled scan? I haven't found a way in the security programs, or in task scheduler.

Thanks Ron, that did it. I had not drilled down far enough in the Library tree. Give yourself a "Solution".

One would think that the more logical approach for MS would be to allow one to set a WD scan schedule in the program itself ...  

@joe53  said: One would think that the more logical approach for MS would be to allow one to set a WD scan schedule in the program itself ... 

Glad that helped, but they don't want peeps disabling WD too easily...