Windows Home Server users : BEWARE

[bledd]

http://support.microsoft.com/kb/946676

MS

When you use certain programs to edit files on a home computer that uses Windows Home Server, the files may become corrupted when you save them to the home server. This issue occurs if the following conditions are true:
• You edit files that are located in a shared folder on the home server.
• You use one of the following programs to edit the files or to save the files to the home server:

Microsoft has successfully reproduced corruptions for the following nine programs:
• Windows Vista Photo Gallery
• Windows Live Photo Gallery
• Microsoft Office OneNote 2007
• Microsoft Office OneNote 2003
• Microsoft Office Outlook 2007
• Microsoft Money 2007
• SyncToy 2.0 Beta
• Intuit QuickBooks
• uTorrent
The following programs have been reported by customers as having caused corruptions. However, we have not yet been able to reproduce corruptions.
• Photoshop Elements
• Zune Software
• Apple iTunes
• TagScanner
• Mozilla Thunderbird
• Adobe Lightroom
• Intuit Quicken
• MS Digital Image Library
• MP3BookHelper
• ACDSee
• WinAmp
• Windows Media Player 11
• Microsoft Office Excel
• Visual DataFlex
Note You may also experience this issue when you use other programs that are not listed here.

crikey!

 

[lay-z-boy]

The fact that it has been a recognised problem since Dec 21st last year also worries me.

 

[Cosimo]

http://support.microsoft.com/kb/946676



crikey!

How did they ever test this?

 

[BillytheImpaler]

How did they ever test this?

By running the programs listed and observing failure in the manner described? I don't get it.

 

[nikebee]

By running the programs listed and observing failure in the manner described? I don't get it.

I believe he means when Home was being developed, these are problems that really should have been found before it was even released.

I.E. - "How could they have tested this piece of junk?"

 

[Cosimo]

I meant the product not the simulation of bugs.

 

[Datamonkey]

This is old news guys, only time i had fallen foul of it was when using multiple disks to be honest, and also when i tried running a standard av app on the server instead of whs aware products.

Working fine with 2 hdds in raid 0 which i know is not a support solution and avast whs.

Still begs how they released the product with faults like these still apparent. This was one of the original faults and reasons why HP delayed its whs offering.