When running Oracle RDBMS on VMware, and before running "OPatch apply" to apply any Oracle patch, you might consider reviewing these two internet postings:
http://valchuk.net/locked-dlls-during-opatch-apply/
https://bitbach.wordpress.com/2013/06/05/unlocking-oci-dll-and-friends-when-upgrading-or-patching-oracle/
... they describe how to unlock those Oracle DLLs locked VMware Tools, etc., so you can proceed with running OPatch without having to reboot Windows.
The only other option is to set all Oracle services to Manual in the control-panel, and remove the Oracle_Home from the PATH environment variable, and then reboot Windows, so then VMware won't know anything about the Oracle DLLs, and none should start following the reboot, allowing you to proceed with OPatch Apply.
I use the ListDLLs.exe and ProcExp.exe free utilities from Microsoft to determine which processes have the Oracle DLLs locked.
I couldn't find any OTN Community forum postings on this, so I created this post.