Files Are Deleted When You Drag Them from One Location to Another in Windows Explorer

This article has been archived. It is offered "as is" and will no longer be updated.
When you drag a file from one location to another in Windows Explorer, and then you click No in the Confirm File Replace dialog box, the files may be deleted from the source location and not copied to the destination as expected.
This problem may occur if the data object that is moved supports only the CFSTR_FILECONTENTS/CFSTR_FILEDESCRIPTOR clipboard format.

When you drag an object from a folder (including objects in namespace extensions) in Windows Explorer (or from any other program) to a file system folder in Windows Explorer, and the file already exists, Windows Explorer opens the Confirm File Replace dialog box. The move target then communicates to the move source the result of the move operation by setting one of the DROPEFFECT_* flags in the data object's CFSTR_PERFORMEDDROPEFFECT clipboard format. The move source is responsible for deleting the source file after the move operation is completed.

The problem that is described in the "Symptoms" section may occur if you click No when you are prompted to overwrite existing files during a move operation. In this scenario, CFSTR_PERFORMEDDROPEFFECT remains set to DROPEFFECT_MOVE, and this signals the move source that the files have been moved and tells it to delete those files from the source location. This may cause data loss, because existing files are not overwritten in the destination folder, but they are still deleted from the source location.

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.


No prerequisites are required.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

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.
   Date         Time   Version            Size    File name   ----------------------------------------------------------   30-Jun-2003  18:06  5.0.3700.6764   2,357,520  Shell32.dll         27-Jun-2003  00:27  5.0.2195.6761   4,607,488  Sp3res.dll  
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages

Article ID: 821739 - Last Review: 10/26/2013 18:52:02 - Revision: 2.7

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB821739