Ed Bott has more news on the data corruption bug, specifically the scenario in which the bug occurs and some behind the scenes context around the KB article – worth a read.
There’s been a huge amount of online vitriol poured out around this issue, which is probably to be expected given the seriousness of the bug, but also the time of year, with not a lot of other tech news happening. Some have been questioning the need to backup data on a backup product – I understand the logic, but personally, I’ve always kept a backup of my most important data (photos, music and software) on an external hard drive which is not attached to the home server, ever since my WHS beta days almost a year ago. Why? Well, at first, it was extra protection required for running a beta product. Nowadays, it’s just good practice - copying data to an external hard drive is very easy to do once in a while, so why wouldn’t you?
Do I trust Windows Home Server with my data? More than any other v1 Microsoft product I’ve used. Thankfully I’ve not had any data corruption issues since starting with WHS Beta 2. But would I blindly trust any product 100% with my music collection, wedding photos, holiday snaps? No, and neither should you. If you’re running Windows Home Server without surge protection, without a UPS, without a “doomsday” backup tucked away, then sort it out – now! Windows Home Server provides most homes with the first layer of backup protection, which is fantastic. Software such as Jungle Disk and Keep Vault’s online backup adds a second. I like to also have a third – and it’s on that Maxtor External Hard Drive.
Back to the bug – to date, Ed has the most up to date news – as MVPs, we’ve got the same information as everyone else right now. To be honest, I’ve deliberately not sought out updates from the team, as it’s better for them to be 100% focused on fixing the bug as quickly as possible. With a bug like this, when there’s news to share, it’ll be shared quickly.
We (the WHS MVPs, that is) have our regular monthly update call with the WHS team on Jan 2nd (to which all Microsoft MVPs are invited this month, by the way) at which I hope to hear more. Fingers crossed the fix is already in place by then, but stay tuned for any updates in the meantime.

















