Windows Home Server gets a big bug fix (and much more)

Windows Home Server gets a big bug fix (and much more)

Summary: Microsoft today announced that it has released a public beta version of Power Pack 1 for Windows Home Server. It’s more than a service pack, with at least two significant new features and a long list of enhancements. Forget about the new stuff, though. Every Windows Home Server user wants to know: Does this update fix the data corruption bug first uncovered late last year? The short answer is yes. The longer answer is yes, and the delay was worth it. Here's an inside look at what you can expect from Power Pack 1 and how you can get your hands on it.


That noise you just heard from outside Seattle was a collective sigh of relief, as Microsoft announced that it has released a public beta version of Power Pack 1 for Windows Home Server. It’s more than a service pack, with at least two significant new features (client support for x64-based Windows machines and the ability to back up data from the server to external media) and a long list of enhanced features. Under normal circumstances, I’d be writing first and most about those new and improved features and comparing the improvements to the initial release of Windows Home Server last year. But instead, I’ll be answering the question that every Windows Home Server user wants to know: Does this update fix the data corruption bug first announced late last year?

Windows Home Server gets the big fix

The short answer is yes.

The longer answer is "yes, and the delay was worth it." Power Pack 1 was originally announced five months ago at CES, but its public debut was pushed back to await the fix for the data corruption bug. What was supposed to be a quick fix turned out to be much more complex. The underlying problem, according to official announcements and confirmed by insiders I’ve spoken with over the past few months, was buried deep in a crucial Windows Home Server component: the Drive Extender feature. On any system with two or more hard drives installed, this code handles the process of migrating data between drives and duplicating shared data to protect it from data loss caused by hardware failures; if this code failed, the files being migrated were damaged, usually beyond repair.

To make sure the bug was fixed, once and for all, Microsoft did a top-to-bottom code review of all the interactions between the Drive Extender functionality and the underlying file system. How serious was this review? A veteran Microsoft developer, one of the four original architects of NTFS, was lured back to work full-time with the team reviewing and fixing the code.

This release is faster and more polished than Windows Home Server v1, and it appears to be as bulletproof as the Windows Server 2003 code on which WHS is based. Over the past few weeks I’ve tested release candidates of this beta code on a pair of test systems. During that time I’ve backed up 10 separate computers daily - more than 200 hundred individual backup sets - and I've performed more than a dozen full and partial restores without a single failure. Basic operations like transferring files and opening backup sets from the server are noticeably faster than they were in the original release of Windows Home Server. I’ve added and removed hard drives and transferred many terabytes of data between a wide assortment of Windows XP and Vista clients and other members of the Windows Server family. In all those file operations, I haven’t seen a single data hiccup.

Microsoft is confident based on its internal testing and feedback from the first wave of beta testers that the data corruption bug is squashed for good. In the blog post announcing the availability of the PP1 beta, General Manager Charlie Kindel said: "We are running this public beta with the aspiration that we will get thousands of beta testers to help us prove that we not only have fixed 'the bug,' but have significantly improved all parts of Windows Home Server..."

Although this is billed as a beta release, I have no hesitation in recommending it for any Windows Home Server installation, provided that you first read and heed the release notes.  (Seriously, read the notes first. They’re well written and useful and contain a warning or two that might apply to you.) To download an update package for your existing Windows Home Server system, go to Microsoft Connect and sign up for the beta. If you want to start from scratch on a clean system, sign up for the beta and download the full evaluation version (good for 120 days), available in ISO format.

The look, feel, and basic operation of Windows Home Server haven’t changed noticeably in this update, but just about every feature has received some polishing. Here's a quick summary of the Power Pack 1 feature list:

  • Connector software for systems running x64 versions of Windows Vista. With this client software installed, x64 users have access to every feature available in the x86 version, including backup and management via the Windows Home Server console. (And to anticipate one question: The new x64 connector will not work with older builds of Windows Home Server.)
  • Server backup capabilities. Using this build you can plug in an external hard drive and designate it as a Server Backup drive (see below), which you can then use to back up the contents of shared data folders on the server. (Microsoft previously announced that this feature would allow backups of the backup database as well, but that capability was cut from the feature list and will not be available in the final Power Pack 1 release.

Windows Home Server data backup in Power Pack 1

  • New restore media. The boot CD used to restore a backed-up image to a client hard drive now includes two images, one of which is designed to work better on machines (typically Windows XP clients) that have 512MB or less of installed RAM.
  • Backup and restore enhancements. The updated client software allows you to disable backups when a machine (especially a notebook) is sleeping or hibernating. Both backup and restore capabilities have been tweaked to make them better able to withstand network connection problems.
  • Remote access enhancements. The process of retrieving files over a remote connection is considerably more usable, with drag-and-drop support in IE6 and IE7, plus the ability to package a group of files into an archive (in Zip format) before beginning a download.

As it turns out, the data corruption bug affected a very small number of users (HP executives tell me they received virtually no support calls on the issue, and my informal survey of beta testers confirmed that this bug was hard to hit and even more difficult to reproduce). Given the extensive amount of testing this release has received over the past few months, I expect the public beta to be a short one. Microsoft says they won't speculate on final release dates until they have a thumbs-up from thousands of external testers, but based on what I've seen I expect the final release to appear sometime next month. Between now and then, I’ll take a closer look at the state of the Windows Home Server platform and its competition.

Topics: Software, Data Management, Hardware, Operating Systems, Servers, Storage, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • gr8 news

    Thanks for the update!

    The next thing i would expect them to update is from WMC 2.0 to WMC 4.0 that would solve all my issues with streaming content to Xbox 360 and will position WHS not only as a backup server but also as a Complete Media Server.
  • The connector didn't run on x64 Vista???

    If Microsoft is to encourage x64 adoption they need to ensure ll of their software works on x64 versions of Vista. There is no excuse for the initial client failing to run on x64 Vista.
    • No 64bit Support?

      That kind of surprises me. I would have thought that the initial release would have supported x64, which is what I use. It *is* a bit frustrating not to have x64 supported out of the box. What was Microsoft thinking? At least it should be an issue now.
      Ross Snowden
    • No 64 bit? No buy-in from me!!!!

      64-bit or death! :)

      Seriously, if MS wants 64-bit, then it's got to be everywhere.
      • X64 is supported.

        The new connector software does work with X64. Not just Vista X64, but XP X64 too!!! I think what he was trying to say is that the new connector software will not work on a non-PP1 updated WHS system. They are separate downloads. Installed it on my XP X64 system and can FINALLY backup the X64 computer, along with the others in my home. GREAT UPDATE!!!
        • XP 64

          How did you get the connector to install on an XP 64 box? I have been trying for two days and the setup finds my server, installs the software, and then an error message pops up saying the process couldn't be completed.
  • RE: Windows Home Server gets a big bug fix (and much more)

    so is this ready yet? or should I wait?
    • I answer both of those questions in the post

      Read again... It's still a beta, but I recommend it as long as you read the release notes.
      Ed Bott
  • RE: Windows Home Server gets a big bug fix (and much more)

    Yawn. Is anyone interested in this? Has anyone apart from Ed bought one? Actually I bet Ed got his courtesy of MS.
    • I bought the OEM version...

      ...but I'll monitor the beta forum for a while before I add this. Unintended consequences, you know...
    • Bought it and love it

      I built my own home server and purchased WHS OEM version from It's been running constantly since January '08 without a problem. I am one who happens to be interested in WHS articles! There happens to be a nice community out here that use WHS, shares information about the OS, and produces WHS software. Give it a try before giving it a 'yawn'.
    • hell yes!!

      I have been waiting for this bug to be fixed. I will absolutely buy one. The bug was the only thing holding me back. I have two computers and run a small business from home. This would totally remove any backup concerns and allow me to access data remotely. whats not to love?!?!? yeah, sure, I can build my own server for cheaper - whatever. I dont want another loud-a$$ space heater in my house. this thing will be MUCH quieter, MUCH smaller, MUCH cooler temp than anything else. I generally have disdain for Microsoft but I love Publisher and I love windows home server. I will buy the HP product as soon as this release comes with it.
  • State of the company???

    When this has to happen:

    "A veteran Microsoft developer, one of the four original architects of NTFS, was lured back to work full-time with the team reviewing and fixing the code."

    What does that say??? The people still there must be feeling really great about that. of us looking on from the outside oughta kinda wonder what that tells us, too - i.e. is the quality of developer at M$ on the decline?
    • Kernel knowledge

      For some of their code, they called in one of their best programmers with intimate knowledge of the kernel's workings, to make sure the code was of the highest possible quality. I fail to see how getting expert advice is a bad thing.

      Updated to add: Other companies do this as well. Google hired Vint Cerf, one of the original architects of the Internet, to work with its developers. Is that a failing on Google's part, or a smart move?
      Ed Bott
      • great point!!

        I agree
  • RE: Windows Home Server gets a big bug fix (and much more)

    Still needs a bug fix. I have 3 machines on my WHS which are backed up daily. Yesterday I tried to add a fourth, a laptop. Installation progressed, and then I was informed that the laptop couldn't be backed up because the drive was FAT. Jokes aside, the drive is NTFS. Then I was informed that WHS couldn't get access to the computer. Sorry, but I can see it from anywhere on my network and vice versa. No manual backup, no automatic backup, doesn't see the machine, thinks NTFS is FAT - this is robust? Hearing from others who joined me in local beta, they are having trouble as well. Hmmm. Maxtor Safety Drill is looking better and better.
    • Have you reported that?

      I've been monitoring the private beta groups closely and haven't seen any reports of that issue. I'm sure the development team would love to get a report from you so they can try to reproduce it and, if it is a bug, fix it.

      You have access to beta forums and tools to report bugs. If you don't report it, how do you expect it to be fixed in the final version?

      The dev team has been very responsive to bug reports, in my experience.
      Ed Bott
      • Didn't happen in Beta

        In Beta, I had just set up the three machines and everthing worked. When the Beta expired, I installed the production release (2 days ago - I have been away from home for 3 months), and all went well with the original three machines, save for a glitch removing an old member of the storage pool during a needed expansion, which I resolved with a PO restart. It was not until the fourth machine came into the picture that the issue arose. I'm working through what might be the source of the problem now, but when I mentioned it to another Beta tester, he said he had been having problems as well - I will find out more Saturday at our club meeting. I mention it here because I find it anomalous that the client connector software would come up with so off-the-wall a malfunction as to mischaracterize a file management system (FAT?), and to solicit from others whether they, too, have seen this. When I try to configure backup, the client appears not to respond at all, which may be an artifact of the FMS misidentification. More when I know more.
        • Public newsgroups

          Have you searched the public WHS newsgroups or reported it there? Might be a known issue or might be a weird hardware-related issue.

          Good luck sorting it out.
          Ed Bott
          • Anything's possible

            Could be a weird hardware issue, although the laptop is not one of the "Joe's Lobsters, Snow Plowing, and Laptops" brands, but rather a Dell Inspiron 1000 running SP2 Home, which I use through an Extigy as a music server (thus the interest in WHS as a back end). I have not searched newsgroups or otherwise, since I want to review the configuration history of the machine and move to SP3 and retest first. I will also be adding a Vista machine and some other configurations to see if it's isolated or common to all machines not originally in the Beta suite (I did an upgrade in place rather than a fresh install of WHS to keep the existing backups in place while I meddled). Scandisk seems happy, and CONVERT confirms the NTFS reporting, so, onward.