Any user of a modern computer system ultimately comes to understand how Windows works. Sooner or later this will happen. It is possible to personalize settings or fix many problems precisely by changing the parameters of keys and registry entries. But what if suddenly the user, say, with the installed “seven” receives a message stating that registry editing is prohibited by the Windows 7 administrator? Let's look at most situations and the reasons leading to them.
How to understand that registry editing is prohibited by the system administrator
First of all, any user, regardless of the level of preparation, should be aware that the Windows registry editor works somewhat differently than other applications.
The simplest example: when making changes, any other program asks the user to save them. But just not the registry editor. If something is changed, even a normal exit from the program automatically saves the changes.
But the appearance of a warning like “Editing the registry is prohibited by the system administrator" (Win 7, 8, 10 or a clearly outdated XP OS) can be due to many reasons. Moreover, this can not always be connected even with the lack of administrative access rights to the computer terminal and the basic or hidden functions of the “OSes” themselves.
The causes of such situations
Suppose that Windows XP is installed on the terminal, which allows several authorized users to work on the same computer under their own accounts. It goes without saying that in addition to them there is also a computer administrator, whose "account" allows you to change absolutely all system parameters.
It is clear that the admin can impose some restrictions on users' access to certain functions, so that, say, by their inexperience, God forbid, not make any critical changes to their own settings. In principle, this may not affect the performance when logging in as an administrator, but user settings can simply “fly off”, and quite simply. That is why the administrator blocks access to these functions, as a result of which the user is faced with the problem that registry editing is prohibited by the Windows XP administrator. By the way, this applies equally to all modifications of Windows.
Almost the same prohibition can occur in the case when several computer terminals are connected to a local network. As you know, the management of the health and configuration of such networks is assigned to system administrators. And it is they who set the settings in such a way that users of local machines could not get to not only change the settings specified by the system administrator by default, but also to critical changes in the same system registry. That's why instead of a message, say, in the usual “e-book”, the user, when trying to access the registry editor with the regedit command in the Run menu or on the command line itself (cmd call command), receives a system response in the form that editing the registry it is forbidden by the XP system administrator, but that the blocking of access is carried out at the level of the system administrator, who is responsible for the operation of the “LAN”.
But there are other situations. Imagine the simplest option: the user works in the installed system himself, other users on the "computer" is not registered, that is, he is his own administrator. And suddenly, for no reason, he receives a message stating that editing the registry is prohibited by the system administrator? How so? He is the administrator! What is the reason for this? First of all, with the manifestation of the activity of virus programs, less often - with the installation of any specific applications.
And if it's a virus
Indeed, modern viruses and the people who create them today have come to understand the essence of Windows. Some of these applications are able to block access to the system functions of Windows.
Some virus developers do this because there is nothing to do, some just for fun, to check the system for vulnerability, and at the same time their abilities, some just try to get into someone else's computer and make their changes. That’s not the point.
Again, with such unauthorized exposure, a problem may arise due to the fact that a notification about the current restrictions appears on the screen, in particular, that editing the registry is prohibited by the system administrator.
There is only one way out - an immediate scan of the system with the installed full - time anti - virus scanner, or better, with utilities such as Rescue Disc, which allow you to perform an in-depth scan of your computer for viruses even before the OS itself boots from the hard drive. Such utilities can be launched either from optical or from a USB drive ... Naturally, in the BIOS settings they will need to be specified as the first priority device to start (calling with Del, F12, F2, etc. - it all depends on the brand of the computer or laptop , as well as from the BIOS developer himself).
Editing the registry is prohibited by the system administrator: what to do
Now, in fact, we are approaching the issue of finding solutions and correcting such situations. In principle, today there are quite a lot of solutions to this problem: from Windows native tools to using third-party utilities. Now we will focus on the simplest ways to troubleshoot problems, for example, in the same "seven" related to the fact that editing the registry is prohibited by the Windows 7 administrator (today this OS is the most common and in demand among most users).
Using Group Policy Client
If anyone does not know, some elements of the system registry that are responsible for accessing the system functions in the same "seven" are duplicated by the client service of local and group policies. As a rule, system administrators do not block it, assuming that the user does not know how to get to it. Let's make a reservation right away: if the client is blocked, this method will not work.
Nevertheless, if the user receives a message stating that registry editing is prohibited by the system administrator, you can call the command line or the Run menu and enter gpedit.msc in the corresponding field.
Next, find the settings branch, in which on the right there will be a line prohibiting access to registry editing access tools. Here you need to select the submenu, called by right-clicking, and use the command to change settings, after which, in fact, put a “bird” in front of the disconnect parameter, and then save the changes.
Using Symantec Tools
The well-known Symantec Corporation, once at the forefront of computer security, offers its solution.
On the official resource, you just need to find and download to your computer a small file called UnHookExec.inf, which after launch is able to remove all restrictions on access to the Windows registry editor. Its launch involves the use of a right click, after which the installation command is selected from the menu (by the way, some drivers are installed manually in the same way).
Command line
Using the command line is a no less effective way when you receive a message that editing the registry is prohibited by the system administrator , although in a somewhat specific way.
First, in a console similar to a DOS system, you need to enter the line shown in the illustration and press the enter key (Enter). The registry will be unlocked.
If this is not enough, so as not to enter the command all the time, you can simply copy this code to the standard Notepad, and then save the contents as an executable file with the extension .bat. In Windows XP, for example, a double click will be enough to launch an item; in versions of Vista and above, you need to start the file with a right click as administrator.
Conclusion
Actually, this can be the end of the consideration of the problem. Of course, here are only the most common causes of its occurrence and the most popular ways to eliminate it. For example, we did not consider the question of how to enter the system under the administrator in the same “e-book”, although this is done at the level of any user quite simply. But for most cases, it is recommended to use either the Group Policy client (if it is not blocked) or downloading and launching a file from Symantec. The second option is much simpler.