Seems like this problem was solved. The question was posted here again -> link The error above was gone after a reboot, a different error showed up -> link The new error would be resolved in this way -> link