Windows Server 2003
Service pack information
For additional information about how to resolve this issue in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
811492�
It May Take 35 Seconds to Delete Files Over The Network
Windows XP
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389�
How to obtain the latest Windows XP 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. 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.
File information
The English version of this hotfix 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.
Windows XP Professional SP1 and Windows XP Tablet PC Edition
Date Time Version Size File name
------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 400,896 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 154,880 Rdbss.sys
Windows XP 64-Bit Edition
Date Time Version Size File name
-------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 1,259,392 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 489,216 Rdbss.sys
After you install this hotfix, a new registry key is created. This registry key has the following properties:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters
Value Name: NoDeleteOnClose
Value Type: REG_DWORD
Value Data: 0 or 1
Default Value: 0
The default value for
NoDeleteOnClose is
0, and this value takes effect only when the
OplocksDisabled DWORD value is set to
1 in the same registry key. The behavior of this update depends on
the value of the
NoDeleteOnClose DWORD value, and the value of the
OplocksDisabled DWORD value, as follows:
- OplocksDisabled value is set to 0 (recommended). This hotfix resolves the problems deleting files
that are described in the "Symptoms" section of this article, but you may continue to
experience the intermittent redraw problems in Windows Explorer that are described in
the "Symptoms" section of this article.
- NoDeleteOnClose is set to 1, and OplocksDisabled is set to 1. This hotfix resolves the redraw problem that is described in the
"Symptoms" section of this article, but you may experience intermittent
problems deleting files in Windows Explorer only (even when the file is not
already open) that are described in the "Symptoms" section of this
article.
For additional information about the OplocksDisabled registry
value, click the following article number to view the article in the Microsoft Knowledge Base:
296264�
Configuring opportunistic locking
in Windows