Home Server fix delayed until June

Home Server fix delayed until June

Users of devices like this HP MediaSmart Server will have to wait until June for a bugfix to be released.

Those of you running Windows Home Server will be disappointed to hear that a bug first covered here in December is still on Microsoft's “To Do” list.

To recap, the flaw results in files edited directly on the server – as opposed to being edited on a desktop and then manually copied to the server – having a non-zero chance of vanishing completely. Not what you need from a server that's supposed to be your primary document store, really.

A post to the Home Server Technet blog on Monday has offered scant hope for users still trying to gingerly work around this issue. In the blog posting – signed by “The Windows Home Server Tearm” - the issue is described as the team’s top priority. The post also promises that “the team is making good progress on the fix” and understands “the issue really well at this point.

From there, the news takes a turn for the worse. Describing the glitch as occurring at “an extremely low level of the operating system” the team claims to need “several more weeks” to test the fix that has been written to address the flaw. After that, a beta version of the patch will be launched.

The long and short of it is: if you're currently experiencing this issue, you'll have to find ways around it until June this year at the absolute earliest – six months after the flaw was reported to Microsoft.

Until then, the advice from the original KnowledgeBase article applies: “use Windows Explorer or a command-line tool to copy files to and from the Windows Home Server-based computer” and “do not use applications to directly edit or change files that are stored on the Windows Home Server.

Are you shocked at how long Microsoft is taking to fix a critical bug in its flagship home server product, or do you think the whole issue has been blown out of all proportion? Share your thoughts over in the forums.


Discuss in the forums Reply
Cthippo 12th March 2008, 09:00 Quote
Meanwhile, my WinME based server contines to chug along without any issies whatsoever. How did they manage to screw this up so royally?
WildTangent 12th March 2008, 09:09 Quote
This is absolutely ridiculous. Glad I'm using Ubuntu on my file server.
Woodstock 12th March 2008, 09:32 Quote
and they wonder why linux is starting to get a larger user base
cjoyce1980 12th March 2008, 09:38 Quote
WinXP Pro x64 all the way
BlackMage23 12th March 2008, 09:52 Quote
Win2003 Enterprise X64 FTW
jsheff 12th March 2008, 10:11 Quote
I've been using WHS for about 4 months now, and I got caught out by the bug before it came to light. Lost around 1TB of data. Pretty gutting to say the least. Thakfully, none of it was personal data that wasn't copied somewhere else, like my photos or files. Was a bitch to rip all my CDs and DVDs back to the server again, but now I understand the problem I haven't caught the bug again. Basically, if you're going to use the uTorrent add-in, don't download to a server shared folder. It's to do with WHS's storage balancing system basically trying to balance a file that's already open or being edited (i.e. an unfinished torrent, a word document being saved at the time of balancing, tagging a folder of mp3s, etc). I have my uTorrent set to download to an external drive NOT added to the storage pool, meaning WHS will not try and move those files around drives, then once the download is finished, uTorrent moves the completed file(s) to a server share. It is an annoyance, and one that I'm not trying to defend at all, losing data sucks - simple as.
airchie 12th March 2008, 11:44 Quote
That really is useless.

Linux FTW TBH. :)
C-Sniper 12th March 2008, 13:58 Quote
yay slackware linux for my server.
leexgx 12th March 2008, 13:58 Quote
i had this same problem in the beta server as well (but i was running it in VMware with 6x90gb disks in vmware to test it out)

its an bad bug that should of been fixed an long time ago
Woodstock 12th March 2008, 19:17 Quote
Originally Posted by leexgx
i had this same problem in the beta server as well (but i was running it in VMware with 6x90gb disks in vmware to test it out)

its an bad bug that should of been fixed an long time ago

imo i cant believe it wasnt noticed before release, it should not have been released with it.
OleJ 12th March 2008, 20:43 Quote
ROFL! Talk about shooting yourself in the foot with a shotgun :D
Just like any other RTM from MS it's a public beta in disguise.
It's funny how it took MS six revisions of NT to finally release a stable and thorough Windows (XP). Which they then went on and ruined with Vista...

Built on new technology technology :D indeed!
Log in

You are not logged in, please login with your forum account below. If you don't already have an account please register to start contributing.

Discuss in the forums