Just installed and reinstalled 12.1.0 build 3272444 on Windows 10, but no matter which vm image I tried to launch, I quickly got the same error:
2016-03-12T22:27:04.243-08:00| vmx| I125: UUID: location-UUID is 56 4d 44 66 60 da 8e af-51 c5 3d de 5f 5c 57 ab
2016-03-12T22:27:04.246-08:00| vmx| I125: Hostinfo_OpenProcessBits: OpenProcess access bits are 1000.
2016-03-12T22:27:04.255-08:00| vmx| I125: FILE: FileLockScanDirectory discarding M63120.lck from D:\VM\Test\564d4466-60da-8eaf-51c5-3dde5f5c57ab.vmem.lck': invalid executionID 6936-131023239917785450(vmware-vmx.exe).
2016-03-12T22:27:04.288-08:00| vmx| I125: MainMem: Opened paging file, 'D:\VM\Test\564d4466-60da-8eaf-51c5-3dde5f5c57ab.vmem'.
2016-03-12T22:27:04.288-08:00| vmx| I125: MStat: Creating Stat vm.uptime
2016-03-12T22:27:04.289-08:00| vmx| I125: MStat: Creating Stat vm.suspendTime
2016-03-12T22:27:04.289-08:00| vmx| I125: MStat: Creating Stat vm.powerOnTimeStamp
2016-03-12T22:27:04.289-08:00| vmx| I125: VMXAIOMGR: Using: simple=Generic unbuf=Compl
2016-03-12T22:27:04.290-08:00| aioCompletion| I125: VTHREAD start thread 7 "aioCompletion" host id 2968
2016-03-12T22:27:04.312-08:00| vmx| I125: WORKER: Creating new group with numThreads=1 (20)
2016-03-12T22:27:04.339-08:00| vmx| I125: WORKER: Creating new group with numThreads=16 (36)
2016-03-12T22:27:04.340-08:00| vmx| I125: MigrateResetStaleVMDBHostLog: Hostlog .\Jeos-34589fcb.hlog doesn't exist.
2016-03-12T22:27:04.341-08:00| vmx| I125: MigrateBusMemPrealloc: BusMem preallocation begins.
2016-03-12T22:27:04.341-08:00| vmx| I125: MigrateBusMemPrealloc: BusMem preallocation completes.
2016-03-12T22:27:04.341-08:00| vmx| E105: PANIC: VERIFY bora\vmcore\vmx\main\timeTracker_user.c:238 bugNr=148722
2016-03-12T22:27:04.341-08:00| vmx| W115: Win32 object usage: GDI 4, USER 6
2016-03-12T22:27:04.341-08:00| vmx| I125: CoreDump_CoreDump: faking exception to get context
...
2016-03-12T22:27:04.579-08:00| vmx| I125: image file C:\Windows\System32\dbgcore.dll
2016-03-12T22:27:04.579-08:00| vmx| I125: file version 10.0.10586.0
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 7316
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 8144
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 7320
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 7264
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 7268
2016-03-12T22:27:04.579-08:00| vmx| I125: CoreDump: Including thread 2968
2016-03-12T22:27:04.674-08:00| vmx| I125: Panic: monitor not available, skipping monitor coredump.
2016-03-12T22:27:04.674-08:00| vmx| I125: Backtrace:
2016-03-12T22:27:04.674-08:00| vmx| I125: Exiting
Tried to remove *.vmem.* and then relaunch the vm image, got the same error! Tried another image, got the same error:
2016-03-12T22:53:53.832-08:00| vmx| A100: ConfigDB: Setting uuid.location = "56 4d 18 17 7c b3 f0 cd-0e 6f b0 3e 0c 83 89 21"
2016-03-12T22:53:53.833-08:00| vmx| I125: FILE: FileDeletionRetry: Non-retriable error encountered (D:\VM\Ubuntu-15\Ubuntu 15.10 Wily (64bit).vmx~): The system cannot find the file specified (2)
2016-03-12T22:53:53.865-08:00| vmx| I125: AIOGNRC: numThreads=17 ide=0, scsi=1, passthru=0
2016-03-12T22:53:53.865-08:00| vmx| I125: WORKER: Creating new group with numThreads=17 (17)
2016-03-12T22:53:53.877-08:00| vmx| I125: WORKER: Creating new group with numThreads=1 (18)
2016-03-12T22:53:53.877-08:00| vmx| I125: MainMem: CPT Host WZ=0 PF=2048 D=0
2016-03-12T22:53:53.877-08:00| vmx| I125: MainMem: CPT PLS=1 PLR=1 BS=1 BlkP=32 Mult=4 W=50
2016-03-12T22:53:53.877-08:00| vmx| I125: UUID: location-UUID is 56 4d 18 17 7c b3 f0 cd-0e 6f b0 3e 0c 83 89 21
2016-03-12T22:53:53.881-08:00| vmx| I125: MainMem: Opened paging file, 'D:\VM\Ubuntu-15\564d1817-7cb3-f0cd-0e6f-b03e0c838921.vmem'.
2016-03-12T22:53:53.881-08:00| vmx| I125: MStat: Creating Stat vm.uptime
2016-03-12T22:53:53.881-08:00| vmx| I125: MStat: Creating Stat vm.suspendTime
2016-03-12T22:53:53.881-08:00| vmx| I125: MStat: Creating Stat vm.powerOnTimeStamp
2016-03-12T22:53:53.881-08:00| vmx| I125: hread 676 3628VMXAIOMGR: Using: simple=Generic unbuf=Compl
2016-03-12T22:53:53.881-08:00| aioCompletion| I125: VTHREAD start thread 7 "aioCompletion" host id 676
2016-03-12T22:53:53.902-08:00| vmx| I125: WORKER: Creating new group with numThreads=1 (19)
2016-03-12T22:53:53.909-08:00| vmx| I125: WORKER: Creating new group with numThreads=16 (35)
2016-03-12T22:53:53.910-08:00| vmx| I125: MigrateResetStaleVMDBHostLog: Hostlog .\Ubuntu 15.10 Wily (64bit)-47a35b86.hlog doesn't exist.
2016-03-12T22:53:53.911-08:00| vmx| I125: MigrateBusMemPrealloc: BusMem preallocation begins.
2016-03-12T22:53:53.911-08:00| vmx| I125: MigrateBusMemPrealloc: BusMem preallocation completes.
2016-03-12T22:53:53.911-08:00| vmx| E105: PANIC: VERIFY bora\vmcore\vmx\main\timeTracker_user.c:238 bugNr=148722
2016-03-12T22:53:53.911-08:00| vmx| W115: Win32 object usage: GDI 4, USER 5
2016-03-12T22:53:53.911-08:00| vmx| I125: CoreDump_CoreDump: faking exception to get context
The Google search showed some old fix for Player v7, but it did not apply to the problem I encountered. I am posting this to the forum and hopefully some resolution can be found here.