RSSMicrosoft promises data corruption fix in final Home Server Power Pack
By Nate Mook | Published July 21, 2008, 4:13 PM
7 months of beta testing later, Microsoft is finally ready to say it has squashed the data corruption bug that has plagued Windows Home Server since its launch last year, releasing the final build of Power Pack 1 to existing customers and OEMs.
The update to the company's operating system designed to function as a media server in the home was originally slated to include features such as backing up of shared folders, Vista x64 support, more efficient power consumption and improved performance. However, the release was delayed so Microsoft could figure out, and a include a fix for, the data corruption problem.
The issue occurred when certain programs were used to edit or transfer files stored on a Windows Home Server-based computer that has more than one hard drive. Applications that caused the corruption included: Windows Vista Photo Gallery, Windows Live Photo Gallery, Office OneNote 2003 and 2007, Office Outlook 2007, Money 2007, SyncToy 2.0 Beta, Intuit's QuickBooks, and uTorrent.
Why did it take so long for Microsoft to resolve the bug? After isolating the issue, the company was forced to completely rewrite the storage subsystem for Windows Home Server. A beta release of Power Pack 1, which Microsoft hoped would "prove we fixed the bug," was released last month to testers to make sure nothing was missed.
"Our OEM partners will be updating their systems with Power Pack 1 and HP will release a software update for the HP MediaSmart Server, delivering enhanced media streaming capabilities from PacketVideo, server-side anti-virus from McAfee and compatibility with 64-bit home PCs," the Windows Home Server team wrote in a blog post Monday.
The English version of Power Pack 1 -- which brings Home Server to build number 1800 -- can be downloaded now, with German, Spanish and French versions coming soon. Those who do not download the update manually will receive it automatically in August, when Chinese and Japanese language versions become available.
Microsoft sells the Windows Home Server to OEMs such as HP who utilize the OS on their hardware systems. However, it can be found and purchased on its own through some retailers, although Microsoft won't provide direct support services.
I heard that the bug was intermittent and hard to reproduce, and that was one of the reasons it took so long to fix.
More discussions on how it's going are over on mediasmarthome.com.
Score: 0
I've had an HP MediaSmart Home Server for several months and having heard about the data loss issue have been reluctant tp put too much important data on it.
having just installed the update though I have seen a big performance increase and so i would say that the info on the pack is correct (there are a lot of bug fixes as well as enhancements in the update which is why it isn't being called a SP bt rather a PP or Power-Pack).
I have previously updated the CPU and RAM on the device and even then didn't see such an improvement as I have installing the PP.
The biggest thing I've noticed is that data transfer to\from the server and the balancing of data over the disk array is much much faster which itself makes it worth installing as that really sucked before.
Score: 0
Woohoo! Finally, a patch to the bug I could never induce. Wait, what?
Ah well. Perhaps they've sorted out some of the other niggling issues with WHS. Still, probably Microsoft's greatest product, IMO. It's the only MS product I haven't had trouble with. :/
Score: 0
I thought they had fixed that a month or so ago...
Guess not.
Suffice it to say that a server that corrupts data somewhat lessens its value.
Regardless of what you think of MS, this is not a high point... In fact, its one of those moments that if someone had suggested it, no one would have thought it possible...
Score: 0
It was fixed a month ago but it still was in beta so MS wanted to make sure before it was publicly released that they have squashed it...
This is the final release now available to everyone
Agreed on the high point I have a free evaluation copy I been putting off using until this was fixed...
Score: 0
It took seven months because "after isolating the issue, the company was forced to completely rewrite the storage subsystem for Windows Home Server".
I'd much rather they take 7 months rewriting a poorly coded subsystem than cobble together a fix which sometimes leads to more problems (as MS usually end up doing).
Good on Microsoft.
Score: 0
I agree in principle, but why the hell didn't they make it properly to begin with?
It's a large error to miss after all, considering storage is pretty much the entire point of having Home Server.
7 months with that problem isn't a fun time. Surely with their large workforce they could have gotten another couple of people in to help (including training them with the new code inside that 7 months).
Score: 0
Because the combination of programs that was causing the issue didn't show up during testing, so it was actually easy to overlook
Score: 0
Because I've tried inducing the error with the programs they list and I can't do it. It's not surprising they didn't find it either. Despite what many say, it's a fairly rare bug.
Score: 0
7 months.
Need I say more..?
Score: 0
Nope.
Ever. ;)
Score: 0
I should have seen that one coming...
Score: 0