New
#21
Glad it helped. New thread started on 4.18.1908.7 -- New Defender Antimalware Client Version
Seems to be a few issues cropping up for some users.
MS Posts Support Note About Defender SFC /Scannow Errors
-
-
New #22
Guess what? I realized I had periodic scanning turned off on my Enterprise PC, so I turned it back on (I use Norton on that machine, my only remaining holdout). When I turned it back on, then ran WU again, here's what I saw:
To me, that says: "Defender only updates if it's enabled for use." Good to know!
--Ed--
-
New #23
Windows Update has just downloaded the new Antimalware update. I checked Defender settings and it has been updated. So straight away I ran sfc /verifyonly. CBS log errors again! Ive looked at them and they are the same Windows Defender Powershell issues as before. I didn't reboot my PC before running sfc /verifyonly. Also, in my case I hadn't fixed the errors previously. I have just waited for Microsoft to release this antimalware update fix. I wonder if either of these things might be the problem? Should I have used DISM to fix the problem before the Antimalware engine got updated to this new version?
Quote
Related Discussions
