Originally Posted by sse1990
I would have to disagree strongly since that was the one and only key I deleted and after that my system was screwed.
I came to find out after that I was not the only one that had that problem. They also deleted the one key and the system was screwed.
But I figured I would try it since all the other fixes didn't do anything for me, this was the first one that I tried that I would have to get into regedit for, ( I ususally try and not play in the registry unless I really have to and in this case the problem hides itself in there.).
So what you are saying then is that anyone that tries your fix and screws up their system after reading this, YOU are now solely responsible for it.
I am trying to warn people that there is more to it than you think. But if you insist that there isn't and they screw up their system then you SHOULD be held responsible since you say it will not do anything.
Anytime you play with the registry you can cause some damadge so that is why I DO NOT post ANY instructions on playing with it.
Sorry to hear this solution didn't work for you. As you mention, editing the Registry should be done with care and regular back ups are a good precaution.
In your earlier post you mentioned you had edited the Registry before me having posted on this issue. Was this the same instruction or something else?
I offered a solution that has been widely tested and if you had taken the time to read through the 2 links I provided, you would have had a very good appreciation of the mechanics involved and the reasons for this approach.
I know this solution works because I have done it on 2 computers. I spent a great deal of time researching a fix and I read many instructions very carefully. I have checked 5 Windows XP systems and 2 Windows 2000 systems, all of them contain the key mentioned earlier and none of them have any values set normally, only a hidden value for CWS.
To be sure appropriate care and attention is given this matter, in case it'* not obvious, I will edit my earlier post to include a warning when editing the Registry. I'm sorry you feel I am responsible for your troubles in offering a known solution.