Diagnosing/troubleshooting technical issues usually require that one gives appropriate technical information to analyze and you've not really done that so not sure what help you expect. The bottom line is force rebooting a Virtual Machine can corrupt it beyond repair and should be avoided whenever possible. Doesn't necessarily mean it will always happen and in many cases nothing will happen however the potential for un repairable corruption is always there when forcing a system (physical or virtual) to reboot. Also maintaining proper backups is imperative in general and especially so with virtualization
If the Virtual Disk itself became corrupted you can try repairing it with vmware-vdiskmanager and if it's Windows that became corrupted then repairing it is not different then if it was a physical machine and one should act accordingly and this is not really a VMware issue per-se and one should turn to Microsoft to Microsoft centric forums for help with Windows.
That said, have you tried booting from the installation DVD/ISO Image and tried manually doing a System Restore to Restore Point prior to the forced reboot/shutdown?