ITsVISTA
Information that makes life easier when it comes to installing, managing, and using Windows Vista.
Start About FAQ Blogroll Shop

ITsVISTA KB-Link: KB963044

On a computer that runs Windows Vista or Windows Server 2008, after you rename, delete, or move the files in a network share that is hosted on a Windows Vista or Windows Server 2008-based computer, files are still listed in the network share

On a computer that runs Windows Vista or Windows Server 2008, you have a network share that is hosted on a computer that runs Windows Vista or Windows Server 2008. In this scenario, after you rename, delete, or move the files in the network share, you may see that the original file names are still listed in the network share, although the operation that you performed on the files is successful.

For example, consider the following scenario:

  • You have the following network share:
    \\Server\Share.
  • You use the following command to move a file:
    Move \\Server\Share\Dir1\file.txt \\Server\Share\Dir2\file.txt
  • You use the following command, and you see that the operation is executed successfully:
    Dir \\Server\Share\Dir2
  • You use the following command to check the original directory:
    Dir \\Server\Share\Dir1

In this scenario, you may find that the original file.txt file name is still listed in the network share.

Notes

  • This problem occurs if the network share is connected by using the Server Message Block (SMB) v2 protocol. The default network share protocol between Windows Vista or Windows Server 2008 is SMB v2.
  • This problem also occurs if you try to rename, delete, or move the files by using an application that calls the MoveFileEx function.
  • This problem no longer occurs after about 10 seconds. This means that after about 10 seconds, the file disappears from the original directory.
There is a download that resolves this issue. See Hotfixes for details.
32-bit Download: Contact Microsoft
64-Bit Download: Contact Microsoft

For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB963044.

Get notified of new posts for FREE via RSS or E-mail

Subscribe to ITsVISTA!

Related Posts