Ask This On A Windows 10 Dedicated Forum. It's Probably Something Simple.
As I already stated, the problem is already known by Microsoft and there have been tons of reports of this problem on the Feedback System from Windows Insider Participants. Microsoft is hopefully looking into this problem. This errors exists already since W7, so I'd be not surprised if they'd just ignore it and force us users to find a way to fix it.