Eventually thanks to you people I have managed to find out what this exception error means. I have exactly the same problem. Is Microsoft releasing a patch for the wheel or just ignoring the problem?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.