I have a very similar problem, although mine will actually get past the boot up phase. I was previously on 2.05.08, and updated to 2.06.10 a couple of days ago. I’ve timed it at least ten different times, and the unit will stay powered for anywhere between 5-15 minutes before powering itself ever since the 2.06.10 update. This problem absolutely did not happen prior to taking the 2.06.10 update.
It doesn’t appear to be related to anything I’m doing on the WD at the time it powers off. One time I was playing a video directly off of the onboard hard drive, and after about 7 minutes of play the unit turned off. Another time I was streaming media to another device off of the wdtv live hub, and the media/content became unavailable after playing for about 11 minutes (the wd had shut itself off again). Another time I left it booted into the main menu screen, and did nothing. At about 14m20s after starting, it shut off while simply sitting at the menu.
I opened a support case with WD. They had me reset the device to factory default settings, but that didn’t help. Then they directed me to the following URL, which provides older code revisions to download, extract to the root directory of a USB device, and plugin to the unit. This let me downgrade to the last known good revision of code I was running - 2.05.08 (although when I took the update via USB, it said ver 3.05.08 – I suspect to trick it into thinking its an “upgrade” as the revision number is higher, even though the code is older?).
Now I’m on 2.05.08 and the spontaneous power off problem persists, when it never did before on 2.05.08.
I will note that when I first tried to apply the new 2.06.10 firmware, it appeared to get through the 2 stage update process (you’ll see a percentage complete bar for 1/2 and then 2/2). However when it automatically rebooted itself, it was still on 2.05.08 code, telling me there was another update available. I applied the update a second time, and it took (most notably adding a games option to the main menu, and a picasa widget/app addition).
So I’m not sure if some sort of file/nvram/block corruption happened during the update process, but it has been broken ever since, even after rolling back to known good revisions of code.
I plan on calling WD support back again tonight after work to see if they have any other ideas, but the last support rep I spoke to led me to believe the next step was issuing an RMA to get a new unit, which does not particularly sit well with me considering I have nearly 1tb of data on it with nowhere to temporarily store it
Anyone else run into a similar situation and found a way to resolve the spontaneous shutdowns?