Version Information in Registry Does Not Reflect Slipstreamed Upgrade to Windows 2000 Server SP1 (289215)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
This article was previously published under Q289215 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
After you use a slipstreamed installation to upgrade a computer from Windows NT 4.0, Terminal Server Edition, to Windows 2000 Server Service Pack 1 (SP1), the version information in the registry may not show that SP1 is installed. This behavior raises issues for programs that require installation of SP1.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
WORKAROUND
To work around this behavior, manually add the missing registry value: 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. - Start Registry Editor (Regedt32.exe).
- Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion - On the Edit menu, click Add Value, and then add the following registry value:
Value name: CSDVersion
Data type: REG_SZ
Value data: Service Pack 1 - Quit Registry Editor.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows 2000 Service Pack 2.
Modification Type: | Major | Last Reviewed: | 9/20/2006 |
---|
Keywords: | kbbug kbenv kbfix kbWin2000PreSP2Fix KB289215 |
---|
|