![]() Sure I could restore a full backup image I have to prove that Microsoft Defender Offline Scan worked prior to the update but who would really be interested in that proof? I mean I literally have no indication that any corruption exists anywhere throughout the OS yet something that worked before the Cumulative Update is now broken and not a peep of it has been mentioned in any documentation that I came across lately that it is a known issue with the November 11th Cumulative Update for systems on 20H2. Some articles suggested a repair install but honestly at this point, if sfc /scannow isn't flagging anything and my OS is completely operational with no Event Viewer Errors and no Reliability History issues of any kind (especially Critical Events) I really can't justify using a repair install that probably will not fix it either. Yes, I rebooted after the DISM Restore Health Command. The second thing I tried was a Restore Health function with the DISM command and it reported a successful operation and still the Offline scan won't initiate. After hours of extensive reading about how WDO and now Microsoft Defender Offline scans are not working for some since as far back as 2017 for Windows Defender Offline, I had removed all remnants of Malwarebytes from my registry in an attempt to see if any of those entries were conflicting with the Microsoft Defender Offline Scan. I'll give this thread a little bump and explain what I have tried so far to no avail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |