HP Statement on Data Corruption Issue
Paul Thurrott’s SuperSite for Windows Blog have published a statement issued by HP over the data corruption issue. Paul’s blog also state that HP hasn’t had anyone call in with this issue to their support line and that the issue isn’t even a top five question from customers seeking support. Which suggests that as we have always stated that the issue is indeed rare, especially as the MediaSmart Server is the best-selling WHS solution that’s currently available.
HP’s Statement:
HP has been in close communication with Microsoft on the Windows Home Server data corruption issue. There are two points to remember: we are only aware of a small percentage of customers with confirmed instances of the issue, and it occurs only when utilizing certain programs on Home Server systems with more than one hard drive. We understand disappointment with the estimated June delivery of a fix. But we also understand the challenges MS faces in reproducing bugs that occur so infrequently, the complexity of finding the right solution, and the need to complete extensive testing to ensure the bug fix is done correctly. HP is working with MS and is providing engineering and test resources to expedite this fix. With all the complexities of various operating systems, numerous applications, the variety of networking components, and the layers of software on top of Drive Extender, the testing will, in our experience, take some time to complete. Until that time, HP recommends that all HP MediaSmart Server owners follow Microsoft’s recommendations to ensure their data remains safe. More information can be found on Microsoft’s web site.
Paul Thurrott’s SuperSite for Windows Blog.
Share this WHS Article with Others:
Why is it that WHS zealots require passionate and inept enthusiast?
Microsoft and HP are just down playing the whole data corruption design flaw. That’s obviously as why, because they stand to lose customers knowing how their data is at risk.
Just think, if everyone knew there’s a design flaw in WHS that leads to data corruption with just about every Microsoft software application that connects with WHS from a PC client, who would feel fuzzy and all warm with that?
Common sense tells you that data corruption is a very serious problem. Maybe you don’t mind having your family videos, photo albums, financial data files, and everything else corrupted because you forgot to adhere to the many specifications by Microsoft not to edit or transfer files that are stored on a Windows Home Server-based computer is just totally inexcusable.
I know of at least a dozen of my customers who have returned back their WHS products due to this fiasco catastrophe. And yet, Microsoft continues to delay, put off and wait to bring relief to those who already purchased WHS as paying customers.
So why is Microsoft like HP still selling WHS with a proven design flaw knowing customers are at risk of data corruption?
Imagine Ford or Toyota selling a proven defect like brakes failing without warning, and be able to get away with it?
WHS should have been recalled immediately upon discovery of this serious design flaw.
I am really getting peeved at all the reports that this bug is very rare and only affects a small number of users.
I have had this problem ever since I first began using WHS, and had the data corruption issue kill my OneNote files 2-3 times per week. I was working directly with MS on this issue back in September & October. I can easily continue to reproduce this problem should I continue to use OneNote from a WHS share – which is a recommended mode of using OneNote for sharing and synchronizing notebooks across computers.
I have had to give up on using OneNote in this manner, and have stopped using Windows folder re-direction to point my home folder to WHS as many program read/write to the Documents folder directly. I have had many documents become corrupt, including 10 years of financial history stored in MS Money.
This product had some small appeal when it first come out for a niche market. Geeks that love MS stuff, that want a server with the SBS 2003 features like RWW but less complexity and more media focus.
This bug coming out early after its release and Microsoft’s less than speedy fix basically killed it. If someone were to ask my advice about this product, it would be a “NO WAY IN HELL” type of answer.
On December 21st, Microsoft announced that in some situations, customers could experience data corruption/loss when using Windows Home Server.
What has Microsoft done to resolve this problem? Check back in June 2008 please…
That’s a “wow” experience if I ever heard such a fish story!
I wonder what would have happened if such a bug had remained in the “corporate” Windows 2003 R2 server version.
WHS isn’t a corporate product, and thus being sold to consumers, Microsoft allows this design flaw to occur.
I have to say that I am a bit disturbed (and frankly on the edge of mad) about where we are in regards to this data corruption bug combined with the release of a new WHS operating system. I’m mad at myself about not doing proper research prior to purchasing my system – simply assuming that it would ship working as I needed it and that it would be at least a year before the thing is obsolete.
As far as I am concerned, if I cannot use the shared folders to share files (aka edit from various PC’s around the house), it is simply a huge backup drive to me.
I’m also disturbed that this bug will not be fixed until approximately the same time as the next WHS OS is released.
Unless there is a compelling reason to keep WHS, I’m sending it back! Anybody feel the same way and/or can give a compelling reason to keep it? Please – help me out!
Does that data corruption bug bother me – damn yes it does. It shows how piss poor Microsoft’s internal quality control is.
Microsoft’s strategy may well be to incourage every WHS version 1 user to purchase WHS v2 (Vail) here. Otherwise, why upgrade a system that finally works?
All Microsoft will say, is in that the all new and improved WHS is better than before. Only, how does that help everyone stuck with older and now obsolete, not to mention, broken WHS version 1?
Like others, for now I use only one disk in WHS. Only I had bought it with two (HP EX475). I’m very frustrated at the lack of x64 support and second with the data corruption bug too.
I just regret not waiting since I won’t be able to use tWHS for 50% of what I bought it for. Thanks for Microsoft making me a dumb ass.
In reality WHS is a dud. The KB 946676 corruption bug renders the WHS almost unusable. Personally, I cannot wait for the fix, so that I can once again use my WHS for what I bought it for. I bought into the promise of what WHS could be, not into the WHS beta testing program for what it actually is.
I read in “Windows Home Server for Dummies” that 512k was all the server needed and no performance would be gained by adding more memory! Had I known about the data corruption bug before hand I would most definitely had not purchased WHS!
Microsoft keeps telling me that I need to learn to live with the “bugs”. Not to mention the aftermath of experiencing data corruption. Which we all know Microsoft isn’t going to recover the lost data that they caused. If that isn’t harmful, how could it be any worse?
The only thing necessary for the triumph of evil is for good people to do nothing about it.
Thanks for all of your replies! It has given me a bit of insight as to how you all are taking this news and gives me a sense of understanding of what my expectations ought to be.
With all due respect, do you really need a server to perform backup and read-only sharing? It seems a less expensive NAS ought to do what you want (and more – you’d even be able to do sharing without read-only).
The worst part is not knowing, & not having an easy way of finding out, whether/if any of my files were corrupted (short of testing them one by one) or whether they’re all fine.
Most have purchased the EX470 for around $549, which is essentially now a 500 GB NAS drive, or about $749 (the EX475, like me) for a 1TB GB NAS drive. I do not see this as a wise expenditure.
Error found in the event file.
Unexpected error 0×6 from CreateFile on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{38BEFB10-ED3F-4681-A3DE-DB5789B78A93}.Machine.configdat: The handle is invalid.
Since that, the backup service stops. So now on my HP EX475 I cannot even backup my PC clients! And everything says the data corruption glitch has nothing to do with backup!
For the life of me, I cant see why anyone would use WHS as ONLY a backup device. And just because you don’t use it as more than a backup device and you don’t experience the trouble some of us are having, doesn’t mean the BUG is unimportant!!
HP’s WHS has been named/marketed as a ‘MediaSmart Server’. It was built on MS Windows SERVER 2003 technology. To imply on this and other threads that it was never meant to be more than a backup device and that problems occurred when they tried to add other features (such as becoming a FILE SERVER) is wild speculation at best and at worst, is simply… WRONG.
I never edit files directly on the WHS because it’s too slow anyway.
“A bug has been discovered in the redirection mechanism which, in certain cases, depending on application use patterns, timing, and workload, may cause interactions between NTFS, the Memory Manager, and the Cache Manager to get out of sync. This causes corrupted data to be written to files.” – Microsoft KB 946676
This is a clear case of using confusing or overwhelming somebody by giving an impenetrable explanation using technical terms and concepts if I ever heard before.
Come on Microsoft, get it fixed, be honest and open up!
It’s not just WHS that’s broken!
Court papers reveal 18 percent of Vista system crashes trace back to Microsoft.
See Article:
blogs.pcworld.com/staffblog/archives/006726.html
Is it any wonder WHS suffers with design flaws as well!
A huge amount of Vista failures, crashes and reboots!
The list documents “Crashes by Organization” for all file type drivers. At the top of the list is Nvidia with roughly 480,000 crashes, or 28.81 percent of the total, followed by Microsoft (17.97 percent), Unknown (17.07 percent), AMD-ATI (9.30 percent) and Intel (8.83 percent). Webroot Software (3.99 percent), Realtek Semiconductor (3.34) and Creative Labs (1.09) are the only other organizations with more than 1 percent of driver crashes on the list.
Source: http://www.crn.com/hardware/206905475?pgno=1
Was Microsoft’s flagship Vista OS ready for prime time?
Is WHS ready for public release?
It’s more than obvious, Microsoft is selling unfinished, beta ready products upon the public! Is it any wonder KB 946676 remains unfixed?
Nvidia users believe they were victims of fraud and bad business practices on the part of Nvidia and some of its manufacturing partners. So they put together a website to gather support for a class action lawsuit.
See here: nvidiaclassaction.info/thefullstory.html
Microsoft users can do the same! If you feel you were victums of fraud and bad business practices on behalf of Microsoft, here’s our chance to get things straighten out, once and for all.
Why should Microsoft continue to sell WHS with a proven design flaw, that causes data corruption?
Why shouldn’t Microsoft fix this proven and admitted design flaw in a reasonable amount of time?
Why should we accept data corruption to be live with it, as if that’s what we bought to use Windows Home Server for?
I’m sure someone can add to the list, and help get Microsoft to do the right thing!
We bought a product called WHS that does not work properly, period. We deserve reparations!
Bring on the WHS Class Action Lawsuit!
When people started reporting WHS bugs during the beta period about data corruption, with this severe problem, Microsoft ignored them to put WHS into production as a final release product for the public to purchase with an already known harmful and serious design flaw in their product.
And guess what, Microsoft is still selling Windows Home Server despite it’s KB 946676 warning about data corruption that occurs under a wide use of situations that end users must take steps to reduce the many risk such as with Microsoft’s own applications like:
Microsoft Windows Vista Photo Gallery
Microsoft Windows Live Photo Gallery
Microsoft Office OneNote 2007
Microsoft Office OneNote 2003
Microsoft Windows Media Player 11
Microsoft Office Outlook 2007
Microsoft Money 2007
Microsoft Office Excel
Microsoft Digital Image Library
Microsoft Zune Software
Microsoft Virtual PC 2008
Microsoft Project 2000
Microsoft SyncToy 2.0 Beta
Is that what everyone using WHS expects? Unsupported file sharing in a server?
Hewlett-Packard’s message of using WHS is as follows:
“You should not directly open and/or edit files that are stored on the MediaSmart Server while doing any other activity such as large data transfers or media streaming. If you are doing a large data transfer or streaming and need to edit a file on the server, you should first copy the file over to a PC and then open it for editing.” – HP
How is this product what we bought a Home Server for? Just don’t use it as intended and advertised!
HP recommends that all HP MediaSmart Server owners follow Microsoft’s recommendations to ensure their data remains safe.
That’s like telling passengers flying aboard an aeroplane, bring your own parachutes, as we don’t and didn’t expect to actually land the plane! You’re just coming along for the ride of your life!
Since Microsoft hasn’t provided any resolution with their proven known design flaw (KB 946676) and it appears perhaps only something ahead, apparently around June 2008, I’ve decided NOT to wait, being how I bought WHS in December 2007.
HP provided me with a refund of the total purchase. I advise everyone else to do the same. If someone manages to proceed with a class action lawsuit, all the better, because Microsoft knows better than this, and they ought to be made reasonable!
Microsoft’s biggest lemon – Windows Home Server
blogs.zdnet.com/hardware/?p=1499
“Windows Home Server has the capacity to hose your data. For an OS, that’s bad, but for a filer server OS, that’s a disaster.”
Even Microsoft technology evangelist Volker Will lost a considerable amount of data to Microsoft Home Server.
blogs.msdn.com/volkerw/archive/2008/01/16/stay-at-home-server.aspx
According to a blog post by the Windows Home Server team the current estimate for the release of a patch is June 2008 – nearly a year after Windows Home Server was released.
Remember, how many times we were promised how the Windows Home Server Team was working through Christmas, and that the fix would be soon.
If this is soon, can you imagine what is delayed?
I agree, there’s no excuse for releasing a file server OS containing such a critical flaw, and there’s no excuse for a fix to take so long, leaving users with data corruption!
Microsoft isn’t going to recover your destroyed files, photos, videos and data!
Want more aggravation? Just use WHS with Vista! Double trouble mixed together. Data corruption and BSOD.
If anyone is thinking of buying WHS or Vista, don’t.
Microsoft’s internal quality bars suck! Plain and simple. They didn’t catch it the first time, then during the 100,000 beta stage as they obviously released WHS upon the public, and think to tell us again, we shall wait more to insure it passes our internal quality bars.
WHS is no less like a terrorist, because it holds all your data at risk, of destruction! While WHS customers suffer data loss hoping their WHS data get tossed a life preserver before downing! Otherwise, it will be too late, if not for some already as note above!
Bring on the class action lawsuit! This has gone far enough!
Pretty much ANYTHING that modifies file attributes can hose your data in WHS via your PC client. For example, even Windows Media Player can do it! So, don’t believe Microsoft’s claim that only a handful of apps are affected.
I would have thought that file integrity would have to be NUMBER ONE one any file server.
Not to mention, carefully backing up the flawed file doesn’t help you a bit.
As for backup can WHS backup from a machine that’s running OSX, Linux, BSD, Solaris, or a PS 3?
Answer is NO. So why even use WHS unless your just stuck on Windows buggy code that is in need of constant patches, updates, service packs and even power packs that still just don’t offer to provide even a data corruption fix!
What does it take? Apparently, a class action lawsuit on behalf of everyone!
Microsoft claims that this problem only affects a small number of users (customers)…” So did the Pinto rear end collision fires. Which brings us to you, that is would you be one of “those” before or ahead to experience something horrible too? Why even take the chance? Or rather, why should anyone need to?
WHS leaves the purchaser with two choices: 1) lose valuable data or 2) live in mortal fear of losing valuable data.
WHS has the set-up for multiple disks, so it is absolutely normal to think it will work well with MORE than one disk, but it does NOT.
How can there be a low-level problem in Windows Home Server if it’s really based on Server 2003? This is beyond bad. This is awful.
Do you want your accounts receivables in QuickBooks to vanish? Do you want your Outlook e-mail store to disappear, or those of you who are running SharePoint on Home Server to possibly see all your collaborative work to disappear into a black hole? I don’t think so!
eWEEK’s Joe Wilcox pointed out in a recent blog, Windows Server and Windows Vista share common code legacy, and Vista is “notorious” for file-copying problems.
So why was WHS shipped when the bug was already known?
Microsoft only plans to dominate software, web services, CRM, ERP, digital media delivery, format standards and Operating Systems. No single company can control “everything”, Microsoft only wishes to control how you get everything.
That is why under “BallmerSoft” they will be having a BIG move to software as a service. While third party providers actually produce the software for them.
Then when something goes wrong, it’s NOT Microsoft’s fault, despite pedaling and distributing the planet Earth. This will make it even easier for Microsoft to switch providers, be China or some developer in India.
Microsoft should be careful about their products for living up to what they advertise it to be and be careful it does what they say it will do; that’s the lesson that many tech companies are learning the hard way.
Microsoft recently found that out as its facing an uphill battle to fight against a class action lawsuit alleging Microsoft intentionally deceived using “Vista Capable” stickers!
Note: Apple’s bold advertising claim that its MacBooks support “millions of colors.” The only problem — MacBook LCD are only 6-bit TFT models, only allowing for only 262,144 colors.
If people don’t stand up to this fraud, corporations like Microsoft just get away with anything these days, even data corruption by having us end up paying for our own data destruction.
Stand up and demand resolution! No more delays, no more excuses!
Because, of the Windows Home Server data corruption fiasco, Microsoft will certainly need to apply new labeling stickers on their products, that read as, “Works For Sure” as nobody is going to believe or trust Micro-BUGGY-crap again.
Especially, since broken WHS (with a proven design flaw that destroys your data) continues to be sold to new customers by Microsoft.
If that wasn’t all, consider the nightmare trying to upgrade to Vista SP1?
See this here:
blogs.computerworld.com/my_nightmare_trying_to_upgrade_to_vista_sp1
I feel Microsoft should suspend sales of WHS until the data corruption design flaw is fixed.
Microsoft officials acknowledged this week that they are not going to release until June a fix for the serious data-corruption bug affecting Windows Home Server (WHS) that was first discovered months ago and affects the back-up of a growing number of Microsoft and third-party applications.