Editing the registry is prohibited by the system administrator: what to do

Any user of a modern computer system eventually comes to understand how Windows works. Sooner or later it will happen. To personalize the settings or fix many problems, you can change the key settings and registry entries. But what if the user, say, with the installed "seven" suddenly receives a message stating that editing the registry was prohibited by the administrator of the Windows 7 system? Let's look at the majority of situations and the reasons that lead to them.

How to understand that editing the registry is prohibited by the system administrator

First of all, any user, regardless of the level of training, should be aware that the Windows Registry Editor works somewhat differently than other applications.

The simplest example: when making changes, any other program prompts the user to save them. But not the registry editor. If something is changed, even the usual exit from the program results in automatic saving of changes.

But the appearance of a warning like "Editing the registry is prohibited by the system administrator" (Win 7, 8, 10 or the explicitly aging XP OS) can be associated with a variety of reasons. And this can not always be connected even with the lack of administrative access rights to the computer terminal and the main or hidden functions of the "operating systems" themselves.

The causes of such situations

Let's say that the terminal has a Windows XP system that allows several authorized users to work on one computer under their accounts. It goes without saying that besides them there is also a computer administrator, whose "accounting" allows you to change absolutely all the parameters of the system.

It is clear that the administrator can impose some restrictions on users' access to certain functions, so that they, for example, by their inexperience, God forbid, did not make any critical changes to their own settings. On the performance at the entrance to the admin, in principle, this may not be reflected, but the user settings can simply "fly off", and quite elementary. That's why the administrator blocks access to these functions, as a result of which the user is faced with the problem that the registry editing was prohibited by the administrator of the Windows XP system. By the way, this applies equally to all Windows modifications.

Almost the same prohibition can be manifested in the case when several computer terminals are united in a local network. As you know, management of health and configuration of such networks is entrusted to system administrators. And they set the settings in such a way that users of local machines could not get to that before changing the settings set by the default sysadmin, but also to critical changes in the same system registry. That's why instead of the message, say, in the usual "ekspishke", the user when they try to access the Registry Editor with the introduction of the regedit command in the "Run" menu or on the command line itself (the cmd command) and gets the system response in the form of editing the registry It is forbidden by the administrator of the XP system, but that access is blocked at the level of the sysadmin responsible for the "localization" functionality.

But there are other situations. Imagine the simplest version: the user works in the installed system himself, the other users on the "computer" is not registered, that is, he is himself an administrator. And suddenly, for no reason at all, he receives a message stating that editing the registry was 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 came to understand the essence of the operation of Windows. Some of these applications can block access to the system functions of "Windows".

Some virus writers do this from the fact that there is nothing to do, some - just for the sake of interest, to check the system for vulnerability, and at the same time and their abilities, some just try to get into someone else's computer and make their own changes. The bottom line is not that.

Again, with such unauthorized exposure, there may be a problem with the fact that the screen displays a notice of the current restrictions, in particular that the administrator has prohibited the editing of the registry.

There is only one way out - an immediate system scan by an established anti - virus scanner, or, better - utilities such as Rescue Disc, allowing you to scan the computer in depth for viruses before the operating system boots from the hard drive itself. Such utilities are run either from the optical or from the USB-medium ... Naturally, in the BIOS settings they will need to be specified as the first priority device for launching (calling by the keys Del, F12, F2, etc. - everything depends on the brand of the computer or laptop , As well as from the developer of the BIOS).

Editing the registry is prohibited by the system administrator: what to do

Now we, in fact, come to the question of finding solutions and correcting such situations. In principle, there are a lot of solutions to this problem today: from Windows own tools to the use of third-party utilities. Now we will focus on the simplest ways to fix problems, for example, in the same "Seven", connected with the fact that editing the registry was prohibited by the administrator of the Windows 7 system (today this OS is the most common and in demand for the majority of users).

Using the Group Policy Client

If someone does not know, some elements of the system registry responsible for accessing the system functions in the same "seven" are duplicated by the client service of local and group policy. As a rule, the sysadmins do not block it, considering that the user does not know how to get to it. Let's talk at once: if the client is blocked, this method will not work.

However, if the user received a message stating that editing the registry was prohibited by the system administrator, you can call the command line or the "Run" menu and enter gpedit.msc in the corresponding field.

Next, you'll find a branch of the settings in which the right-hand side will contain a bar for access to the registry editing tools. Here you need to select the submenu called by the right click, and use the command to change the settings, after which, in fact, put the "bird" opposite the trip parameter, and then save the changes.

Using Symantec tools

A well-known corporation Symantec, once stood at the origins of computer security, offers its solution.

On the official resource, you simply need to find and download to the computer a small file called UnHookExec.inf, which after launching can remove all restrictions on access to the Windows registry editor. Its start involves using the 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

No less effective way when you receive a message that the registry editing was prohibited by the system administrator is the use of the command line, albeit in a somewhat specific way.

First, in a console similar to DOS, you need to enter the string shown in the illustration and press the Enter key. The registry will be unlocked.

If this is not enough to not enter the command permanently, you can simply copy this code into the standard "Notepad", and then save the contents as an executable file with the .bat extension. In Windows XP, for example, to run the item, it will be enough to double-click, in versions of Vista and above, the file must be run with the right-click on behalf of the administrator.

Conclusion

Actually, on this consideration of the problem can and finish. Of course, here are only the most common reasons for its appearance and the most popular ways to eliminate it. For example, we did not consider the question of how to log into the system under the admin in the same "exishka", although this is done at the level of any user completely elementary. But for most cases, it is recommended to use either the Group Policy client (if it is not blocked), or downloading and running the file from Symantec. The second option is much simpler.