Just a quick heads up, running Windows Update to update the Defender definitions did indeed fix this issue for me
