Has anyone mentioned before that this is probably an issue with Microsoft changing something on a Service Pack or Hotfix?

I have the same issue, but I'm dealing with...