Computer Hope

As the subject above.

what vmware problem 

Curious of the problem too?

Its usually pretty solid assuming system running it has good hardware. Interested to see how we can help with this one.

Hello
Such a problem.
Just one of these days, I can't start any of my OSs in my virtual machine. I did not change anything in my BIOS/UEFI as a notification suggested. Anyway, I did a power cycle of my PC and got no help.
Regarding AMD-V, I have no such option in my BIOS/UEFI. I could see AMD fTPM there (it's been enabled), but there is no AMD-V, as we see on the notification.
I have not updated the BIOS/firmware cause
- I don't know how to do this
- I can't believe this is the reason that my VMware is messed up now.

Only seen stuff like what your having if hardware changed. Was there any upgrades to the hardware between the last time it worked and now -or- were these virtual machine images transferred from another machine to this one to where there is a mismatch from where it was originally built on?

Wait a minute... I recall something now. I was fixing a Windows update error on my Win11 a couple of weeks ago. It was a KB5034441 update. To the video instructions, I had to expand a recovery partition on my SSD, and I did so. I guess that the first time I encountered a problem with opening OS on my VMware was after my action on the SSD partition.

BTW: this is a video  https://www.youtube.com/watch?v=GUnvAN7ffs4

How does this sound to you, guys? Could it be the reason for the VMware problem?
As we know, we assign some disk area for each OS on VMware, and once I touched the disk partition fixing the Windows update, I also touched an OS on VMware. 

Wow! I just deleted one OS from VMware and installed a new one instead, and I see I can't start the newly installed OS on VMware (same error). It seems like I have to uninstall all VMware and then reinstall 

If not modifying the partition, maybe a corrupted file system on my disk was a cause of the VMware problem. Could it be? Lately, I found out some of the file system was corrupted. I have fixed that.

Can't believe it!!!! Throughout all that time virtualization was off on my PC. I knew virtualization had to be on having an operating virtual machine, but I didn't even think virtualization might be off.

And for *censored* what would I do to turn virtualization off in my machine in the first place? Had no reason to do this! Besides VMware, I also have a BlueStacks emulator on my system, which requires virtualization. Thru all that time I was pretty sure virtualization was on on my machine.

So how could this happen that virtualization went off? Well, I don't worry about this now. I'm glad that the issue is solved. And it's time to end this shameful topic.

Glad its working again and the solution makes sense. Dependency Missing / Enabled was the cure.