Hi Phil, interesting, we'll try the same. We noticed the problem appears to have happened around mid-December when the Windows Defender Antimalware client was upgraded from 4.14 to 4.18.1812.3. Did you?
We are currently running W10 v1803. Does that make any difference?
Best regards
Scott