One of MY video files got trashed to 0 bytes, too

There have been quite a few threads about folks saying that their WDTV “converted” one of their video files to 0 bytes and it “got bricked” and unplayable, and I only half-believed their assertions.  Not anymore, because an ISO file on a HD connected to my Live Plus player was unplayable today, and when I looked at the file from my PC via the network, it showed 0 bytes file size.  Just the file name remained.  This file was put on the drive this past June, it played fine a few times (it’s for the kids and can get mulitple plays).

I was able to delete this file ,so I think it was still there, but somehow its size changed, or WDTV changed its size making it un-useable.  Anyway, after deleting, I copied it back to the HD via the backup drive with same videos.  I don’t think it is a firmware version issue – I don’t have the current firmware on, but the one that preceeded it.  Previous complaints from others mentioned using the current firmware.

I DO think it is a WDTV player issue; at least with the Plus units.

So, my question is:   Has anyone got a real handle on this problem, and could anyone from WD comment on this, because it is REALLY happening. 

BTW, I checked other videos on this drive for being 0 bytes, and there were none but the one I mentioned.  But, hey:  stay tuned.

It have not happens to me, yet, but there are many users reporting this.

You better contact WD Support, it is the best way to get an answer from they, this is a user to user forum.

OK, I just discovered TWO more 0 bytes ISO files since I wrote the first message above.  I’ll give support a call.

Are you saying that this is happening just on the Live Plus, or have you heard of it happening on other players?  If it’s happened on the Live Hub or Live Streaming, then make sure someone reports it in the Issues Exchange for those devices.

Thanks for replying here, Bill.  I;ll let others know what you told me in a previous private message when I asked you about this issue:    Bill_S >>>  “We have no idea what could be causing this, but we are investigating it.  I don’t think we’ve been able to reproduce it, yet.  But we are taking it serious.”

Since I only have a WDTV Live Plus, I don’t have firsthand knowledge about other units.  I knew there were previous complaints of this, so I google-searched and came up with these  links – for other units besides the Live Plus:

There are more links to this issue.  I found them by using this Google search link;

Bill, since the problem appears related to other units and is reported by quite a few folks, WOULD YOU REPORT THIS ISSUE  to the appropriate WD folks for us all?



The zero byte issue is well known in the WDLXTV and Linux community. The issue has been traced to the Paragon driver used by WD which under certain circumstances will return a zero byte value or worst the USB hard drive is completely deleted.

I posted a comprehensive list of links relating to the zero byte issue only to be ignored.

The only successful resolution at this stage is a complete re-format of the USB hard drive or use networked hard drives.

Thanks for chipping in here.  So, is this the message thread link you refer to re: Paragon, etc: 

One of the “take-aways” I get from this is that if WD, a HARD DRIVE company is using some Linux “knockoff” driver instead of a genuine Microsoft driver, they should reverse course and use the MS driver. 

The other takeaway is; do I really need to format my HD that is having this trouble?  Maybe so, because these drives have been connected for almost a year to the Live Plus, and only in the very recent past have they begun to display this problem.  The HDs, are self-powered Hitachi SimpleDrives, 2TB each.  The drives inside are decent Deskstar 7K2000 drives that spin at 7200 rpm.

So, once I copy the contents to another one of these drives, and I format, should I use Quick Format or the slow grind?  Should I format with Win 7 or XP?

Also, I mostly transfer new files to these drives via the home network connection, and when I have taken the drives off the WDTV to periodically run CHKDSK, they pass the long overnight test.

Hopefully, we have gotten WD’s attention this time for this 0 byte problem, and their experts can figure it out.  Our friend Bill can keep us forum members in the loop.

I’ll let you know as soon as I find out something.

Here’s a message thread from this past August that addresses the 0 bytes issues with helpful comments from some of the regular forum members:

The take-away from the message is to always eject the drives attached to the WDTV before removing them and/or turning off the WDTV.  Better to be safe than sorry.

So, tonight, I will do the above before taking out the drive creating the 0 byte errors, put it on the PC and run the complete CHKDSK overnight.  When the drive goes back on the WDTV, I will try to always remember to eject the drives in the future. Perhaps this procedure will remove (or lessen) the 0 bytes problems.

Of course, if there is ever another home power failure (ha!) this will blow the efficacy of “careful” drive removal and WDTV shut downs!