Appears to be, but my machine is in a delayed release group for the Windows 10 May 2020 update, so it's possible the issue will be fixed when MS rolls out the May 2020 update to everyone.
Just a quick heads up, running Windows Update to update the Defender definitions did indeed fix this issue for me
