Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot start a computer that is running an Itanium-based version of Windows Server 2008 if the system hive size exceeds the 32-MB limit


View products that this article applies to.

Symptoms

Itanium-based versions of Windows Server 2008 have a 32-megabyte (MB) limit for the system registry hive size. In certain configurations on a large system, the system hive may reach or exceed the 32-MB limit. This behavior frequently occurs if the system has multiple disks and volumes and if the system hive includes multiple control sets. If the limit is reached, the system may not start.

This hotfix enables new single-control-set functionality. Single-control-set functionality enables a computer that is running an Itanium-based version of Windows Server 2008 to use only one control set.

↑ Back to the top


Workaround

Important This issue was completely resolved in Windows Server 2008 R2.

To work around this issue, reduce the size of the registry in Windows Server 2008. To do this, follow these steps:
  1. Install the hotfix that is described in the �Hotfix information� section.
  2. Add the following registry subkey:
    LocationHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Configuration Manager
    NameSingleControlSetEnabled
    TypeREG_DWORD
    Value1
  3. Restart the computer to let the new registry setting take effect and to enable single-control-set functionality.

Note The system no longer creates the Last Known Good control set after single control set functionality is enabled. Therefore, we suggest that you use a scheduled task to back up the system hive for system recovery.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntoskrnl.exe6.0.6001.224789,483,84823-Jul-200919:55IA-64SP1
Services.exe6.0.6001.22478746,49623-Jul-200916:44IA-64SP1
Services.mofNot Applicable2,86601-Apr-200917:33Not ApplicableSP1
For all supported Itanium-based versions of Windows Server 2008 SP2
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntoskrnl.exe6.0.6002.221839,462,32823-Jul-200919:30IA-64SP2
Services.exe6.0.6002.22183746,49623-Jul-200916:35IA-64SP2
Services.mofNot Applicable2,86603-Apr-200921:34Not ApplicableSP2

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22478_none_6c77faefcd7040f2.manifestNot Applicable16,81923-Jul-200920:45Not Applicable
Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.22183_none_6e4e9b79caa33354.manifestNot Applicable16,81923-Jul-200920:14Not Applicable
Ia64_microsoft-windows-s..s-servicecontroller_31bf3856ad364e35_6.0.6001.22478_none_cfa759b6e6962f94.manifestNot Applicable43,54223-Jul-200920:41Not Applicable
Ia64_microsoft-windows-s..s-servicecontroller_31bf3856ad364e35_6.0.6002.22183_none_d17dfa40e3c921f6.manifestNot Applicable43,54223-Jul-200920:10Not Applicable
Package_for_kb973816_sc_0~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,42524-Jul-200918:30Not Applicable
Package_for_kb973816_sc_1~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,53024-Jul-200918:30Not Applicable
Package_for_kb973816_sc~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,70624-Jul-200918:30Not Applicable
Package_for_kb973816_server_0~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,42924-Jul-200918:30Not Applicable
Package_for_kb973816_server_1~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,53424-Jul-200918:30Not Applicable
Package_for_kb973816_server~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,71824-Jul-200918:30Not Applicable
Package_for_kb973816_winpesrv_0~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,42624-Jul-200918:30Not Applicable
Package_for_kb973816_winpesrv~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,43424-Jul-200918:30Not Applicable

↑ Back to the top


Keywords: KB973816, kbhotfixserver, kbqfe, kbsurveynew, kbfix, kbexpertiseadvanced, kbautohotfix

↑ Back to the top

Article Info
Article ID : 973816
Revision : 2
Created on : 11/2/2009
Published on : 11/2/2009
Exists online : False
Views : 246