At least 2 users I know of had this problem and it was due to the Windows 10 2004 update. Uninstalling it fixed it, but they didn't try to reinstall the update to see if the update just failed to install properly the first time.