I got the same error this morning on my work computer. A reboot did not get the error, and everything was OK. Microsoft updates were applied to the work computer last night, so that may have been the cause.