We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now


I am changing the HeapDecommitFreeBlockThreshold on a Exchange 2003 server and having problems in the registry

dwielgosz asked
Medium Priority
Last Modified: 2012-08-13
The solution to this is so simple, yet so difficult. i came across this possible issue in the documentation on the MS website. i dutifully proceeded to open the registry editor and created the DWord value. No Problem. However when I try to change the value from the default "0" to the recommended "0x00040000" the editor does not allow me to type the little "x" in the second character position for the Hex value. I have tried putting the value in in decimal, "262144" and then clicking on "Hex", but that gives me a Hex value of "40000" which I believe has the same meaning as "0x00040000" but it looks different and I'm hesitant to the point of not willing to click out of it and reboot. I have seen similar issues posted hear on EE and they all get pointed to the article on MS Tech Net or the KB article which never mention anything but the "0x00040000" value with the 'x" in it. Could someone please give me some advice about the small "x". and not being able to enter it in the registry editor?
Watch Question

Top Expert 2006

please check the following microsoft atricles.

The "HeapDecommitFreeBlockThreshold" registry key

How to optimize memory usage in Exchange Server 2003

How to troubleshoot virtual memory fragmentation in Exchange Server 2003 and Exchange 2000 Server


So what are you saying, to just set it with the decimal number and not worry about the inability to enter the number in hex?
Top Expert 2006
yes..  the following KB has the steps defined

The "HeapDecommitFreeBlockThreshold" registry key

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts


OK, I get it. By virtue of the fact that the instructions are referring to using the decimal equivalent it can be safely assumed that it's OK to use the decimal, even though the article (nor any that I have found) have not addressed the small "x" part of the hex number being entered. haha Just wanted 'proof" because I have a "nice" exchange server that's running smoothly and I didn't want to create any problems. There's always enough issues without creating any new ones. Thanks for the help.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.