I lost my virtualization capabilty when I upgraded the BIOS

[fernandonv2]

I had virtual machines using Vmware or Oracle Virtualbox. My Bios was F70. When I upgraded to F72, the virtualization option was disabled in BIOS so I enabled it again. This was a known procedure for me. However Windows didn't boot, I got a blank screen, I could see the mouse prompt and move it on my blank screen and that was all. I disabled the virtualization option in BIOS and got my Windows back but I can't virtualize anymore. Then came new updates, F73, F74 and F75 and I hoped the new ones would correct the problem but it is the same. I tried enabling virtualization in Windows but it's no good. So I want to downgrade my BIOS to F70 again, or get a solution for the new BIOS. I haven't find a solution anywhere, please check it out, thanks. My OS is Windows 10 64 bit, my PC is HP Notebook -15-bs001la.

[BeemerBiker]

Try setting bios defaults using the F9 key.  I think that is the one.  Press it on each bios setup page.

Possibly there is a bios entry for VT-I  on/off instead of enable / disable Virtualization

AMD has a different name "SVM"

for old bios scroll down to bottom of the page

I assume you have secure boot.  Please read the ChatGpt advice.  You need the latest vm and need to remove the old one

Secure Boot is a security standard that can be enabled for virtual machines (VMs) to ensure that only trusted software from the PC manufacturer is used to boot the PC. It can help protect systems from malware and unauthorized software by verifying the integrity of the boot process. However, Secure Boot can have some implications for virtualization, including:

• Trusted publishers

  When Secure Boot is enabled, all OS boot components, such as the boot loader, kernel, and kernel drivers, must be signed by trusted publishers. If Secure Boot can't verify that the image is signed by a trusted publisher, the VM won't boot.
• Signed drivers

  When Secure Boot is enabled, only signed drivers can be loaded into the VM. If the boot process encounters a component with a missing or invalid signature, it will stop with an error.
• UEFI firmware

  UEFI firmware in generation 2 VMs doesn't support Secure Boot setup mode. If non-Microsoft UEFI shells or UEFI applications aren't digitally signed correctly, Secure Boot must be disabled for the VM.
• VMware Tools

  VMs that use UEFI secure boot require VMware Tools version 10.1 or later. Before activating Secure Boot, VMware Host-Guest Filesystem should be removed from VMware Tools if the VM is Linux.