Hmm. I remember getting this same error not that long ago. Unfortunately I don't recall why I was getting it or what I happend to make it go away.
I remember having some issues after doing some Windows Updates, but I don't recall whether these were related.
Sorry I can't help further--just know you're not the only one to see this error.
Hopefully someone else will have more info!