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.â€