Your Computer Stops Responding When You Create a File on a Local File Share

This article has been archived. It is offered "as is" and will no longer be updated.
On a Windows 2000-based computer, if you create a file that has the temporary bit set, and the file is on a local file share, the computer may stop responding.
This problem may occur if the Maximize data throughput for network applications option is selected on the Properties page for File and Printer Share for Microsoft Networks. If the dirty page threshold is exceeded, Cache Manager has to wait for a flush to occur; therefore, it throttles (suppresses) all writes. (A dirty page is a page that has been modified in the cache but has not yet been written to disk.) Because the files are temporary files, Cache Manager will not flush them automatically.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft 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

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

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, submit a request to 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.The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version        Size       File name   ----------------------------------------------------------   15-Nov-2001  12:27                     5,149   22-Jan-2003  09:19  5.0.2195.6658  1,692,288  Ntkrnlmp.exe   22-Jan-2003  09:20  5.0.2195.6658  1,691,840  Ntkrnlpa.exe   22-Jan-2003  09:20  5.0.2195.6658  1,712,512  Ntkrpamp.exe   22-Jan-2003  09:19  5.0.2195.6658  1,669,888  Ntoskrnl.exe   16-Dec-2002  11:26           4,096  Spmsg.dll   16-Dec-2002  11:27          87,040  Spuninst.exe

Microsoft 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 Microsoft Windows 2000 Service Pack 4.
More information
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Article ID: 813485 - Last Review: 01/09/2015 13:43:00 - Revision: 2.0

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbwin2000presp4fix kbfix kbbug KB813485