windows-delayed write failed

When tranfering files from my hard (backup) to my external drive I get the error Message:, Windows-Delay Write Failed.
Windows was unable to save all the data for the file E:\$Mft. The Data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file eleswhere.
How can I solve this problem? Please HELP!
Thank You

I found this case, http://support.microsoft.com/kb/925269, in search of the same issue I’m having. The information contained is pretty basic. My issue I have is a Seagate 1TB external drive that I have a lot of music on. When I plug the drive in and start playing music, I intermittently receive the same message as you (except my drive letter is K:). The case states that WindowsXP does not handle removable media with NTFS format, which I verified by right-clicking on the drive letter under My Computer and then selecting Properties. It shows the drives format under File System on the General tab. This is as far as I’ve gotten with this issue. Apparently my only two options are copying my entire drive, then formatting the drive to FAT or FAT32 file system and then copying everything back OR upgrading to Vista or 7.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

«Delayed write failed» error message when .pst files are stored on a network file server that is running Windows Server 2008 R2

Symptoms

Consider one of the following scenarios:

You enable Remote Desktop on a computer (computer A) that is running Windows 7 or Windows Server 2008 R2.

You configure an Outlook 2010 client that is installed on computer A to save Personal Folder (.pst) files on another computer (computer B). Computer B is a file server that is running Windows Server 2008 R2.

You establish a remote connection to computer A from a client computer, and then start Outlook 2010 in the Remote Desktop session.

In this scenario, you receive the following error message that states that the .pst file is corrupted:

Delayed Write Failed
Windows was unable to save all the data for the file file path. The data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere.

Additionally, the following event is logged in the System log on computer A:Note This issue does not occur if you disable the Server Message Block version 2 (SMBv2) file sharing protocol on the file server.

You have mapped a network drive to a server share and you use offline files to make the data on this share available offline.

You have a MUP filter driver installed (e.g. disc encryption Software).

You try to open a file (e.g. a text file) of a given size from this share while you’re connected to the Network, although the actual SMB Connection to the server is not yet established.

In this Scenario, you might get the this error message:

Cannot open the %% file. Make sure a disk is in the drive you specified

If you click on OK the text file will be empty. If you now close and open the file again it might work.

Cause

Scenario 1:
This issue occurs because the Outlook 2010 client tries to write data to an open SMBv2 file ID that has read-only access.

Scenario 2:
This issue occurs because the offline files client tries to read the file from the server before the actual SMB connection is established.

Resolution

To resolve the issue, install the hotfix on the computer that Outlook 2010 is installed on (computer A) respectively on the Computer that Encounters the error while opening the file.

Note This update also fixes a regression issue in the Rdbss.sys file after the update 2775511 is installed. Install this update (2732673) after you install update 2775511. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2775511 An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

Microsoft Catalog

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 the problem described in this article. 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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 be running 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

«Delayed Write Failed» error when an I/O stress test runs against a Windows Server 2012 failover cluster from a Windows 8-based or Windows Server 2012-based client

Symptoms

Considering the following scenario:

You have a Windows Server 2012 failover cluster that is configured by using continuously available file shares.

An I/O stress test is running on a Windows 8 or Windows Server 2012-based client against the failover cluster. The stress test has a high ratio of open and close operations to data operations. For example, the test repeatedly opens a file on the file share, reads the file, and then closes the file.

Note This scenario may be found in stress tests but does not map directly to customer-usage scenarios.

In this scenario, you may experience I/O errors during failover. Additionally, the following event may be logged in the System log:

Cause

When a file on the file share is opened, a file handle is created. After the file is closed, the Server Message Block (SMB) redirector will cache the file handle for a short time. However, there is a limit on the number of handles that can be cached in this manner. During the stress test, the SMB scavenger can fall behind in closing the cached handles. This may result in a large backlog of handles. Eventually, the number of handles exceeds the limit that can be failed over within the continuous availability time-out and some I/O operations may fail. By default, the continuous availability time-out is 60 seconds.

Resolution

This hotfix is also available at Microsoft Update Catalog.

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 the problem described in this article. 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:

http://support.microsoft.com/contactus/?ws=supportNote 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 be running Windows 8 or Windows Server 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.