topic Update VM Workstation pro 16.1 to 16.2 in VMware Workstation Pro Discussions

Update VM Workstation pro 16.1 to 16.2

zech02 — Tue, 19 Oct 2021 14:55:53 GMT

Windows 10 pro - latest patches - Update VM Workstation Pro 16.1 to 16.2
After the update, I could only start one VM. When I start a second VM I get the message "Failed to start the virtual machine".
The following message is in the Vmware.log file:

2021-10-19T14:24:27.684Z In(05) vmx FILE: E:\Virtual Machines\vmware.log: rename of E:\Virtual Machines\vmware-0.log -> FileRotateByRename failed: The process cannot access the file because it is being used by another process
2021-10-19T14:24:27.698Z No(00) vmx ConfigDB: Setting floppy0.clientDevice = "FALSE"
2021-10-19T14:24:27.710Z Wa(03) vmx PowerOn
2021-10-19T14:24:27.710Z In(05) vmx VMX_PowerOn: VMX build 18760230, UI build 18760230
2021-10-19T14:24:27.710Z In(05) vmx HostWin32: WIN32 NUMA node 0, CPU mask 0x00000000000000ff
2021-10-19T14:24:27.715Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1871, success=1 additionalError=0
2021-10-19T14:24:27.717Z In(05) vmx FILE: FileRotateByRenumber: rename of vm.scoreboard -> E:\Virtual Machines/vm-2.scoreboard failed: The process cannot access the file because it is being used by another process
2021-10-19T14:24:27.717Z Wa(03) vmx FileIOCreateRetryEx: Unrecognized error code: 1224
2021-10-19T14:24:27.717Z Er(02) vmx VMXSTATS: Failed to open or create vm.scoreboard: The requested operation cannot be performed on a file with a user-mapped section open.
2021-10-19T14:24:27.717Z Er(02) vmx VMXSTATS: Failed to map, open, or create the file, vm.scoreboard.
2021-10-19T14:24:27.717Z In(05) vmx Module 'VmxStats' power on failed.
2021-10-19T14:24:27.717Z In(05) vmx VMX_PowerOn: ModuleTable_PowerOn = 0
2021-10-19T14:24:27.717Z In(05) vmx
2021-10-19T14:24:27.717Z In(05)+ vmx Power on failure messages: Failed to start the virtual machine.
2021-10-19T14:24:27.717Z In(05)+ vmx
2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2021-10-19T14:24:27.717Z In(05) vmx Transitioned vmx/execState/val to poweredOff
2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4244]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
2021-10-19T14:24:27.717Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2021-10-19T14:24:27.717Z In(05) vmx Transitioned vmx/execState/val to poweredOff
2021-10-19T14:24:27.717Z In(05) vmx WQPoolFreePoll : pollIx = 3, signalHandle = 1080
2021-10-19T14:24:27.718Z In(05) vmx Vix: [mainDispatch.c:815]: VMAutomation_LateShutdown()
2021-10-19T14:24:27.718Z In(05) vmx Vix: [mainDispatch.c:770]: VMAutomationCloseListenerSocket. Closing listener socket.
2021-10-19T14:24:27.718Z In(05) vmx Flushing VMX VMDB connections
2021-10-19T14:24:27.718Z In(05) vmx VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2021-10-19T14:24:27.718Z In(05) vmx VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2021-10-19T14:24:27.718Z In(05) vmx VigorTransport_ServerDestroy: server destroyed.
2021-10-19T14:24:27.718Z In(05) vmx WQPoolFreePoll : pollIx = 2, signalHandle = 748
2021-10-19T14:24:27.718Z In(05) vmx WQPoolFreePoll : pollIx = 1, signalHandle = 756
2021-10-19T14:24:27.720Z In(05) vmx VMX exit (0).
2021-10-19T14:24:27.720Z In(05) vmx OBJLIB-LIB: ObjLib cleanup done.
Why does a VM block all other VMs when starting? Up to 6 VMs were running in parallel before the update to 16.2.
I deleted all VMs on the library and tested them with three VMs. How can I solve this problem?

Re: Update VM Workstation pro 6.1 to 6.2

scott28tt — Tue, 19 Oct 2021 14:51:40 GMT

6.x or 16.x??

Is it always the same second VM that won't start, or literally any second VM?

Re: Update VM Workstation pro 16.1 to 16.2

zech02 — Tue, 19 Oct 2021 14:58:14 GMT

Excuse me - INow have adjusted the version number in the text.

Re: Update VM Workstation pro 6.1 to 6.2

zech02 — Wed, 20 Oct 2021 13:04:45 GMT

I tested with 3 VMs: three times - "Poweroff" of all VMs - each time a different VM was started, then the second and third generated this message. The commonality of all VMs is Ubuntu 20.0x and were created with the same VM template. As I said with 16.1, all three VMs were running at the same time.

In the meantime, I've uninstalled 16.2 and reinstalled 16.1. After the installation, I was able to use the VMs again.
Now I could compare what has changed on the file system under 16.2. With version 16.2 an option "scoreboard" is activated and this option creates a file in the directory.
If a second VM is started, this file appears to be accessible to the first VM.

2021-10-19T13:25:07.843Z In(05) vmx Vix: [mainDispatch.c:4206]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1871, success=1 additionalError=0
2021-10-19T13:25:07.845Z In(05) vmx VMXSTATS: Successfully created statsfile: vm.scoreboard
2021-10-19T13:25:07.846Z In(05) vmx VMXSTATS: Update Product Information: VMware Workstation 16.2.0 build-18760230 Release TotalBlockSize: 64
2021-10-19T13:25:07.846Z In(05) vmx HOST Windows version 10.0, build 19043, platform 2, ""

Now I am curious whether my assumption is correct!

Re: Update VM Workstation pro 16.1 to 16.2

wila — Wed, 20 Oct 2021 15:04:47 GMT

Hi,

Looks like your VM's logging settings are misconfigured.

From your snippet:

E:\Virtual Machines\vmware.log: rename of E:\Virtual Machines\vmware-0.log

Normally a log is written local to the VM so if your VM is "Windows 10" then all of the VM's files are in the "Windows 10" folder - including the log files!

The above line would then have looked like:

E:\Virtual Machines\Windows 10\vmware.log: rename of E:\Virtual Machines\Windows 10\vmware-0.log

IOW, I don't think it is the scoreboard -whatever that is- new feature.

edit: refinement of my conclusion: It might actually be the scoreboard feature that stops the VM, but it is triggered by a misconfiguration, not the feature itself. The scoreboard files on my VM's are also local to the VM folder, not in a general location.

--
Wil

Re: Update VM Workstation pro 16.1 to 16.2

zech02 — Mon, 01 Nov 2021 07:41:43 GMT

Ok I have cloned my VM's in different folders. Now I can work with 6.2. Thanks for the support.

Re: Update VM Workstation pro 16.1 to 16.2

Celikoo — Mon, 24 Jan 2022 07:56:58 GMT

I've upgraded to the 16.2.2 today and I found a solution for my win10 machine:

open your vm config --> go to the tab "options" --> under "Enhanced Keyboard" set: "Use if available"

after that I was finally able to start my VM and the VMWare Tools could be downloaded after the first startup.

Maybe this can help for some of you?

Best regards