The png picture you provided **is** the WDO scan.
Once the scan is complete, the device restarts.
- this scan, then restart is normal and unlike earlier Win10 1703 or earlier 1703 Insider Builds
Actually, that is not true.
Firstly, as I said, it worked before, showing me first that window, then the actual scan.
Secondly, that window stays for about 2 minutes (if the subsequent scan fails, otherwise it's less ; I've been thinking it may have something to do with updating the definitions), while a WDO-scan of even a new computer with an almost empty harddisk takes
some 5 minutes.
Thirdly, acting on a suggestion from someone on another thread, I uninstalled the "2017-06 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4022716)" from June 28 I mentioned above, after which WDO worked normally again : first the
window in the picture I provided, then the actual scan.
I then reinstalled the update, expecting WDO to fail again afterwards (which it didn't), but the update that was 'reinstalled' was "KB4022725", which is the same number as a cumulative update installed on June 13, while "KB4022716" seems to remain uninstalled.
WDO is now again working normally as before.
It is not my intention to antagonize you (or anyone, for that matter), but is it not a bit hazardous to say "[that] **is** the WDO scan", especially towards less experencied users who then think they are safely running a scan and their system is clean, while
there actually is no scan being performed ?
Kind regards,
John.
Edit : for clarity, when WDO works normally, this is the window I first get :
https://www.groovypost.com/wp-content/uploads/2013/04/WDO-Launching.png
After about 30 seconds, this disappears and the scan window appears, looking something like this :
https://alssl.askleomedia.com/wp-content/uploads/2017/02/wdo-running.png
where I can click on the Update tab, minimize, maximize, ...