I've seen this error a couple times. Each time logging in as a different user(in AC, not Windows), then logging out and returning to my normal user seemed to fix it. Worth a try...