Registry Size Increases After Installing Outlook Express 5 (223492)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition

This article was previously published under Q223492

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

SYMPTOMS

Installing Microsoft Outlook Express 5.0 on Windows NT Server 4.0, Terminal Server Edition may cause the registry to grow unnecessarily.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack



To work around this problem, before installing Outlook Express 5.0 on Windows NT Server 4.0, Terminal Server Edition, create the following registry key:

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.
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatilibity\Applications\setup50

    NOTE: The above registry key is one path; it has been wrapped for readability.
  3. On the Edit menu, click Add Value, and then add the following REG_DWORD registry value:

    Flags=0x108

  4. Quit Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Modification Type:MajorLast Reviewed:6/24/2004
Keywords:kbbug kbfix KB223492