Open Software Solutions

Consider the following scenario. On a Windows Server 2003-based computer, an application calls the GetFileAttributesEx function to retrieve the file attributes of a file. Then, the application calls the MoveFileEx function to move the file to another location on the computer. If the application repeats these actions on several million files, the computer becomes unresponsive. Additionally, the debug log indicates that the NtfF tag consumes lots of paged pool memory.

Note This issue also occurs on a Windows Server 2008-based computer.

Back to the top

When the application calls the GetFileAttributesEx function on a file, all intermediate directories of the file are cached by the NTFS file system. These directory resources remain in the cache until the corresponding directories are specifically traversed (either opened or closed).

If an application calls the MoveFileEx function to move the file to another location shortly after it calls the GetFileAttributesEx function, there is insufficient time for the cached directory resources to be traversed. Therefore, these resources remain in the cache even if the file is closed after it is moved to the new location. In this scenario, the system’s paged pool memory is eventually exhausted.

Back to the top

Hotfix information for Windows Server 2003

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 this specific problem. 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

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 (SP2) installed.

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.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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.

Windows Server 2003 SP2, x86-based versions

File name	File version	File size	Date	Time	Platform
Ntfs.sys	5.2.3790.4319	591,872	23-Jun-2008	11:29	x86

Windows Server 2003 SP2 and Windows XP SP2, x64-based versions

File name	File version	File size	Date	Time	Platform
Ntfs.sys	5.2.3790.4319	1,044,480	24-Jun-2008	05:55	x64

Windows Server 2003 SP2, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ntfs.sys	5.2.3790.4319	1,888,768	24-Jun-2008	05:54	IA-64

Back to the top

Hotfix information for Windows Server 2008

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 this specific problem. 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

To apply this hotfix, you must have Windows Server 2008 installed.

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.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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.

Windows Server 2008, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb953325~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,772	26-Jun-2008	02:39	Not Applicable
Package_2_for_kb953325~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,939	26-Jun-2008	02:39	Not Applicable
Package_3_for_kb953325~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,777	26-Jun-2008	02:39	Not Applicable
Package_4_for_kb953325~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,777	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,421	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,429	26-Jun-2008	02:39	Not Applicable
X86_5520d471ba8d364fa842024b3d081eee_31bf3856ad364e35_6.0.6001.22210_none_1fcda64d5c72da11.manifest	Not Applicable	692	26-Jun-2008	02:39	Not Applicable
X86_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6001.22210_none_a6eff88236115275.manifest	Not Applicable	16,265	25-Jun-2008	03:44	Not Applicable
Ntfs.sys	6.0.6001.22210	1,082,424	25-Jun-2008	03:17	x86

Windows Server 2008, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_ee869119f5f579e28032d56230104714_31bf3856ad364e35_6.0.6001.22210_none_3316f1dbd8796abe.manifest	Not Applicable	696	26-Jun-2008	02:39	Not Applicable
Amd64_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6001.22210_none_030e9405ee6ec3ab.manifest	Not Applicable	16,525	25-Jun-2008	04:13	Not Applicable
Package_1_for_kb953325~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,782	26-Jun-2008	02:39	Not Applicable
Package_2_for_kb953325~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,951	26-Jun-2008	02:39	Not Applicable
Package_3_for_kb953325~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,787	26-Jun-2008	02:39	Not Applicable
Package_4_for_kb953325~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,787	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,429	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,437	26-Jun-2008	02:39	Not Applicable
Ntfs.sys	6.0.6001.22210	1,537,592	25-Jun-2008	03:49	x64

Windows Server 2008, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_45896cf2ed18f2f6f17b19301afd933e_31bf3856ad364e35_6.0.6001.22210_none_4bd67f43637d13e3.manifest	Not Applicable	694	26-Jun-2008	02:39	Not Applicable
Ia64_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6001.22210_none_a6f19c78360f5b71.manifest	Not Applicable	16,517	25-Jun-2008	04:13	Not Applicable
Package_1_for_kb953325~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,777	26-Jun-2008	02:39	Not Applicable
Package_2_for_kb953325~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,782	26-Jun-2008	02:39	Not Applicable
Package_3_for_kb953325~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,782	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,425	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	26-Jun-2008	02:39	Not Applicable
Package_for_kb953325_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,433	26-Jun-2008	02:39	Not Applicable
Ntfs.sys	6.0.6001.22210	3,282,488	25-Jun-2008	03:46	IA-64

Back to the top

To work around this problem, you must traverse the original directory after you move the file to the new directory. To do this, follow these steps:

1.	Call the GetFileAttributesEx function to query a file.
2.	Call the MoveFileEx function to move the file to a new directory.
3.	Call the GetFileAttributesEx function to query the file’s original directory (the file’s directory from step 1).

Back to the top

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

Back to the top

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site:

For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top