Windows Display Write Failed

snowman910

I have installed Bitdefender Antivirus Free Edition version, which is updated through an hour ago to version 1.0.21.1099 and uninstalled Avira on my home workstation:

XP SP3

Intel® Core2 CPU

6300 @ 1.86GHz

1.87 GHz, 3.25 GB of RAM

and on my wife's home workstation:

XP SP3

Intel Pentium III

853 MHz, 768 MB of RAM

and since the installation on February 6th, both computers are experience repeated Windows Delayed Write Failed error messages, and are freezing up and warm boot is required to get them working again, and there has been one blue screen. None of this was occurring before the antivirus changes.

As suggested by Microsoft, I have turned off turn off Enable write caching on the disks, follow these steps:

Click Start, and then click My Computer.

Right-click the hard disk, and then click Properties.

Click the Hardware tab.

Click to select the hard disk, and then click Properties.

Click the Policies tab.

Click to clear the Enable write caching on the disk check box, and then click OK.

Click OK to close the Local Disk (C:) Properties dialog box.

Repeat steps 3 through 5 for each hard disk that is installed in your computer.

but doing this did not help.

There is a lot of information on the Web about a Windows Delayed Write Failed virus, which I suspect is linking to fake antivirus schemes. Malwarebytes scans run clean.

I am unable to get e-mail assistance through the Bitdefender website because I foolishly failed to keep record of the License Keys for each installation, and without that, the contact form will not function. I am unable to find the License Keys through the Bitdefender controls. I have found an e-mail address in the product license, but it is not identified as a technical assistance address. Can anyone help me, please? Thank you in advance!

AlexCS

I'm having the same issue on multiple XP computers that I installed BD on yesterday. I've managed to get on to their tech support so will let you know once I have an answer...

bmdb

I am having the same issue on a couple of PC's as well. I sure hope we can get a solution.