Windows 10 - Defender Offline Scan not working

Now windows defender is working fine, it just takes few minutes to restart the pc, downloading updates and starting the scan. 

All that i did is updating to the latest windows 10 fall creators update.

Hi Marv,

Found this thread at the top of the list, due to your current posts.

You do not say what your current W10 version is. This thread was

started some time ago, when WDO actually had some problems.

Most recent of which, was caused by certain updates that were

released for W10 version 1703. However, version 1709 corrected

that problem, and WDO seems to be working just fine at that

version for me.   What kind of symptoms do you have?

NOTE: Until recently, it was also possible to run WDO on W10

   computers using a Media USB, created using the Mssstool that

   applied to W7. It appears, that is no longer possible. Attempts

   to use the USB method now, results in an error 0x8004cc01.

   Looks like Microsoft may have modified the WDO program, again.

That aside, the internal WDO program seems solid at v1709

build 16299.64.

Regards,  Glen

Thanks for this - I'm leaning towards a refresh or worst case reinstall of windows

Hi Julie - thanks for the response - I have tried all the other steps in this thread, via powershell etc. I currently do not have a USB key so haven't been able to try running it on start up (however do believe this would work). Prior to my issues windows did dectect a trojan and Malwarebytes also picked up suspect registry keys and other PUPs.

I am thinking of doing a PC Refresh as there still seem to be small issues and my last windows 10 update did not run sucessfully - I am trying this first:

https://www.microsoft.com/en-us/wdsi/products/scanner#

Windows security scanner - however have had issues downloading the file as of now - the download is continually interupted/does not complete.

The only thing that worked was to join the Windows Insider Program.  It sends out W10 updates/rebuilds.  And one of them fixed the issue.  So I suppose if I reinstalled W10, that might have worked. But doing so is a little intimidating and I didn't want to risk my existing content.  Wimp.