The only solution I had so far was disabling the I have spent months researching this (without success), the problem is when you search for this error you only find generic regurgitated garbage like from the first response here which doesn't help at all. Of course, finally documenting a problem after people have been suffering for almost a year is the most we can expect from Microsoft: Actually FIXING the problem in the source code would affect the bottom line too much. Deleting those registry keys mentioned by JS36688 has finally fixed this problem, which has been driving me nuts for about nine months! I have no idea where JS36688 has found the solution, but now after a so many months, Microsoft has documented
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |