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.

Error message when you create a new partition during a Windows Server 2008 installation on a computer that has UEFI enabled: "0x8004240f"


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that uses GUID partition table (GPT) disks and has Unified Extensible Firmware Interface (UEFI) mode enabled.
  • You configure the computer to start from the UEFI firmware.
  • You try to install Windows Server 2008 on the computer.
  • When you are prompted for which partition to install the system on during installation, you click Advanced to create a new partition.
  • The default size of the new partition is the total available space on the disk. Therefore, you leave the default partition size unchanged and then click Apply to continue the installation.
In this scenario, you receive an error message.
The error message on the x86 version of Windows Server 2008 is as follows:
0x8004240f (VDS_E_NOT_ENOUGH_SPACE)
The error message on the x64 version of Windows Server 2008 is as follows:
Failed to create a new partition on the selected unused space. [Error: 0x8004240f]

↑ Back to the top


Cause

This problem occurs because the Setup program calculates the available disk space on GPT disks incorrectly.

↑ Back to the top


Resolution

Hotfix information

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.

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.

Prerequisites

No prerequisites are required.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

Windows Vista and Windows Server 2008 file information notes

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.6000.16xxxWindows VistaRTMGDR
    6.0.6000.20xxxWindows VistaRTMLDR
    6.0.6001.18xxxWindows Vista and Windows Server 2008SP1GDR
    6.0.6001.22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.6002.18xxxWindows Vista and Windows Server 2008SP2GDR
    6.0.6002.22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the original release of Windows Server 2008.
  • 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 x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22448167,93611-Jun-200912:15x86
Audit.exe6.0.6001.2244852,73611-Jun-200909:55x86
Diager.dll6.0.6001.2244831,23211-Jun-200912:20x86
Diagnostic.dll6.0.6001.22448122,36811-Jun-200912:20x86
Oobeldr.exe6.0.6001.2244842,49611-Jun-200909:55x86
Setup.cfgNot Applicable2,71101-Apr-200919:28Not Applicable
Setup.exe6.0.6001.22448192,58411-Jun-200913:00x86
Spprgrss.dll6.0.6001.2244854,27211-Jun-200912:20x86
Sysprep.exe6.0.6001.2244894,72011-Jun-200909:55x86
W32uiimg.dll6.0.6001.224482,928,64011-Jun-200912:20x86
W32uires.dll6.0.6001.22448266,75211-Jun-200912:20x86
Wdsutil.dll6.0.6001.2244847,61611-Jun-200912:20x86
Win32ui.dll6.0.6001.22448417,28011-Jun-200912:20x86
Windeploy.exe6.0.6001.2244862,97611-Jun-200909:55x86
Winsetup.dll6.0.6001.224481,470,97611-Jun-200912:20x86
Actionqueue.dll6.0.6002.22151167,93611-Jun-200912:04x86
Audit.exe6.0.6002.2215152,73611-Jun-200909:39x86
Diager.dll6.0.6002.2215131,23211-Jun-200909:40x86
Diagnostic.dll6.0.6002.22151122,36811-Jun-200909:40x86
Oobeldr.exe6.0.6002.2215142,49611-Jun-200909:39x86
Setup.cfgNot Applicable2,71104-Apr-200905:54Not Applicable
Setup.exe6.0.6002.22151192,56811-Jun-200912:33x86
Spprgrss.dll6.0.6002.2215154,27211-Jun-200909:39x86
Sysprep.exe6.0.6002.2215194,72011-Jun-200909:39x86
W32uiimg.dll6.0.6002.221512,928,64011-Jun-200912:07x86
W32uires.dll6.0.6002.22151266,75211-Jun-200909:39x86
Wdsutil.dll6.0.6002.2215147,61611-Jun-200909:38x86
Win32ui.dll6.0.6002.22151417,28011-Jun-200912:07x86
Windeploy.exe6.0.6002.2215162,97611-Jun-200909:39x86
Winsetup.dll6.0.6002.221511,470,97611-Jun-200912:07x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22448167,93611-Jun-200912:15x86
Audit.exe6.0.6001.2244852,73611-Jun-200909:55x86
Diager.dll6.0.6001.2244831,23211-Jun-200912:20x86
Diagnostic.dll6.0.6001.22448122,36811-Jun-200912:20x86
Oobeldr.exe6.0.6001.2244842,49611-Jun-200909:55x86
Setup.cfgNot Applicable2,71101-Apr-200919:28Not Applicable
Setup.exe6.0.6001.22448192,58411-Jun-200913:00x86
Spprgrss.dll6.0.6001.2244854,27211-Jun-200912:20x86
Sysprep.exe6.0.6001.2244894,72011-Jun-200909:55x86
W32uiimg.dll6.0.6001.224482,928,64011-Jun-200912:20x86
W32uires.dll6.0.6001.22448266,75211-Jun-200912:20x86
Wdsutil.dll6.0.6001.2244847,61611-Jun-200912:20x86
Win32ui.dll6.0.6001.22448417,28011-Jun-200912:20x86
Windeploy.exe6.0.6001.2244862,97611-Jun-200909:55x86
Winsetup.dll6.0.6001.224481,470,97611-Jun-200912:20x86
Actionqueue.dll6.0.6002.22151167,93611-Jun-200912:04x86
Audit.exe6.0.6002.2215152,73611-Jun-200909:39x86
Diager.dll6.0.6002.2215131,23211-Jun-200909:40x86
Diagnostic.dll6.0.6002.22151122,36811-Jun-200909:40x86
Oobeldr.exe6.0.6002.2215142,49611-Jun-200909:39x86
Setup.cfgNot Applicable2,71104-Apr-200905:54Not Applicable
Setup.exe6.0.6002.22151192,56811-Jun-200912:33x86
Spprgrss.dll6.0.6002.2215154,27211-Jun-200909:39x86
Sysprep.exe6.0.6002.2215194,72011-Jun-200909:39x86
W32uiimg.dll6.0.6002.221512,928,64011-Jun-200912:07x86
W32uires.dll6.0.6002.22151266,75211-Jun-200909:39x86
Wdsutil.dll6.0.6002.2215147,61611-Jun-200909:38x86
Win32ui.dll6.0.6002.22151417,28011-Jun-200912:07x86
Windeploy.exe6.0.6002.2215162,97611-Jun-200909:39x86
Winsetup.dll6.0.6002.221511,470,97611-Jun-200912:07x86
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22448200,70411-Jun-200912:36x64
Audit.exe6.0.6001.2244864,00011-Jun-200910:09x64
Diager.dll6.0.6001.2244838,91211-Jun-200912:41x64
Diagnostic.dll6.0.6001.22448146,43211-Jun-200912:41x64
Oobeldr.exe6.0.6001.2244848,12811-Jun-200910:09x64
Setup.cfgNot Applicable2,71101-Apr-200917:21Not Applicable
Setup.exe6.0.6001.22448209,48011-Jun-200913:28x64
Spprgrss.dll6.0.6001.2244854,78411-Jun-200912:41x64
Sysprep.exe6.0.6001.22448108,03211-Jun-200910:09x64
W32uiimg.dll6.0.6001.224482,928,12811-Jun-200910:09x64
W32uires.dll6.0.6001.22448266,24011-Jun-200910:09x64
Wdsutil.dll6.0.6001.2244856,32011-Jun-200912:41x64
Win32ui.dll6.0.6001.22448573,95211-Jun-200912:41x64
Windeploy.exe6.0.6001.2244876,80011-Jun-200910:09x64
Winsetup.dll6.0.6001.224481,866,75211-Jun-200912:41x64
Actionqueue.dll6.0.6002.22151200,70411-Jun-200912:04x64
Audit.exe6.0.6002.2215164,00011-Jun-200909:48x64
Diager.dll6.0.6002.2215138,91211-Jun-200912:08x64
Diagnostic.dll6.0.6002.22151146,43211-Jun-200912:08x64
Oobeldr.exe6.0.6002.2215148,12811-Jun-200909:48x64
Setup.cfgNot Applicable2,71103-Apr-200921:28Not Applicable
Setup.exe6.0.6002.22151209,48011-Jun-200912:38x64
Spprgrss.dll6.0.6002.2215154,78411-Jun-200912:08x64
Sysprep.exe6.0.6002.22151108,03211-Jun-200909:48x64
W32uiimg.dll6.0.6002.221512,928,12811-Jun-200909:48x64
W32uires.dll6.0.6002.22151266,24011-Jun-200909:48x64
Wdsutil.dll6.0.6002.2215156,32011-Jun-200912:08x64
Win32ui.dll6.0.6002.22151573,95211-Jun-200912:08x64
Windeploy.exe6.0.6002.2215176,80011-Jun-200909:48x64
Winsetup.dll6.0.6002.221511,866,75211-Jun-200912:08x64
Actionqueue.dll6.0.6001.22448167,93611-Jun-200912:15x86
Audit.exe6.0.6001.2244852,73611-Jun-200909:55x86
Diager.dll6.0.6001.2244831,23211-Jun-200912:20x86
Diagnostic.dll6.0.6001.22448122,36811-Jun-200912:20x86
Oobeldr.exe6.0.6001.2244842,49611-Jun-200909:55x86
Setup.cfgNot Applicable2,71101-Apr-200919:28Not Applicable
Setup.exe6.0.6001.22448192,58411-Jun-200913:00x86
Spprgrss.dll6.0.6001.2244854,27211-Jun-200912:20x86
Sysprep.exe6.0.6001.2244894,72011-Jun-200909:55x86
W32uiimg.dll6.0.6001.224482,928,64011-Jun-200912:20x86
W32uires.dll6.0.6001.22448266,75211-Jun-200912:20x86
Wdsutil.dll6.0.6001.2244847,61611-Jun-200912:20x86
Win32ui.dll6.0.6001.22448417,28011-Jun-200912:20x86
Windeploy.exe6.0.6001.2244862,97611-Jun-200909:55x86
Winsetup.dll6.0.6001.224481,470,97611-Jun-200912:20x86
Actionqueue.dll6.0.6002.22151167,93611-Jun-200912:04x86
Audit.exe6.0.6002.2215152,73611-Jun-200909:39x86
Diager.dll6.0.6002.2215131,23211-Jun-200909:40x86
Diagnostic.dll6.0.6002.22151122,36811-Jun-200909:40x86
Oobeldr.exe6.0.6002.2215142,49611-Jun-200909:39x86
Setup.cfgNot Applicable2,71104-Apr-200905:54Not Applicable
Setup.exe6.0.6002.22151192,56811-Jun-200912:33x86
Spprgrss.dll6.0.6002.2215154,27211-Jun-200909:39x86
Sysprep.exe6.0.6002.2215194,72011-Jun-200909:39x86
W32uiimg.dll6.0.6002.221512,928,64011-Jun-200912:07x86
W32uires.dll6.0.6002.22151266,75211-Jun-200909:39x86
Wdsutil.dll6.0.6002.2215147,61611-Jun-200909:38x86
Win32ui.dll6.0.6002.22151417,28011-Jun-200912:07x86
Windeploy.exe6.0.6002.2215162,97611-Jun-200909:39x86
Winsetup.dll6.0.6002.221511,470,97611-Jun-200912:07x86

↑ Back to the top


HOTFIX INSTALLATION STEPS

Expand the hotfix package

Expand the Windows6.0-KB971576-platform.msu package by following these steps:
  1. At a command prompt, switch the current directory to the directory that contains the Windows6.0-KB971576-platform.msu package.
  2. Type the following commands, and then press ENTER:
    md tmp
    Expand –f:* Windows6.0-KB971576-platform.msu tmp
    md cab
    Expand –f:* tmp\Windows6.0-KB971576-platform.cab .\cab
    Note When you run these commands, the files are extracted to a Tmp folder, and a file that is named Windows6.0-KB971576-platform.cab is extracted. The updated files are located in two subfolders that are named like x86_microsoft-windows-setup-component_XXXXXX. The subfolder that contains 6.0.6001 in the name is for Windows Server 2008. The subfolder that contains 6.0.6002 in the name is for Windows Server 2008 Service Pack 2.
  3. Create a new folder named Hotfix, and then copy all the updated files into the Hotfix folder.
  4. In the Hotfix folder, rename the Setup.exe file to Setup.exe.sav, and rename the Setup.cfg file to Setup.cfg.sav

Modify the Boot.wim file

Before you follow these steps, install the WAIK (Windows Automated Installation Kit) which is available in the following download:
Download Download the Windows Automated Installation Kit (AIK) package now.
  1. Open the Microsoft Windows Preinstallation Environment (WinPE) command prompt by using the Administrator privilege.
  2. Create a temporary directory named SetUPDVD by using the following commands:
    md SetuPDVD
    cd SetupDVD
  3. Copy the Boot.wim file from the operating system that you are modifying to the SetupDVD folder.
  4. Make a directory to mount the Wim file by using the following command:
    md mount
  5. Use the imagex command to mount the Boot.wim file:
    imagex /mountrw boot.wim 2 .\mount
  6. Copy the updated files to the Sources directory in the mounted Boot.wim file:
    cd mount\sources
    xcopy \hotfix\*.* /e
    cd ..\..
  7. Use the imagex command to mount the Boot.wim file:
    imagex /unmount /commit .\mount

Modify the DVD content

  1. Make a folder named Dvd, and then copy the contents of the DVD to the Dvd folder. For example, you can use the following commands:
    md dvd
    cd \
    cd dvd
    xcopy X:* * /e
    cd sources
    xcopy \hotfix\* * /u
    Note In these commands, the X represents the letter of the DVD drive.
  2. Copy the modified Boot.wim file to the Dvd folder on the hard disk:
    copy \setupdvd\boot.wim *
  3. Rename the Setup.exe.sav and Setup.cfg.sav files back to their original names in the Sources directory. For example, run the following commands:
    copy \hotfix\setup.exe.sav \dvd\sources\setup.exe
    copy \hotfix\setup.cfg.sav \dvd\sources\setup.cfg

Create an installation image

You can use the oscdimg command to create an International Standards Organization (ISO) file of the Dvd folder and to make the image a UEFI-bootable image.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
947024 How to create an ISO image for UEFI platforms for a Windows PE CD-ROM for Windows Server 2008

After you create the image, burn the image to a DVD.

↑ 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


Workaround

To work around this problem, use either of the following methods:
  • Use the Diskpart tool to create the partitions before you start the installation.
  • After you click Advanced to create a new partition during installation, specify a new size that is 2 megabytes less than the default partition size.

↑ Back to the top


More Information

For more information about software update terminology, 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

↑ Back to the top


Additional file information for Windows Server 2008

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

File nameFile versionFile sizeDateTimePlatform
Package_for_kb971576_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36711-Jun-200923:51Not Applicable
Package_for_kb971576_client_2~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69311-Jun-200923:51Not Applicable
Package_for_kb971576_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71311-Jun-200923:51Not Applicable
Package_for_kb971576_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42111-Jun-200923:51Not Applicable
Package_for_kb971576_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69011-Jun-200923:51Not Applicable
Package_for_kb971576_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70111-Jun-200923:51Not Applicable
Package_for_kb971576_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42511-Jun-200923:51Not Applicable
Package_for_kb971576_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69411-Jun-200923:51Not Applicable
Package_for_kb971576_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71311-Jun-200923:51Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22448_none_3292e36bc6791a52.manifestNot Applicable27,02711-Jun-200914:31Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22151_none_34678361c3adda06.manifestNot Applicable27,02711-Jun-200913:59Not Applicable

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

File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22448_none_8eb17eef7ed68b88.manifestNot Applicable27,09311-Jun-200914:45Not Applicable
Amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22151_none_90861ee57c0b4b3c.manifestNot Applicable27,09311-Jun-200914:00Not Applicable
Package_for_kb971576_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37511-Jun-200923:51Not Applicable
Package_for_kb971576_client_2~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70511-Jun-200923:51Not Applicable
Package_for_kb971576_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72311-Jun-200923:51Not Applicable
Package_for_kb971576_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42911-Jun-200923:51Not Applicable
Package_for_kb971576_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70211-Jun-200923:51Not Applicable
Package_for_kb971576_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,71111-Jun-200923:51Not Applicable
Package_for_kb971576_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43311-Jun-200923:51Not Applicable
Package_for_kb971576_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70611-Jun-200923:51Not Applicable
Package_for_kb971576_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72311-Jun-200923:51Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22448_none_3292e36bc6791a52.manifestNot Applicable27,02711-Jun-200914:31Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22151_none_34678361c3adda06.manifestNot Applicable27,02711-Jun-200913:59Not Applicable

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

File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22448_none_32948761c677234e.manifestNot Applicable27,06011-Jun-200916:55Not Applicable
Ia64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22151_none_34692757c3abe302.manifestNot Applicable27,06011-Jun-200913:38Not Applicable
Package_for_kb971576_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42511-Jun-200923:51Not Applicable
Package_for_kb971576_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,52911-Jun-200923:51Not Applicable
Package_for_kb971576_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,70611-Jun-200923:51Not Applicable
Package_for_kb971576_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42911-Jun-200923:51Not Applicable
Package_for_kb971576_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,53311-Jun-200923:51Not Applicable
Package_for_kb971576_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,71711-Jun-200923:51Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22448_none_3292e36bc6791a52.manifestNot Applicable27,02711-Jun-200914:31Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22151_none_34678361c3adda06.manifestNot Applicable27,02711-Jun-200913:59Not Applicable

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbsurveynew, kbbug, kbfix, kbhotfixserver, kbqfe, kb

↑ Back to the top

Article Info
Article ID : 971576
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 218