You may be thinking that whilst the guys from the Windows Home Server team are out here at CES working the crowds, no-one’s back in Redmond nailing that data corruption bug. From discussions I had with the team yesterday, they have nothing official to share right now in terms of timings on a fix, but I do know the developers back in Redmond are still working hard on it, and my sense is they’re making good progress. I’m hoping to bring you more news in the next couple of weeks.













January 8th, 2008 at 9:04 pm
Next couple of weeks ?
I guess I’ll just turn my newly purchased ‘HP Media Smart’ box off until the fix comes out……. Sigh
January 9th, 2008 at 5:06 pm
Two MS Project 2000 data files were corrupted on my HP MediaSmart yesterday. This may or may not have something to do with the brief power cut we experienced earlier while one of the files was in use. I would have expected the saved version to remain intact. Ho hum!
January 9th, 2008 at 5:19 pm
My WHS has been sitting idle for quite a while because of this bug.
January 9th, 2008 at 5:23 pm
That’s bonkers - backup, remote access etc still works fine with no issues. Just follow the guidelines on editing files direct on the home server and you’ll be sweet.
Terry
January 10th, 2008 at 1:51 am
Miles
You must get yourself a battery backed up power supply for your home server! Will sort out issues like that one for you.
Check out http://www.wegotserved.co.uk/2007/06/17/how-to-install-a-battery-back-up-power-supply-to-your-windows-home-server/ for more…
Terry
January 11th, 2008 at 6:19 pm
So… what constitutes editing files? Changing the touch time (last acccessed)? Does storing data on a RAID setup make the bug more likely to effect files?
I think the problem is that it appears MS is playing dumb here. They have a fantastic product in WHS, and very talented software engineers, but they just discovered this after months of forum postings describing it? It shouldn’t be too hard to isolate, since WHS is built on server2003 and that product does not suffer from this bug. It’s the versioning service or drive extender, just lets us turn that off until it’s fixed.