The Windows Home Server team has been heads down working on the data corruption issue since we first posted the Knowledge Base (KB) article in late December 2007. An update to the KB article was posted today that provides more information regarding symptoms, cause, status and guidance. You can read the KB at http://support.microsoft.com/kb/946676/en-us.
One question that is getting asked is, “Will I be affected”? We are aware of only a very small percentage of users with confirmed instances of this issue, and we believe that most people are unlikely to be affected. In the KB article we offer up some precautionary measures that people can take. Some of the instances that were initially attributed to this issue ended up being something else, such as a faulty network card/driver, old routers with outdated firmware, or people incorrectly testing the limits of their home servers.
From the outside looking in, some people would say “Why is this taking so long?” Fixing this issue is the Windows Home Server team’s top priority and the team is making good progress on the fix. We understand the issue really well at this point - it is at an extremely low level of the operating system and it requires thorough testing to ensure that the fix addresses the issue. We have coded a part of the fix which is currently being tested internally. Internal testing is expected to continue for at least several more weeks.
Once the patch has passed internal quality bars, external participants will be asked to help test the fix. Our current plan is to release beta test versions of a fix over the next few months, with a final version currently estimated for June 2008, although that date could change as testing progresses. Thorough testing of the fix is critical and will take time.
If you believe you have evidence that you are experiencing the issue, please send a detailed email of your circumstances to email@example.com, so we can attempt to validate the cause and provide specific guidance. Thanks for your continued support.
The Windows Home Server team
Acknowledging the "data corruption bug" that's been ravaging Windows Home Servers since Christmas, Microsoft today warned users NOT to: • "Use applications to directly edit or change files stored on Windows Home Server" • "Use media management
Setting shared folder permissions to read-only, and to not use application that could directly edit files store on your WHS? So is it still safe to say this product is a Home Server? Because the "workarounds" given in the KB kind of say otherwise.
Because if it's strongly suggested to not do anything of the above, it's not really a storage server.
I was planning on installing a second hard drive in my WHS, but I'm thinking of holding off now. Since I do use applications to directly alter files stored on my home server.
No, it's not fixed yet, but here's a bit more information : The Windows Home Server team has
If you have questions about this issue, please see this thread:
in the Windows Home Server Community forums
Will this June release include "Power Pack 1" or are you releasing a patch solely for KB 946676?
If you have questions about this issue, please see visit the Community Forums:
So are you now going to release Power Pack 1 ahead of the hotfix? The june fix date for this hotifx is only provisional and could take longer, it seems daft to make people wait that long to get all the additional functionality of PP1 in the mean time.
Todd Headrick has asked if you should do this on the Home Server forums;
The overwhelming opinion so far has been "Yes, release the powerpack now"
So is this going to happen now please???
I've posted you on dzone so you can't moderate comments. cheerio!
Filed under: Desktops , Media PCs , Storage Remember that tiny little Windows Home Server glitch that
The WHS team has an update on their blog regarding the corruption issue. In short, they fully understand
This morning I realized that one month ago yesterday (3/24) I arrived bright and early to building 43