@figuerres there is a hotfix for that.
Scott Hanselman had written about this problem a while back. You can see it here:
The following hotfix is for .NET 4.0, not sure if it applies the patch to all versions 4 and lower.
thanks, will check that out when I can....