- yes, but they seemed all to be for software authors.
At least I didn't understand any of it.
The closest I came was the answer to a related but not identical problem:
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product $upport $ervices to obtain the hotfix.
Somewhere somehow I get the impression that the error has to do with .NET Framework. Only thing is, my Frameworks (1.1 and 3.5 SP1) have apparently not been changed recently.