Install fails to detect virtualization when Hyper-V is enabled and doesn't properly disable hyper-V

[waryhermit]

The installer script thought my CPU was not supported. SecondLevelAddressTranslationExtensions and VirtualizationFirmwareEnabled were listed as False. I other virtualization programs block you from even checking. I think you could fix this by rearranging the Hyper-V check before the VT-X check in the script, because when I ran the command "bcdedit /set hypervisorlaunchtype off" and restarted my computer it said I had VT-x.

But then when I ran the install script it said

Hyper-V is enabled on your computer. BeLL App cannot run with Hyper-V enabled. Disabling Hyper-V…

Hyper-V has been disabled. Please, reboot your computer, then install BeLL App again.

However it gave me the Hyper-V message again even after restarting. When I ran the command "Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All" in power shell and restarted it the script worked. I don't know why it didn't work when the script tried to turn it off.

[dogi]

@waryhermit thanks that is a good one

By any case do you remember of the two scripts you was running?

[waryhermit]

@dogi The windows 8.1 and above script. The powershell one.

[aberdean]

@dogi @waryhermit that part of the script is the same in both scripts. Thus, it should be modified on both.

Changing the bcdedit command with the Disable-WindowsOptionalFeature one would be awesome.
Moving the Hyper-V check before the CPU checks is also a great idea, but we should make sure that it would still work when the CPU is not compatible. That can be easily tested on a VM.