Regedit Problem Windows 2000 pro

Warder45

Senior member
Jan 3, 2004
214
0
0
The jist is that there are 2 users who should be able to get into regedit that can't and 2 users who are not supposed to get into regedit and can. The problem is that the on the 2 users computers who can't get to it they have a registry key that is blocking them from opening it where as the 2 users who can get in don't have that key. All the rest of the users with admin permissions can open regedit and all the rest of the users without admin permissions can't. In addition all the users without admin permissions have that registry key blocking it and all admin users don't have that key.

What we thought initially was that this was a spyware issue. Many users had lots of spyware and we thought one of them might be messing with the registry. After running ad aware on one of the users machines we found that he(user who is supposed to get to regedit and can't) could then get into regedit, but if he rebooted his machine he would have to run ad aware again as the key reappeared each time blocking access. We've also changed each users groups multiple times, with no effect.

As I'm not that familiar with 2000, is there a way to look and see what permissions a user has? Perhaps even though we've changed the users groups to one with more permissions it still isn't setting the registry editing one correct? I've searched through google and microsofts help and found no answers, if anyone had a good website with help/information about 2000 that might help as well. Thanks for any help and if this is in the wrong forum mods please move it to the correct one.
 

mikecel79

Platinum Member
Jan 15, 2002
2,858
1
81
What type of permissions are you looking for? Registry permissions use regedt32. File permissions use Windows Explorer.

What is the key that is preventing them from running Regedit?
 

Warder45

Senior member
Jan 3, 2004
214
0
0
Thanks for the help but we figured it out. It's bug in windows 2000, perhaps being caused by a security patch or lastest service pack. I'm going to look an see if I can find where to tell microsoft the problem and if were lucky it may get fixed.