Hyper-V Feature question

aVRage

Member
Hello everyone! happy new year!
Now to the point.. Want to update my image, this time i tried to activate Hyper-V and other stuff like Virtual Machine Platform, Windows Hypervisor Platform.
Why? Beacause i want to use Docker Desktop and without Virtual stuff it don't work.

So i activated in NTlite Compatibility for Hyper-V Host, checked Components, checked Features, looking in settings and services.
Logging into windows and Hyper-V stuff is active
The question is, why it show "Disabled" (in Features windows of NTlite) and not Enable like other stuff listed here? I need a specific FOD package to enable it or is already in the ISO? it is normal?
Also, with Hyper-V in windows checked, VirtualBox (i use also this) cannot load some machine, so i tried to disable Hyper-V, restart windows, but Hyper-V still active in "Turn windows features on or off". Why?
Thanks for help
 
Features on Demand (FOD) can fall into three categories:
- integrated inside the image, enabled by default​
- integrated inside the image, but disabled​
- not integrated, but can be installed online or integrated as optional FOD package​

Hyper-V features fall under the integrated, but disabled by default category. The component files are present in the image, but you use a DISM capability command to hard-link the hidden files to their destination folders (Feature is now available). When you use DISM to disable it, all the linked copies are removed, leaving the original components safely hidden.

As long as the Feature is integrated, it can be enabled or disabled (back and forth) an infinite number of times. NTLite is reporting the current FOD enablement status from the offline image.

VirtualBox doesn't work well with Hyper-V enabled. FAQ.
 
thanks for the reply, the error is when i tried to turn it on or off manually, or with cmd and DISM
Code:
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
or from powershell
Code:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
in both cmd and powershell it say is completed but don't ask me to restart Y/N

the specific point why i want to turn it ON is because "vmcompute" service is needed to start Docker Desktop properly.
But it is Hyper-V Host Compute Service.

So now going for my 5° iso test :oops:
its attached if you want to look, the rest just work fine for me from one year+
Just want to integrate all requirements for Docker, and make the rest as it was.

EDIT: tested and failed again, DISM online is by any chance using windows update? Because is disabled..
Now i see everything checked under Features, tried cmd DISM and powershell, same as before, non prompting to restart, it don't create the path.
There is a way to do it "manually" or offline?!

Screenshot 2024-01-05 022743.pngScreenshot 2024-01-05 022626.pngScreenshot 2024-01-05 023151.png
 

Attachments

  • Auto-saved 4310bf57.xml
    63.8 KB
Last edited:
Hyper-V features are currently enabled in your install image:
Code:
                <Feature name="Microsoft-Hyper-V-Management-Clients">true</Feature>
                <Feature name="Microsoft-Hyper-V-Hypervisor">true</Feature>
                <Feature name="Microsoft-Hyper-V-Tools-All">true</Feature>
                <Feature name="Microsoft-Hyper-V-Management-PowerShell">true</Feature>
                <Feature name="Microsoft-Hyper-V">true</Feature>
                <Feature name="Microsoft-Hyper-V-Services">true</Feature>
                <Feature name="Microsoft-Hyper-V-All">true</Feature>
                <Feature name="VirtualMachinePlatform">true</Feature>
                <Feature name="HypervisorPlatform">true</Feature>
                <Feature name="Microsoft-Windows-Subsystem-Linux">true</Feature>

DISM or PS enabling them (again) would be a null operation, and won't result in a restart request.

WU is not needed (just the SSU servicing stack, for DISM) for toggling any integrated features. If the Feature wasn't included in the image, WU would be required to download the missing feature packages from the MS servers.

Code:
Get-WindowsOptionalFeature -Online -FeatureName *Hyper* | select DisplayName,State

DisplayName                              State
-----------                              -----
Windows Hypervisor Platform           Disabled
Hyper-V                               Disabled
Hyper-V Platform                      Disabled
Hyper-V Management Tools              Disabled
Hyper-V Module for Windows PowerShell Disabled
Hyper-V Hypervisor                    Disabled
Hyper-V Services                      Disabled
Hyper-V GUI Management Tools          Disabled

Did you install Docker for WSL2 or Hyper-V? Those are two different back-ends.
 
First of all in the previous test (with other iso settings) i installed the Subsistem for Linux, then update the kernel for WSL2, then installed Ubuntu
but Ubuntu wont let me finish the installation (stucked to "this take few minutes" state) under WSL2, so at some point i switched to WSL1, and finally i was able to finish the installation of Ubuntu with my credential.
Was fine, with "wsl.exe -l -v" i was see the Ubuntu under version 1
Then i switch to WSL2
Installed Docker Desktop, choose WSL2 instead of Hyper-V and start the application.
Docker try to start and get stucked in this state, without see anything.
Googled for this problem and found the cause in "vmcompute" service that require to be set (but from windows security.. and i delete every edge of defender and company :D)
the "solution"

and if i try "net start vmcompute" from powershell as they say
this is the result
Screenshot 2024-01-05 031442.png
 
You didn't read this part?
Code:
cd "C:\Program Files\Docker\Docker"  
./DockerCli.exe -SwitchDaemon
 
tried and not works
Screenshot 2024-01-05 120657.png
also, this just switch to windows container, but i need a linux containers.
Also, hyper-v is checked and all but not works, service is stopped and cannot be started.
I think this little vmcompute want the "control", but to do it i need to activate what? Defender? in any way? Can i filter only something?
I use Norton as antivirus (actually never installed for this test)
To be clear, actually is checked in Features, but if i try to disable it, it just fail with errors, looks like is "visually enabled" but not for real.
 
is hyper v enabled in bios ? I know i had an issue before with hyper-v not working even tho it was 'enabled' , but it was switched off in bios

Some bioses have it there other don't , mine does ( asus b550-f gaming ). just a thought
 
is hyper v enabled in bios ? I know i had an issue before with hyper-v not working even tho it was 'enabled' , but it was switched off in bios

Some bioses have it there other don't , mine does ( asus b550-f gaming ). just a thought
yes SVN is active (virtualization)

going for another try with Security Center active and Defender too.
Curious about this
Screenshot 2024-01-05 150138.png
Can i let this disable in settings, while is checked Defender and Security center in components?
I want to access to this place
Hyper-V-Failure-6.jpgAnd edit this setting as said in this guide to fix
 
Last edited:
I make another ISO, with defender disabled but security center accessible.
The problem is Hyper-v itself
If i try to connect to a server (inside Hyper-V Manager) this is the result
Screenshot 2024-01-05 205430.png
Meanwhile WSL2 installed, set to default, but ubuntu wont launch in WSL2
In WSL1 ubuntu its ok
I dont know what to do, thinking vmcompute was the real cause, but maybe there is something missing in the VM ecosystem itself.
This is the last image used
 

Attachments

  • Auto-saved 4310bf57.xml
    63 KB
Back
Top