Update on Windows Home Server Bug Fix

On the Windows Home Server team blog they are reporting that a fix for the data corruption problems will be included in the Home Server Power Pack 1. Beta testers (including me) should get the fix sometime in April to try out.

The team is making great progress on the data corruption issue.  We plan on releasing a beta of Power Pack 1 with the data corruption bug fix to our hardware and software Partners, Microsoft MVPs, Windows Home Server Insiders, and Microsoft Employees in April.   And then based on feedback and additional testing, we currently plan on releasing a public beta in May.  If you are interested in participating in a future public beta, go to http://connect.microsoft.com/WindowsHomeServer to register.  When the Power Pack 1 software is ready for public testing, we will contact the people that have already registered at the Windows Home Server Connect site with more details on the public beta program.

An update regarding Windows Home Server Power Pack 1

About the author Ian Dixon:
Founder of The Digital Lifestyle.com and host of The Digital Lifestyle Show. Started podcasting in 2005, Windows Entertainment and Connected Home MVP. Lover of gadgets from the Raspberry Pi to the iPad, Android to Windows 8. Also a massive motor racing fan
  • Anonymous
    This’ll sort the real beta testers out from the boys. There’s often a tendency to view participation in something like this as a way of getting your hands on cool technology fast and the expectation may be that it might be a little flaky but not that it will corrupt or lose anything.

    We shouldn’t think about it like that, but its hard not to. I wonder what percentage of users really have committed their only copies of family photos or music to this beta release of Windows Home Server.

  • Ian Dixon
    I have never had this bug, since I had the first beta so it looks like a very specific set of circumstances
  • Anonymous
    Hey, everyone using Windows Home Server is a beta tester! 😉
  • Anonymous
    I’d heard it only occurred when editing a file directly on the home server and when the home server has more than one drive. Copying a file to a local drive and then editing and then copying back does not cause the problem. So, presumeably, its related to writing portions of data in the middle of a file (possibly when some other Home Server housekeeping is taking place) which is why only certain programs cause the problem.

    It sounds as though if you treat a file as an atomic unit you won’t fall foul of the problem. The fact that it has taken so long to resolve makes me think that it’s a bit nasty (or a fundamental design fault).

  • Ian Dixon
    I would say its a design problem
  • Anonymous
    Here is my roundup a recent posts, and don’t forget to post your Media Center setup pictures and enter…
This site uses cookies.