We've been seeing similar issues lately (different error messages), seemingly due to something in the latest Win10 update when desktops get updated. If your (Win10) desktop was recently updated with a new OS build, then this knowledge base article may help: