You’re not alone: there was a Windows [10] update a few days ago which appears to be responsible for this problem, see …