No.
This issue was reported by many and one of the suggestions I was going to give was to wait it out. Basically they said that the issue was that there was a long delay on boot when this error came up.
This was mainly showing on Vista, but the platforms are very similar. There are the same issues on Server 2008 on google.
I would bet it was an update. We had something similar happen on one of our client's systems and we had to wait 6 hours before the update went through. Thanks M$