Windows Server 2003 Registry Hacks (also work on XP or Vista)

Introduction

New Registry Section - Especially for Vista, but also works with XP.

My aim in this section is to give you the experience, confidence and satisfaction of making changes to your Windows registry.

There are times when you read about a Windows Server 2003 feature but there is no icon to implement it.  Therefore the only way to test that feature is to change a setting in the registry.  Another reason to master registry editing is so that you can remotely troubleshoot a machine via Regedit.

The executables to hack the registry are Regedit (or Regedt32).  The newer versions of Regedit remember the last place you visited, which is extremely useful when you are constantly adjusting values.  If you have not been to the registry before, click on the Windows START (Button), click on Run, type regedit and then press OK.

How Dangerous is editing the registry?

People give dire warnings about changing the registry.  My view is that changing settings via the registry is no more hazardous than say - configuring the monitor refresh rate through the Control Panel.  You may hear that if you make a mistake you can cripple your system; I find that if you type in the wrong key value nothing happens!  However I once saw a 'gung-ho' individual delete a whole section of the registry.  This would have been disastrous if I had not exported the relevant section, so we just imported it and solved the problem.

Registry Tips

• Use Regedit rather than Regedt32 because it has a wonderful FIND.
• Use the REGISTRY Export as a precaution before you experiment.
• Rename settings you do not needed or want, avoid deleting anything in the registry.
• If you are following advice from an article, check whether it says ADD or Change.  With ADD you need an extra step.
• Practice remote registry editing to prepare for an emergency.

Here below is an example of a registry hack, for more ideas see the side menu.

Faster kill for applications not responding

Launch Regedit and click on the 'Find' menu search for WaitToKillAppTimeout.  The default is 20000 milli seconds, my challenge is to try a shorter timeout, say about 5000 (5 seconds).

As you may guess from the name this sets the timeout on processes that are hanging.  Technically this an interesting hack as you have to set it two or thee times in the registry - keep pressing F3 (Find next).  The reason is that this setting is found on the Current user, Default user and maybe another user where you see a SID value.

Learning Points

• Particularly with the HKEY_USER registry settings, you have to make the changes three times; remember F3 to 'Find Next'.
• Time values are in milli seconds e.g 1000 = 1 second

Guy Recommends: SolarWinds Engineer's Toolset v10

The Engineer's Toolset v10 provides a comprehensive console of utilities for troubleshooting computer problems.  Guy says it helps me monitor what's occurring on the network, and the tools teaches me more about how the system literally operates.

There are so many good gadgets, it's like having free rein of a sweetshop. Thankfully the utilities are displayed logically: monitoring, discovery, diagnostic, and Cisco tools.  Download your copy of the Engineer's Toolset v 10

Home Copyright © 1999-2010 Computer Performance LTD All rights reserved

Please report a broken link, or an error.