Does anyone know if any NT service packs fix this problem or if there is anything simple a user can do to fixed the problem described in the Microsoft Article...
The article contains a workaround that it says will solve the problem. Have you tried it?
BTW, that article was only updated on 30th Oct this year - if there was an easier way of solving it (ie, a Service Pack fix) then I would assume they would have put that on there.
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.