Ok, I'm resurrecting this old thread because I ran into this EXACT problem. Jeff suggested it's a file permission problem but it's not, it's actually a bug related to KB article 930901 here: http://support.microsoft.com/kb/930901/en-us. Fortunately there's a solution which is why...