silverlox's Posts

Same problem here. But even more complicated. Workstation pro up to date. NO Encryption wanted or required. VMWare 16.2, Zeon processors and a TPM2.1 on the host so all is good there. I have a Windows 11 VM working happily. Nothing in the vmx file for any bypass of TPM or CPU. So no TPM installed or encrypted in the vmx file. No changes to the registry for Setup etc. This was updated to windows 11 some time ago Now updating a windows 10 VM, cannot get past the TPM issue. Editing the vmx file does not work. Editing the registry does not work. Same problem every time. TPM is required. Using the latest version of Windows 11 from Microsoft. So the question is: Have Microsoft stopped this process from working? Any helpful comments appreciated

Hi I have reverted back to the previous version of Windows 10,1703 as I could not run any VM's in the Fall creators version 1709 after the update. Unfortunately I needed to run a VM with no delay so was unable to try any changes etc. Luckily I had used Acronis True Image to make a backup so the restoration was flawless. Workstation is installed on C, my VM's are on D,E & F. None would work, Windows said VMware had a problem and must close. So I'm waiting for a week or so and will try again but first making a copy of the 1703 OS on a separate drive and booting from that one for the Fall Creators update. Be interested to see if anyone else has this problem Workstation Pro V14 Windows Fall Creators update 1709 HP Z820, dual Xeon, 64GB ram, running on SSD's mostly

Hey Wila My initial comment was:-- I'm running Workstation Pro 12.5.7 and have the same problem So unsure why I should have created yet another thread on the same problem, maybe that would be better but it seemed easier to have lots of info for the same problem. You say use one vCPU and the problem might go away, how do you know I'm using more than one, presuming you mean one virtualCPU per VM? Regards Mike

Addendum to the above. Just tried the notification area icon, used that to access the VMWare icon, used that to "open all background virtual machines" and the failed vm is usable again All without re-starting the host PC.

Hi, I'm running Workstation Pro 12.5.7 and have the same problem. I'm running VMware workstation in the normal Creators edition 1703 Build 15063.483 My VM's, three of them are running in separate VMware instances. One is the Windows 8.1-1 and does not seem to have any problems One is the normal Creators edition 1703 Build 15063.483 and does not seem to have any problems The other one that always crashes is, has just crashed and is still live in the Library view is the latest Preview issue. That one I cannot access, Taking Ownership does not work. I have deleted all .lck files and still cannot open that VM I have tried to run the VMX file but still get the Cannot take ownership. Using the Notification icon I've used that to shutdown all VM's and then tried to re-start the relevant VM but I instantly get the VMWare Workstation has stopped working message I cannot get the minidump as Windows states that Workstation has stopped responding. The .lck files are back again but deleting them I'm back to the virtual mac=hine is in use and VMware has stopped working Any suggestions?