Hyper-V Os Selection

[CanitoCool]

Greetings and happy belated Christmas. I need experts on Hyper-V technology. Here is the problem I am having. I have a customer that works connecting his laptops to cars so they can be enhanced in the way the owner wants. Someone tried to install a software in his laptop and for some reason the laptop is now loading a OS SELECTION. One says HYPER-V ENABLED and the other HYPER-V DISABLED. That laptop never had that screen before. When I checked at PROGRAMS AND FEATURES nothing HYPER-V related is ticked in WINDOWS FEATURES. Is there a way to remove that OS SELECTION and revert it back to a normal Windows 11 boot loading? The other problem is that even if he select HYPER-V DISABLE when he run certain programs, now it says it can't be run under HYPER-V virtualization, when that never happened before. I will appreciate any help provided. Thanks in advance.

 

[ChatGPT]

Hello and happy belated Christmas! I'd be happy to help you with your Hyper-V issue. It seems like someone has enabled Hyper-V on your customer's laptop, which is causing the OS Selection screen to appear during boot-up. To remove this OS Selection screen and revert back to a normal Windows 11 boot loading, you would need to disable Hyper-V. Since you mentioned that you couldn't find any Hyper-V related features enabled in Windows Features, it's possible that Hyper-V was enabled using an alternative method. In that case, you can try disabling Hyper-V using the command prompt. Here are the steps to disable Hyper-V using the command prompt:

1. Open the Command Prompt with administrator privileges. You can do this by right-clicking on the Start button, selecting "Command Prompt (Admin)".
2. In the Command Prompt window, type the following command and press Enter: bcdedit /set hypervisorlaunchtype off
3. Once the command executes successfully, you can close the Command Prompt window. After disabling Hyper-V using the above steps, the OS Selection screen should no longer appear during boot-up, and your customer should be able to boot into Windows 11 directly. Regarding the issue with certain programs not running under Hyper-V virtualization, this could be because those programs have specific requirements or limitations when running in a virtualized environment. Unfortunately, without more specific information about the programs, it's difficult to provide a precise solution. You may need to explore other alternatives, such as running the programs on a physical machine instead of a virtual one. I hope this helps! If you have any further questions, please feel free to ask.

 

[CanitoCool]

I had performed the BCDedit command suggested and still the software says that it can't be run under Hyper-V, when everything Hyper-V related is off.

The program I am using to test if the Hyper-V still display this message when without Hyper-V active it use to run correctly.

 

[Neemobeer]

Is this the host OS or a guest vm?

 

[CanitoCool]

Is this the host OS or a guest vm?

This is the first time I handle a problem like this in terms of a laptop with the Hyper-V feature, to be honest. I have no expertise on it. The closest thing as vm that I had handled as vm is VirtualBox. With that in mind, I can say is the host pc. Let's put it this way. Imagine you turn on your laptop and Windows 10 loads as usual. Then after someone claimed he installed the new software he needed it, he shuts down the laptop and the next day when he turns his laptop on, find that screen of hyper-v enabled and hyper-v disabled. He wants his laptop OS back to his normal operating way. That is something I am trying to helping him with, but I have no expertise with that kind of problem. Putting my heart on the answer to your question. And thanks for trying to help me out.

 

[ussnorway]

someone installed how?

is there a usb or disc still in the laptop perhaps

 

[Neemobeer]

If you're physically powering on a computer then it's 'host' meaning it is the OS booting directly from the hardware as compared to a guest os which runs on the hyper visor layer (vmware, hyper-v, virtualbox etc).

If you select either entry does the system boot? If yes for both I would opt to use the Windows 10 Hyper-V. Select that option and you can simply remove the boot entry for the other.

Removing a boot entry from the BCD (Must have admin rights)

• Open a terminal, cmd or powershell prompt as administrator (right click one of the aforementioned programs and select 'Run as Administrator'
• Type bcdedit /enum
  • You will see one entry for 'Windows Boot Manger' this one should NOT BE DELETED
  • You will likely see two 'Windows Boot Loaders', the description should reflect your menu from the above screenshot
  • For the entry you wish to delete copy the identifier including the '{ }'
• Type bcdedit /delete {long-identifier-number}

The menu should go away unless there is a value > 0 for timeout under the 'Windows Boot Manager' . You can either ignore or change the timeout.

 

[ChatGPT]

The error message clearly points out that the software is detecting a Hyper-V environment, even though you’ve disabled all Hyper-V features. This issue can arise due to residual effects of Hyper-V, lingering configurations, or the Windows virtualization stack still being recognized by the application. Let’s go through some further steps to resolve this:

---

1. Verify That Hyper-V is Fully Disabled​

Even with Hyper-V turned off, Windows might still keep components active within its virtualization stack (like Virtualization-Based Security or other hypervisor features). Here’s how to ensure it’s fully disabled:

Steps to Completely Disable Hyper-V:​

1. GUI Method:
   • Open Control Panel > Programs > Programs and Features.
   • Click Turn Windows features on or off on the left.
   • Ensure the following are unchecked:
     • Hyper-V
     • Windows Hypervisor Platform
     • Virtual Machine Platform
   • Click OK and restart your system.
2. Command-Line Method (Force Disable):
   If the GUI doesn’t handle it completely, use Command Prompt (Admin):
   

   cmd
   dism /Online /Disable-Feature:Microsoft-Hyper-V

   Restart the system afterward to ensure Hyper-V is unloaded.

---

2. Check for Virtualization-Based Security (VBS)​

If Virtualization-Based Security is enabled, it can cause software to detect a virtualized environment, even without Hyper-V directly active.

Check and Disable VBS:​

1. Open Settings > Privacy & Security > Windows Security > Device Security.
2. Look for Core Isolation or anything mentioning VBS.
3. If Core Isolation / Memory Integrity is turned on, disable it.
4. Restart your PC.

---

3. Confirm Hypervisor is Disabled​

Even after disabling Hyper-V, the Windows bootloader might still load the hypervisor. Let’s ensure the hypervisor isn’t active:

Use BCDEdit to Disable Hypervisor:​

1. Open Command Prompt (Admin).
2. Run the following command:
   

   cmd
   bcdedit /set hypervisorlaunchtype off

3. Restart your PC.

To confirm the hypervisor isn’t running:

• Open Task Manager (Ctrl + Shift + Esc).
• Go to the Performance > CPU tab.
• If virtualization is still enabled, it may indicate VBS or another virtualization-related process is still active.

---

4. Test With a Clean Boot​

Some third-party tools or services (e.g., Docker, VirtualBox, WSL) can also trigger detection as part of a “virtualized” setup. Perform a clean boot to rule this out:

Steps for Clean Boot:​

1. Open Run (Win + R), type msconfig, and press Enter.
2. In the Services tab, check Hide all Microsoft services, then click Disable all.
3. Go to the Startup tab and click Open Task Manager.
4. Disable all startup items.
5. Restart the system and test the problematic software.

---

5. Address Possible Software-Specific Requirements​

Certain legacy or poorly optimized software might detect virtualized environments due to:

• Low-level CPU flags being exposed (caused by firmware or BIOS settings).
• Residual registry settings/Hyper-V components.

Additional Steps:​

1. Ensure BIOS Virtualization Settings Are Disabled:
   • During boot, enter BIOS/UEFI (commonly F2, Del, or F12).
   • Look for and/or disable:
     • Intel VT-d / AMD-V
     • IOMMU
     • Virtualization Technology for Directed I/O
   This entirely disables virtualization support at the hardware level.
2. Registry Cleanup:
   • Open Registry Editor (Win + R, type regedit).
   • Navigate to:
     

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization

   • Check for and delete suspicious or outdated virtualization-related keys.

---

6. Alternative: Troubleshoot with the Specific Software Vendor​

If the issue persists, this might be related to how the specific software detects Hyper-V. Software developers sometimes rely on poor detection mechanisms that flag virtualized environments unnecessarily.

• Check the software's documentation or forums.
• If there's no resolution, reaching out to their support team might provide insight into whether the detection can be bypassed.

---

7. Final Resort: Reinstallation​

If nothing works:

1. Perform a system reinstall.
2. Before installing any virtualization tools or enabling Hyper-V-dependent features, install and test this software first.

---

Let me know whether these steps help remove the "This program can not run under Hyper-V" error, or if further investigation is necessary (e.g., identifying lingering services or alternate hypervisor interaction)!