How to Configure Hyper-V UEFI Serial Console Redirection in Windows 11 Using PowerShell

Modern enterprise hypervisor environments and automated cloud staging clusters increasingly deploy headless virtual machines that lack graphical user interfaces or synthetic video adapters. While standard management relies on network-based protocols like SSH, Windows Remote Management (WinRM), or Remote Desktop (RDP), these connections fail when virtual machines encounter early boot errors, kernel panics, damaged network drivers, or firewall misconfigurations. In physical server hardware, administrators resolve these issues via out-of-band serial console redirection over serial ports (Baseboard Management Controller / IPMI serial-over-LAN).

In Windows 11 Hyper-V, Generation 2 virtual machines support UEFI firmware-level serial console redirection. Through PowerShell, administrators can use the Set-VMFirmware cmdlet alongside virtual COM port bindings (Set-VMComPort) to stream UEFI boot screens, bootloader prompts, and Linux kernel serial consoles directly over virtual named pipes or terminal consoles, establishing dependable out-of-band management.

Understanding Hyper-V UEFI Console Redirection Architecture

The Hyper-V Generation 2 firmware architecture includes native serial terminal emulation:

• ConsoleMode Property: Governs how the virtual machine’s UEFI firmware handles standard console I/O before transferring control to the guest operating system bootloader. Supported options include None (disables serial redirection), Default (standard UEFI video console), Com1 (redirects UEFI console output to virtual COM port 1), and Com2 (redirects to virtual COM port 2).
• Virtual Named Pipes: Hyper-V maps synthetic serial ports (COM1 and COM2) to Windows Named Pipes (e.g. \\.\pipe\vmconsole-01). Administrators or terminal emulators (such as PuTTY, Windows Terminal, or custom scripts) can connect to the pipe to interact with the VM console directly.
• Emergency Recovery Access: Serial redirection operates independently of the guest OS network stack, permitting administrators to access GRUB boot menus, Windows Special Administration Console (SAC), or Linux rescue shells during total network failure.

Prerequisites and Verifying VM Generation

Configuring UEFI serial console redirection requires administrative privileges and the Hyper-V PowerShell module installed on Windows 11.

Open an elevated PowerShell console and verify module presence:

# Check Hyper-V module availability
Get-Module -ListAvailable -Name Hyper-V

# Query target virtual machine to confirm Generation 2 architecture
Get-VM -Name "Headless-Server-01" | Select-Object Name, State, Generation

Ensure that Generation returns 2. Generation 1 machines use legacy BIOS controllers and do not support the ConsoleMode firmware parameter.

Inspecting Current Firmware Console Configuration

Query the active firmware configuration of the virtual machine:

# Retrieve current firmware parameters
Get-VMFirmware -VMName "Headless-Server-01" | Select-Object VMName, ConsoleMode, SecureBoot

By default, newly provisioned Generation 2 virtual machines configure ConsoleMode as Default, routing video output exclusively to the Hyper-V Virtual Machine Connection (VMConnect) window.

Configuring UEFI Console Redirection to COM1

To redirect UEFI firmware diagnostics, boot sequence messages, and text consoles to COM port 1, set ConsoleMode to Com1:

# Safely shut down the virtual machine prior to firmware modifications
Stop-VM -Name "Headless-Server-01" -Passthru

# Enable UEFI serial console redirection on COM1
Set-VMFirmware -VMName "Headless-Server-01" -ConsoleMode Com1

Once configured, the UEFI firmware writes early boot status, memory checks, and boot menu items directly to the virtual serial interface.

Binding the Virtual COM Port to a Windows Named Pipe

To access the serial stream from your Windows 11 workstation, bind the virtual machine’s COM1 port to a local Named Pipe:

# Inspect current COM port configuration
Get-VMComPort -VMName "Headless-Server-01"

# Map COM1 to a local named pipe
Set-VMComPort -VMName "Headless-Server-01" -Number 1 -Path "\\.\pipe\vmconsole-headless01"

The Named Pipe \\.\pipe\vmconsole-headless01 is instantiated automatically when the virtual machine starts, providing a bidirectional character stream interface.

Connecting to the Serial Console via Terminal Clients

You can connect to the virtual Named Pipe using standard terminal clients like PuTTY or Windows Terminal:

1. Launch PuTTY on Windows 11.
2. Select Serial as the connection type.
3. In the Serial line field, enter the full named pipe path: \\.\pipe\vmconsole-headless01.
4. Set the Speed (Baud) to 115200, with 8 data bits, 1 stop bit, and parity set to None.
5. Click Open to launch the terminal console.

Alternatively, Windows administrators can connect using open-source utilities like plink.exe or PowerShell named pipe reader streams.

Configuring Guest Operating Systems for Serial Console Redirection

For the guest operating system to continue outputting terminal text after the UEFI firmware hands off control, configure the guest kernel:

For Linux Guests (Ubuntu / Debian / RHEL):

Append serial console arguments to the kernel command line in /etc/default/grub:

GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200n8"

Update GRUB inside the guest (sudo update-grub). The Linux kernel will mirror all boot messages and present an interactive login prompt directly over the serial pipe.

For Windows Server Guests:

Enable Special Administration Console (SAC) via bcdedit:

bcdedit /ems on
bcdedit /emssettings EMSPORT:1 EMSBAUDRATE:115200

Verifying and Committing Firmware Changes

Verify that the firmware settings have committed successfully:

# Validate updated firmware console settings
Get-VMFirmware -VMName "Headless-Server-01" | Select-Object VMName, ConsoleMode

Power on the virtual machine and observe the terminal session:

Start-VM -Name "Headless-Server-01"

By enabling UEFI serial console redirection with Set-VMFirmware, Windows 11 administrators establish a resilient, out-of-band management channel that guarantees access to virtual infrastructure even during catastrophic network outages.