How to Enable the Registry Editor When Disabled by Administrator
Registry Editor, a main registry editing tool equipped in all versions and editions of Windows operating system, can be disabled, blocked and locked to prevent the RegEdit from been ran or executed by users in order to protect important system registry. Other possibility of Registry Editor been disabled is caused by virus or worm such as W32/Brontok-C.
When Registry Editor is disabled, user unable and cannot open or run Registry Editor anymore. Any attempt to run RegEdit.exe will return the error “Registry editing has been disabled by your administrator”. Hence it’s impossible to remove the restriction on Registry Editor usage by using the Registry Editor itself. However, it’s possible to use various workaround to directly edit the registry to remove the policy that blocks Registry Editor usage.
Enable Registry Editor using Local Group Policy Editor
For user using Windows XP Professional, Windows Vista Ultimate, Windows Server 2003 or 2008 with Local Group Policy Editor and has access to an administrative user account, user can change the registry editor options in the Local Group Policy Editor.
- Click on Start -> Run (or Start Search in Windows Vista).
- Enter GPEdit.msc and then press Enter.
- Navigate to the following location:
User Configuration -> Administrative Templates -> System
- In the Settings pane, locate the Prevent access to registry editing tools option, and then double-click on it to open the settings dialog.
- Select Disabled or Not Configured.
- Click on OK button.
- Try to run RegEdit.exe, and if required (still blocking yet), restart the computer.
VBS Script to Enable or Disable Registry Editor
Doug Knox has created a .vbs VB script that able to toggle between enable or disable the Registry Editor. Right click to download and save the regtools.vbs into a folder. Then double click on the VBS file to run it.
The regtools.vbs VB script file will check for the appropriate value related to disabling/enabling of Registry Editor. If the registry key is not found, the key will be created to disable Registry Editor. If the value was found, it will be toggled to its opposite state and you will be informed that you need to log off and log back on or restart your computer. All change by the script is made in HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System.
UnHookExec.inf by Symantec to Reset Registry Values to Default Settings
In many cases, disabling of Registry Editor is caused by virus, worm or Trojan, which attempts to stop user from fixing any changes to the registry, which normally affects changes to one or more of the shell\open\command keys. For example, exefile\shell\open\command key is changed, the virus, worm or Trojan threat will run each time that system run any .exe file. As such, Symantec create a .inf script tool to reset these registry values to their default settings.
WARNING: The UnHookExec.inf will reset registry keys and values related to BAT, COM, EXE, PIF, REG and SCR extensions, beside re-enabling the Registry Editor. Hence, users who just want to re-enable the Registry Editor has to manually modify the .inf file to remove the unnecessary commands.
Download the file UnHookExec.inf and save it to your Windows desktop.
Right-click the UnHookExec.inf file and click install. Action will be taken immediately. No display, nor any notice or boxes will appear before or after running. Try to run RegEdit.exe again, restart and reboot PC if it’s still blocked.
Related Articles
- How to Disable Registry Editor Editing Tool (RegEdit)
- Mobile Registry Editor (MRE) Free Download to Remotely Edit Pocket PC Windows Mobile Device Registry
- Workaround to Install PHM Registry Editor in Windows Mobile 5 and 6 (WM5 and WM6)
- Download and Install Free PHM Registry Editor for WM5 (Windows Mobile 5) Devices
- Activate, Enable and Show Administrator Account in Vista Welcome Screen
- Enable and Unhide Administrator Account with Vista Local Security Policy Setting
- Enable or Disable Built-in Administrator Account in Windows Vista
- CeRegEditor Free Desktop Based Registry Editor for Windows Mobile and CE (Pocket PC) Devices
- Enable and Install Windows 7 Regional Themes and Wallpapars via Registry Hack
- How to Remotely Enable Remote Desktop (Terminal Services or RDP) via Registry in Windows 2000/XP/2000/Vista/2008
Entries (RSS)
November 2nd, 2009 15:17
thanks to UnHOOkexic file, it helped me alot
:-bd
October 20th, 2009 01:22
very very thank you
befor my pc d’not show hidden file
after my pc show
ok
October 13th, 2009 18:51
thank u so much..really helped
October 8th, 2009 10:31
i can’t find system under administrative templates.
help please..
October 2nd, 2009 02:48
when i try to do this “cannot edit DisableCMD: error writing the values new contetns” pops up
August 30th, 2009 19:26
Thnx a lot the UnHookExec.inf works,thx a lot
July 31st, 2009 02:20
Discovered: May 7, 2004
Updated: December 14, 2005 12:00:00 AM
Type: Removal Information
As part of their routine, many worms and Trojans make changes to the registry. Some of them change one or more of the shell\open\command keys. If these keys are changed, the worm or Trojan will run each time that you run certain files.
For example, if the \exefile\shell\open\command key is changed, the threat will run each time that you run any .exe file. This may also stop you from running the Registry Editor to try to fix this.
They may also change a registry value so that you cannot run the Registry Editor at all.
Symantec Security Response has created a tool to reset these registry values to their default settings.
WARNING:
Do not use this tool unless:
A Symantec technician or document directs you to do so.
After reading the removal instructions in the writeup, you are sure that the tool is required.
Follow these steps:
Download the file UnHookExec.inf and save it to your Windows desktop.
(If you cannot connect to the Internet from the infected computer, download to an uninfected computer then save it to a floppy disk. Then take the floppy disk and insert it in the floppy disk drive of the infected computer.)
Note: The tool has a .inf file extension.
Locate the download file, either on the Windows desktop or the floppy disk.
Right-click the UnHookExec.inf file and click install. or copy and paste in u r note pad save as UnHookExec.inf and save in side u r admin folder or whatver u r acount name it and clilck it here is code
[Version]
Signature=”$Chicago$”
Provider=Symantec
[DefaultInstall]
AddReg=UnhookRegKey
[UnhookRegKey]
HKLM, Software\CLASSES\batfile\shell\open\command,,,”"”%1″” %*”
HKLM, Software\CLASSES\comfile\shell\open\command,,,”"”%1″” %*”
HKLM, Software\CLASSES\exefile\shell\open\command,,,”"”%1″” %*”
HKLM, Software\CLASSES\piffile\shell\open\command,,,”"”%1″” %*”
HKLM, Software\CLASSES\regfile\shell\open\command,,,”regedit.exe “”%1″”"
HKLM, Software\CLASSES\scrfile\shell\open\command,,,”"”%1″” %*”
HKCU, Software\Microsoft\Windows\CurrentVersion\Policies\System,DisableRegistryTools,0×00000020,0
(This is a small file. It does not display any notice or boxes when you run it.)
Follow any other instructions for the threat that you are trying to remove.
June 2nd, 2009 11:52
While I can’t say I have had luck with this web page. The tips are valid however the Symantec file and the VBS script keep only coming up as text files.
May 20th, 2009 22:02
my pc with vista business was attack by jambanmu.com, flash.10.exe and macromedia.10.exe.
all desktop are blank (black screen). start button and task bar are disappear. cannot run regedit.
i’m totally lost
March 7th, 2009 13:07
works great, thanks for this
February 22nd, 2009 03:48
thanx!
February 13th, 2009 12:04
what to di when both regedit and gpedit.msc are diabled by administrator which happens generally.
December 23rd, 2008 17:10
not bad, but that doesn’t work if the user isn’t able to run gpedit.msc.
Most of the admins restrict this too.
December 23rd, 2008 13:34
symantec’s tool is very useful when registry is disabled,it also easy to use for beginers.
December 23rd, 2008 02:12
[...] registry, and will not be able to use Regedit to undo the change. However, there are workarounds to re-enable the Registry Editor after [...]