Hello,
So far as i know, there is no solution for this "problem".
But there are multiple issues that associated to this problem. Vmware and Microsoft point to each other to blame.
If the event log shows something about a floppy disk, just remove the floppy drive and controller.
Keep windows and vmware up to date.
And when the VM runs an application like Exchange of SQL, you can ignore this error. But make an back-up with a proper backup solution.
For a complate store, see the post of mulio at page 2
Source: http://technet.microsoft.com/de-de/library/ee923636(WS.10).aspx
If the shadow copy is successfully created, the Volume Shadow Copy Service returns the location information for the shadow copy to the requester. In some cases, the shadow copy can be temporarily made available as a read-write volume so that VSS and one or more applications can alter the contents of the shadow copy before the shadow copy is finished. After VSS and the applications make their alterations, the shadow copy is made read-only. This phase is called Auto-recovery, and it is used to undo any file-system or application transactions on the shadow copy volume that were not completed before the shadow copy was created.
greetings,
peter