Windows 10: Windows Defender Drops Error 0x80070578

My computer won't boot to windows from windows defender offlineMy Windows 10 is not able to Login Due to DefenderWindows Defender Offline for Windows 10How do I get my computer to boot up regularly after running the WDO scan?

Within part 1 (see Windows 10: Windows Defender drops error 0x80070578) I mentioned Windows Defender error 0x80070578, that is based on outdated Windows Defender signature files. As mentioned above, Windows Defender Offline (WDO) is able to load new signature filtes via internet. I suppose, that third party antivirus software (Mc Afee, Norton, Kaspersky and so on) deactivates Windows Defender. So WDO isn't able to update his signature files. Maybe non compatible versions of antivirus software are responsible.

Windows 10: Windows Defender drops error 0x80070578

Download

An alternative is: booting the machine in Windows PE (using a system repair disk, CD, as recovery drive, USB stick, or a Windows 10 install media and entering computer repair option). In Windows PE it's possible to copy user files via command prompt windows from the Windows disk to an external media (USB stick or USB drive).

Unfortunately I had the windows defender offline (WDO) boot loop too. The computer was unusable. The files were saved, the bios was set to UEFI native without CSM, also using the bios the internal hard drive was sanitized, the windows 10 was reinstalled along with drivers, files and applications.

1) test the drivers on your computer using windows driver verifier2) this is a microsoftanswers WIKI on steps to use windows driver verifier -us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c9833)all of my computers immediately produced windows driver verifier blue screens with stop code: windows driver verifier detected violationThere may or may not be additional information that my display the problematic driver. It typically ends with .sys4) if you want to fix the drivers you can record the driver and then uninstall and reinstall the driver. Some additional ways to get blue screen information are to the change the settings to get minidump and memory.dmp files. This information is available in this microsoftanswers wiki: -us/windows/wiki/windows_10-update/bsod-finding-and-fixing-them/1939df35-283f-4830-a4dd-e95ee5d8669d5)once you have experienced on driver verifier produced blue screen then exit windows driver verifier using the troubleshooting menu choice start up options. Of the 9 listed choices choose choice 6 safe mode with command prompt. There you enter verifier /reset and then reboot to the desktop.6) When you are back on the desktop open windows defender. In the right upper corner click on settings. And in the pop up windows click windows defender offline (WDO).7) Upon reboot WDO will load and then run a quick scan offline. Then reboot to the desktop8) So far everything should be back to normal and you should be on the desktop. You have run windows driver verifier once and it has produced a blue screen. You have exited windows driver verifier and returned to the desktop. You have run windows defender offline once and have also returned to the desktop. Both windows driver verifier and windows defender offline have each required reboots.9) this is the step that has reproduced the WDO blue screen boot loop. You now run windows driver verifier a second time.10) no longer can you get to the advanced troubleshooting options. No longer can you turn off windows driver verifier. You are now stuck in a windows defender offline blue screen boot loop. All power ons lead to a windows icon with rotating dots and blue screen with stop code driver verifier detected violation. Then all power off followed by power ons again lead to windows icon with preparing automatic repair followed by WDO load then WDO quick scan. The scan can be canceled or the scan can run to completion however it results in another blue screen.

All of the troubleshooting steps failed. Unfortunately the windows 10 bootable iso does not have the same troubleshooting menu as your computer. The start up options are missing. There is no safe mode with command prompt.

At first I wondered whether WDO was like Norton or Mcafee and other antivirus programs where any residual software after control panel uninstallation could interfere with other software programs. As far as I know there is no software to uninstall WDO like the other antivirus programs. And at first I thought that windows driver verifier had found a residual file of WDO to make the boot loop.

Let me know if you are able to use windows driver verifier to reproduce the WDO boot loops. For me all of the computers had an initial blue screen. I don't know if the WDO boot loop will occur if the first windows driver verifier does not produce a blue screen.And let me know if you can fix the boot loop by using diskpark.

2ff7e9595c