Other topics are discussing the corruption of the image file in the host. I am now finding that 3.0 is deteriorating the integrity of the internals of the drive image. Prior to 3.0 a periodic chkdsk rarely turned up a single error. With 3.0, after a short while, chkdsk will start turning up numerous errors. By telling chkdsk to correct the errors, the drive slowly turned into Swiss cheese. It would work for a session or two, then another chkdsk would find more errors. Eventually, databases became corrupt, programs stopped working and so on as the disk deteriorated. I tried many different things to verify that PWS was the problem - some obvious, some not: 1) Check the host disk (fix permissions, verify disk) - OK 2) Restore the image from a 2.5 backup - Starts to corrupt after a short while 3) Have chkdsk check the disk for physical problems - OK 4) Create a fresh disk image - Starts to corrupt after a short while 5) REPLACE THE HD with another new HD (Seagate Momentus in a MacBook Pro) - same issues 6) VMWare was not on the machine (some report a conflict with PWS) That said, I'm pretty confident that PWS 3.0 is the culprit. The problem is consistent, it may not affect FAT32 or Vista in the same way. I'm running XP SP2 with an NTFS formatted drive.