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?