I believe MS had a problem with one of its patches causing this behavior during the last patch cycle.
Google around that might be it.
I doubt its VMware related.
P.S. Now you know to take a snapshot prior to applying windows updates to your VM's "just in case"
I found a solution here: