The exact same thing just happened to me. The Avast program said it found a vbs:flufferminer-D virus in the same windows defender folder as what you said, and I too had just updated my Windows 7 with about 12 new updates just hours before. Got rid of it and then did the recommended boot scan. Said it had now reappeared in a Windows file, and was I sure I wanted to delete it. It was in the Avast folder that resides in the Windows folder, so I quarantined it with no ill-effects. So it seems to me that Avast isn't recognizing something in one of the new Windows updates for what it really is and it thinks its something bad. I mean, what are the chances of that Windows Defender file being corrupt direct from Microsoft and then only people with Avast get it...? Never happen.