Registry Editing Warning
Yes!!! Editing the registry is a very dangerous activity. Especially if you know not what you're doing — you could utterly destroy your computer. However, quite often it's the only way to get a neat feature, special behavior, or even a FIX, out of your Window's system. Even more often, for the knowledgeable, it's simply a quick and efficient way to TWEAK the system. But since editing the Windows registry is such a sensitive endevour, any article at Microsoft's website that even makes mention of editing the registry is accompanied with some IMPORTANT NOTICE or WARNING that usually reads something like this:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To edit the registry, Microsoft recommends that you follow the steps in the Microsoft documentation only. If it is possible, use the Windows user interface instead of directly editing the registry.
Or something like:
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Which does indeed link to a great starting point to learn more about your Windows registry.
Here it is again (in case you missed it):
256986 Description of the Microsoft Windows registry
Below is an excerpt:
. . .
Information about editing the registry
To edit the registry, Microsoft recommends that you follow the steps in the Microsoft documentation only. If you can, use the Windows user interface instead of directly editing the registry.
You can edit the registry by using Registry Editor (Regedit.exe or Regedt32.exe). If you use Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. Microsoft does not guarantee that problems that you cause by using Registry Editor incorrectly can be resolved. Use Registry Editor at your own risk. For additional information about the differences between Regedit.exe and Regedt32.exe, click the following article number to view the article in the Microsoft Knowledge Base:
141377 Differences between Regedit.exe and Regedt32.exe
Before you modify the registry, make sure to back up the registry, and make sure that you understand how to restore the registry if a problem occurs. For additional information about backing up and restoring the registry, click the following article numbers to view the articles in the Microsoft Knowledge Base:
322756 How to back up, edit, and restore the registry in Windows XP and Windows Server 2003
322755 How to back up, edit, and restore the registry in Windows 2000
323170 How to back up, edit, and restore the registry in Windows NT 4.0
322754 How to back up, edit, and restore the registry in Windows 95, Windows 98, and Windows Me
. . .
Alternatively, you can learn about registry editing off-line from the Registry Editor's Help that's on your computer...
To open your Registry Editor's Help, click Start, click Run, type %systemroot%\Help\regedit.chm, and click OK.
But no matter what you decide to read on the subject, it seems you still won't be able to get away from those warnings. Even the Microsoft Help files on your computer that discuss registry editing will warn you of the dangers:
Caution
- Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer.
On the lighter side, there is a humorous article at Microsoft® TechNet about the "Tweakomatic" which has a section called
"I Thought We Weren't Supposed to Change Settings in the Registry?" — with great satire that reads:
. . .
I Thought We Weren't Supposed to Change Settings in the Registry?
As you probably know, Microsoft has a sort of love-hate relationship with the registry. The registry is the configuration database for Windows and Windows applications, and many options can only be set by manually changing a value in the registry. For example, if you've ever read a Microsoft Knowledge Base article, you've likely seen a sentence similar to this:
To correct this problem, change the following value in the registry.
Now that's fine, except that this sentence is invariably followed by a disclaimer similar to this one:
Warning: Don't ever change a value in the registry. Ever. We know we just told you to do that, but would you jump off a cliff if we told you to? Don't ever change a value in the registry. Don't even say the word registry. We know a guy once who said the word registry, and three days later he was hit by a bus. True story. As a matter of fact, you shouldn't even have a registry on your computer. If you suspect that you do have a registry on your computer, call us and a trained professional will be dispatched to your office to remove the registry immediately. If you accidentally touch the registry, wash your hands with soap and water and call a doctor. Do not swallow the registry or get it in your eyes!
Now, to be honest, some of those fears are a bit exaggerated, and the disclaimer is there largely for legal reasons (remember, this is the day and age when you can order hot coffee in a restaurant and then sue the restaurant when the coffee they give you turns out to be, well, hot). If you do it correctly, changing the registry is perfectly harmless. At the same time, however, it's true that there are certain values in the registry that should never be changed. In fact, changing them can pretty much wipe your computer out, once and for all. It's like working on the bomb squad: if you snip the right wire, the bomb is defused and everything is fine. But if you snip the wrong one—Boom! You just created Microsoft Bob!
. . .
This article, by the Scripting Guys, is a breath of fresh air, and if you've the time, a joy to read. It's nice to see that there are some real honest-to-goodness people that work at Microsoft. I like the section of the article entitled "So I Guess That Tweakomatic Isn't Extensible Either, Right?" - it describes the TweakUI team. It's pretty funny.
And of course there's no getting away from Microsoft's copyrights...
OS: All Platforms > General
Date: 07/27/05
Back to top
|