Registry editing...

Might be useful to add which OS your running Vimal.

Heres a link to a search on the problem if its any good to you

http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=Registry+editing+has+been+DISABLED+by+your+ADMIN%2E

But more importantly wherever I go Koasati follows to mop up after my mistakes, so with any luck he''ll probably be along to help soon
[Message Edited]

If you`re running Win XP, try importing this key into your Windows registry:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System]
"DisableRegistryTools"=dword:00000000

Save the above two lines into a text file (on your Desktop, for instance), naming it somethin.reg (the ".reg" is what counts). Then double-click the icon on your desktop and let it import to registry.

If this doesn`t work, you may want to try creating a separate user account, with admin privileges, log onto that one, and try running regedit. If you can, then you can load your original account''s user hive in and edit the key from there. If you need help loading the hive, write back.

The more official approach, however, is to go into Group Policy editor and change the policy from there. If you`re comfortable with that, the key path given above should point you, more or less, to where you need to go in GP editor.
[Message Edited]

Oh Hell ! I almost forgot, you REALLY need to know what you're doing when you edit the registry, so be sure you back up your registry before you do this !

Sorry if the above is a bit too technical. If so, hopefully someone can post you something more user friendly in addition to Journeyman's search suggestion above.

Yeh I think spbyot would have picked up a spyware problem but you haven't mentioned what anti-virus software your running. Just cos it might save some work you might like to try this

http://vil.nai.com/vil/stinger/

Its a locate and destroy facility for virus's (well respected). At least it should help eliminate the possibity of a virus. Its self executing so you will probably be able to run it without problems.

Oh by the way if you are running XP - state whether you have home or professional version because it may affect some of the options that you have.

If it is a result of a virus then the fixswen.inf file at this link may be the answer you need.

http://vil.nai.com/vil/averttools.asp

I know it has worked for some people with a virus but yet again its a case of horses for courses - so double check before using

Oh yeh - normally when cleaning an XP system it is necessary to disable System Restore in order to avoid re-infecting yourself at a later date.
[Message Edited]

I hesitate to suggest the obvious, but have you considered booting into safe mode first and logging on as the administrator? Then you could check to see what your actual settings are and change them if necessary. Just a suggestion.



[Message Edited]

Hi Shameless - yep there are a few possibilities, apparantly even spybot itself in advanced mode can in some circumstances trigger this event if not used entirely correctly.

Gotta say tho, were it me as a non-techie I would wanna check there wasn't a virus causing the problem, cos if there is it will probably re-occur ? - plus I may be helping to spread it.

At least if there is a known variant showing up it can be cross checked on Google to see what the cure is for any changes it may have made. If there isn't then Vimal can hopefully restore settings either from 'front of house' or the Registry and just forget about it.

Disclaimer "Any similarity to knowledge is entirely co-incidental"

I guess my take on things is kind of like the physician's creed - "First, do no harm." To extend this analogy a bit, the first thing any physician will do is assess the situation and only take steps necessary to stabilize the situation and prevent further harm to the patient. In this case, from what we know, the "patient" has a problem which is annoying but not life threatening. Recommending immediate "surgery" on the registry is not something I would offer right off the bat.

The next step is to gather information in order to make an informed diagnosis. From that standpoint, I think Journeyman's advice was a step in the right direction. Running antivirus and spyware checkers is usually good advice, in that they not only gather information, but may also correct the problem by themselves. The advice I offered also would do no harm and would help to gather information. Asking other questions about the problem also can save time in the long run and help to better diagnose the problem.

Once the information has been collected, only then should a diagnosis be attempted, and corrective actions recommended. In my opinion, even then one should start with the least radical or easiest to perform and reverse if necessary. And generally speaking, it's best to take a little more time to consider your advice before you post. And if there is a precaution involved, like backing up the registry for example, try to always put that information first instead of last. Being first to post is not nearly as important in trying to help someone as being correct.

Finally, the "doctor" needs to bear in mind her/his own limitations. If you're uncertain, say so. There is no shame in not knowing something. None of us is omniscient. Well, maybe Jafo, Yrag, IPlural, and a few others depending on the subject. P As an example, I normally don't post at all on hardware/tech type questions because I know there are others here who know far more and can better help the person. That's what community is about, balancing each other's strengths and weaknesses.

Anyway, sorry to hijack the post a bit, but these things have been on my mind for a while, it's late, and I'm bored. I'll shut up now.

By the way, my post above was not intended as some kind of slam at you guys. It was not even directed at you in particular. It's just that lately I've seen a lot of bad advice given on the boards, some of it even potentially dangerous advice. Please don't take it personally. It's obvious that you guys are sincerely trying to help. Something in Journeyman's last post just triggered the thought process, and I got the urge to speak my piece.

And now I really will shut up.

I think you''d find general agreement Shameless. I wouldn''t dare to advise anyone to make any registry changes based on the scant information available. However was happy to provide links to possible solutions. I know some folks don''t have the degree of access to the net that others have and so endlessly using Google can be prohibitive - so if I can short cut that to a degree I am happy to do so. I guess to be honest one of the things I''d do, even before backing up the registry would be to back up the things I really wouldn''t want to lose, including licences/registration info, screenshots of various configurations for reference etc.

Then if there was no other choice begin on the registry (backing up first in ways I felt confident with and understood how to recover by) with information I needed printed or written out - at least that way the very worst that should be ahead of me is a reformat, some work and probably an education. .


I''m just hoping we find out what happens in the end
[Message Edited]

Yep, I was a little late in qualifying my advice, that's for sure.

In any event, I think at least looking at Group Policy or the relevant registry key FIRST would yield VITAL information in diagnosing the problem.

And, yes, I have indeed predicated all of this strictly based on my experience with Win XP.

Hope IP writes back soon with more info.

hello all.
thanks for your suggestion i am busy trying all of them out...
oh sorry i was in a hurry and i forgot to mention my OS: WinXP

I tried loggin in as the Admin in safe mode, i got through, i am able to open Regedit but i didnt know which key to modify so, i thought i better not!!

And,, the Journeyman! i forgot to have check GOOGLE first! thanks!!

and btw, i got it right. i found a VB Script to do it all...
heres the VBS if u might need it

'Enable Registry Editing
'© Veegertx - 06/27/2003
'This code may be freely distributed/modified
On Error Resume Next
'Prevents errors from values that don't exist
Set WshShell = WScript.CreateObject("WScript.Shell")
'Delete DisableRegistryTools registry values

WshShell.RegDelete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools"
'display message
Message = "You should have access to Regedit now"

X = MsgBox(Message, vbOKOnly, "Done")
Set WshShell = Nothing
Set fso = Nothing

Cheers for coming back Lord Vimal - yeh let us know how it works out - I'm not good with scripts and while I think I understand what it's saying I'm not about to prove I'm wrong here .

Glad to see you found a user-friendly way to change precisely the key I was talking about, with "no harm done".

The best followup on this would be to check that you still have access once in awhile in case it recurs and you need to figure out if you''re unwittingly changing it yourself or if some maleficent other factor is to blame.

Good luck !
[Message Edited]