Running Regedit

Running Regedit

You won't find a shortcut to Registry Editor (Regedit) on the Start menu. You don't want to find a shortcut to Regedit on the Start menu. Imagine what life as an IT professional or a power user who supports friends and relatives would be like if Microsoft advertised this program to every Windows user on the planet. That's one reason why you find so little documentation about Regedit in Help or elsewhere. That's also why Windows provides policies that you can use to limit access to Regedit. IT professionals and power users have great need for Regedit, however—it's often the only way to fix a problem or customize certain settings. For example, I recently used a program that changed critical settings while it was running and then restored them when the program shut down. Unfortunately, the program crashed without restoring the settings, and the only way I could get them back to their original values was to edit the registry. Sometimes, it's the only tool for the job.

NOTE
Regedit and Registry Editor are terms that mean the same thing. Regedit.exe is the name of Registry Editor's program file. “Regedit” is easier to type, say, and read, so I will use this term for Registry Editor throughout the remainder of this book.

Regedit is in %SystemRoot%, C:\Windows on most computers. Click Start, click Run, and type regedit to run Regedit. You don't have to type the path. If you want to start Regedit even more quickly, drag Regedit.exe to your Quick Launch toolbar or to the Start button to add it to the top of your Start menu.

IT professionals can prevent users from running Regedit. They can set the Disable registry editing tools policy in Group Policy, local or otherwise. When users try to run Regedit, they see an error message that says, “Registry Editing has been disabled by your administrator.” Although it's probably not a good idea to prevent the setup program from installing Regedit.exe, you can set the Regedit.exe file's permissions to prevent users from running it, or better yet, you can use Software Restriction Policies to prevent users from running Regedit.exe, regardless of the file's permissions or the users' rights.

NOTE
For more information about Group Policy and Software Restriction Policies, see Chapter 18, “Fixing Common IT Problems.” To learn the best way to deploy file and registry permissions, see Chapter 8, “Configuring Windows Security.”

NOTE
Administrators shouldn't rely on any of these methods to secure the registry completely. These simple barriers don't stop determined users from gaining access to the registry. For instance, users can download shareware registry editors, most of which don't honor the Disable registry editing tools policy. Shareware registry editors also circumvent Software Restriction Policies and permissions that you apply to Regedit.exe. In reality, determined users will always find a way to access the registry, so part of the solution must be a corporate IT policy that you clearly communicate to users.