The only workaround is to kill the process Microsoft Windows Scripting Host.

I have attached an example screen shot.

I strongly suspect ME DC is causing this, probably when it's doing a patch scan. (or something like that)

Has anyone seen this before and have a fix?

Cheers,
Steve.