Introduction
If the device you're remote controlling in Level is a Hyper-V virtual machine, keyboard shortcuts like ALT + TAB may not work as expected. Hyper-V intercepts certain key combinations at the host level by default. One setting in the VM's configuration fixes this.
Configuring Hyper-V Keyboard Passthrough
By default, Hyper-V sends Windows key combinations to the host machine rather than the VM. Changing the VM's keyboard setting redirects them into the virtual machine.
Open Hyper-V Manager on the host machine.
Right-click the target VM and select Paramètres.
In the left panel, select Keyboard.
Change the setting to Use on the virtual machine.
Click OK to save. Keyboard shortcuts will now route to the VM during your Level remote session.
ℹ️ NOTE: This setting changes Hyper-V's behavior for all sessions to this VM, not just Level sessions. If other users connect to this VM via Hyper-V's native console, they'll see the same keyboard behavior.
FAQ
Why doesn't ALT + TAB work when I remote into a Hyper-V VM through Level? Hyper-V captures certain key combinations for the host OS by default. The VM never receives them. Setting the VM's keyboard mode to "Use on the virtual machine" stops Hyper-V from intercepting those keys.
Does this affect the Hyper-V enhanced session or only the basic session? This setting applies to the standard Hyper-V keyboard handling. Enhanced sessions have their own input redirection via RDP. If you're using an enhanced session, also check the RDP keyboard setting described in RDP Keyboard Functionality.
What if I don't have access to Hyper-V Manager? You'll need access to the Hyper-V host (the physical machine running the hypervisor) and appropriate permissions to modify VM settings. This isn't something Level can change remotely — it requires direct or administrative access to the host.
Who can change Hyper-V VM settings? Users with Hyper-V Administrator or full Administrator rights on the host machine. Standard users can't modify VM hardware settings.