Broke 0.9 Vistas Fixed officially acknowledged Dec 20, 2007 their #11 worst broke on record

Windows Home Server: the safe place for your files, terms and conditions apply

Windows Home Server could silently corrupt files edited directly on the server

↳ caused by Windows Home Server (2007)

The market's verdict: +5.2% on MSFT in the week after.

Status: Fixed. Working as intended, eventually.

What actually happened

On December 20, 2007 Microsoft formally warned Windows Home Server owners that editing certain files directly on the server, rather than copying them down first, could silently corrupt them. The list of risky programs included Outlook, OneNote, Windows Live Photo Gallery, SyncToy and Money, which covers most of what a family actually does with files. This was a product whose entire reason to exist was being the safe place for those files. The official workaround was to copy files locally, edit them, and copy them back, the exact chore people bought the server to eliminate. Power Pack 1 shipped the real fix on July 21, 2008, seven months later.

This one is officially acknowledged.

Were you affected? Unbreak it

Fixed in Power Pack 1 (July 2008)

Microsoft has acknowledged this issue; a fix ships in an out-of-band or next cumulative update. Check Windows Release Health before manual workarounds.

Timeline