A Microsoft Hyper-V test setup shows a Generation 2 VM with Secure Boot and virtual TPM verified by Azure Attestation.
Microsoft has added Trusted Launch virtual machines (TVMs) to Windows Admin Center Virtualization Mode (vMode) as a private preview. The feature shipped first as a PowerShell-only option in Windows Server Insider builds. Administrators can now create and manage Trusted Launch VMs in vMode and view each VM's boot-integrity status.

Don't confuse this with a general release. Microsoft says vMode itself became generally available in Windows Admin Center version 2611 on November 16, 2026. The TVM feature is still a private preview, it needs an Insider build of Windows Server on the host, and one required component is only available through Microsoft's Windows Admin Center NDA program. This is a lab project for now.

A Microsoft Hyper-V test setup shows a Generation 2 VM with Secure Boot and virtual TPM verified by Azure Attestation. What Trusted Launch adds to a Hyper-V VM​

Trusted Launch is a security feature you can enable when creating Hyper-V Generation 2 VMs. Microsoft says it provides:

  • Secure Boot on the VM
  • A virtual TPM (vTPM)
  • Protection of the vTPM state at rest
  • Boot integrity verification, also called guest attestation

Microsoft Azure Attestation checks the VM's boot measurements, so changes to the boot path or boot components can be detected. Microsoft's reasoning is that attackers increasingly plant malware in the boot path. The guest OS is usually well defended, and firmware runs with high privilege, so it can change what gets loaded, including boot loaders and drivers. Antivirus running inside the OS often can't see that kind of change.

Attestation reports a problem. It doesn't stop one. It tells you whether the VM started in a known-good state and adds another check alongside the controls you already run.

Summary​

Trusted Launch gives Gen 2 Hyper-V VMs Secure Boot, a vTPM with protected state, and cloud-based attestation of each boot. The vMode preview adds a GUI for creating these VMs and viewing their attestation results.

How far the feature has come since July​

The earlier announcement makes the progress clear. Microsoft first announced Trusted Launch for virtual machines (TVMs) in Windows Server Insider Preview. TVMs are available for preview starting with Windows Server Insider preview build 29621.

In the release notes for Windows Server vNext preview build 29667, Microsoft described the feature as an initial preview that supports TVMs with Secure Boot, vTPM, and vTPM state protection (at rest), managed via PowerShell. The same notes listed four items as not supported in this release: moving TVMs to another server, TVMs in failover clusters or Hyper-V Replica, boot integrity verification, and TVMs in Windows Admin Center (WAC).

The vMode preview covers two of those four: boot integrity verification and Windows Admin Center management. The other two are still missing.

CapabilityEarlier PowerShell-only previewvMode private preview
Secure Boot, vTPM, vTPM state protection at restYesYes
Boot integrity verification (guest attestation)NoYes
Windows Admin Center managementNoYes, in vMode
Moving TVMs to another serverNoNo
Failover clusters / Hyper-V ReplicaNoNo

Windows Report noted at the time that Microsoft plans to add or improve several of these capabilities in future Windows Server Insider releases. That plan is partly delivered. Live migration and clustering are still the features that would make TVMs usable in production. Most Hyper-V shops depend on clusters, so a VM that can't fail over between hosts won't go far beyond a lab.

Summary​

Since the first preview, Microsoft has added attestation and GUI management. Mobility, clustering and replication are still unsupported.

Before you start: prerequisites​

Have all of these ready:

  1. A host running Windows Server Insider preview build 29621 or later.
  2. A separate gateway machine for Windows Admin Center vMode. Microsoft says to install vMode on a dedicated gateway, not on the Hyper-V host.
  3. The guest attestation client folder, IsolatedVmGuestAttestation. Microsoft distributes it through its Windows Admin Center NDA program, so sign up early.
  4. An Azure subscription where you can create an Azure Attestation provider.
  5. Administrator credentials for each guest VM. vMode uses them to install the attestation client inside the VM.

Step-by-step: setting up the preview​

These steps follow Microsoft's published procedure. Menu names are given exactly as Microsoft wrote them.

1. Install the Insider build on the host​

Install Windows Server Insider preview build 29621 or newer on the server that will run the VMs. You need to be a member of the Windows Server Insiders program.

2. Set up vMode and turn on the experiment​

  • Install the latest Windows Admin Center vMode on the dedicated gateway machine.
  • When setup finishes, tick the box to start Windows Admin Center, select Finish, and sign in as an administrator.
  • Click Settings in the top-right corner, then choose Advanced under Development in the left pane.
  • Add the experiment key msft.sme.hyperv.tvmGuestAttestation.
  • Create a resource group in vMode and add your host server to it.
  • Copy the IsolatedVmGuestAttestation folder to C:\Program Files on the host, not the gateway. Microsoft says this must be done before you enable the feature in the next step.

3. Enable Trusted Launch on the host​

In the server's Settings in vMode, choose Isolated guest and click Enable. This installs the Trusted Launch feature.

4. Build the attestation policy and connect Azure Attestation​

This step takes the longest. Start by reading the AK root certificate value from the host's registry:

Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\AszIGVmAgent' -Name 'ActiveAkRoot'

Copy the output and put it in place of <AKRoot> in Microsoft's policy template:

Code:
version=1.2;
configurationrules
{
=> issueproperty(type = "aik_trusted_root_certs", value ="-----BEGIN CERTIFICATE-----<AKRoot>-----END CERTIFICATE-----");
};
authorizationrules
{
[type=="x-ms-azurevm-default-securebootkeysvalidated", value==false] => deny();
[type=="x-ms-azurevm-debuggersdisabled", value==false] => deny();
=> permit();
};
issuancerules
{
};

Here's what the policy does. It sets your host's AK root as the trusted certificate root. It then denies attestation if Secure Boot keys aren't validated or if debuggers aren't disabled, and permits it otherwise. Microsoft's blog shows a filled-in example with a placeholder string where the certificate goes. That string is not a real certificate, so use the value from your own registry.

Next:

  • Create an Azure Attestation provider by following Microsoft Learn's Azure portal quickstart, and write down its Attest URI.
  • Under Attestation policy, set Attestation type to AzureVM and paste in your completed policy.
  • Go back to vMode, enable guest attestation on the server, and enter the Attest URI.

5. Create the Trusted Launch VM​

  • Under Tools in the left pane, choose Virtual machines and click Add.
  • Set Security Type to Trusted Launch and pick an available virtual switch.
  • Confirm on the host:

(Get-VM -name <VMName>).GuestStateIsolationType

It should return TrustedLaunch. The same check was already in the PowerShell-only preview, where Microsoft said the command should return TrustedLaunch.

6. Enable guest attestation on the VM​

Enable guest attestation for the VM and enter its administrator username and password so vMode can install the attestation client inside the guest. A notification confirms when it's done. Expect a few minutes' wait before any status shows up.

7. View attestation status​

The status appears in vMode. Microsoft says it refreshes about every eight hours and checks the boot integrity of the VM's most recent start.

Common failure points​

Microsoft hasn't published a troubleshooting guide, but these are the likeliest problems based on its procedure:

  • The client folder is on the wrong machine. IsolatedVmGuestAttestation goes on the host, in C:\Program Files, and has to be there before you click Enable.
  • The experiment key is missing. Without msft.sme.hyperv.tvmGuestAttestation on the gateway, the attestation workflow won't appear.
  • The example certificate was pasted. Only the value from your host's ActiveAkRoot registry entry is valid.
  • The wrong attestation type. Microsoft's instructions specify AzureVM.
  • No status yet. The first result can take a few minutes, and checks then run about every eight hours. This isn't a live dashboard.
  • VMs that need to move. Live migration, clustering and Hyper-V Replica aren't supported for TVMs in this release. Build your pilot on a standalone host.

Analysis: worth testing, not ready for production​

The direction is good. Trusted Launch has been standard on Azure VMs for years, and bringing that boot-integrity model to on-premises Hyper-V, with a GUI, fills a gap for on-prem shops. The eight-hour check has a purpose too: Microsoft says periodic verification also protects against attacks that turn off reporting from inside the VM. Microsoft doesn't explain how that works, so treat it as the company's claim, not a tested guarantee.

There are three catches:

  • Cloud dependency. Boot integrity for an on-premises VM is checked by an Azure service. Hybrid shops won't mind. Air-gapped or strictly sovereign environments will want to know whether Microsoft plans another option, and it hasn't said.
  • NDA gating. A preview that requires an NDA download will draw feedback mainly from larger customers and partners, not the wider Hyper-V community.
  • Mobility. Until TVMs can be live-migrated and clustered, this is a security feature for standalone hosts.

The preview is a good opportunity for security-minded virtualization teams to learn the attestation workflow before it ships in Windows Server. Use a spare host, and send feedback through the Windows Server Insiders Forum, which is where Microsoft is collecting it.

 

References

  1. TVM in Windows Admin Center: vMode is in Private Preview Windows Admin Center Blog 2026-11-17T18:34:39+00:00
  2. TVM in Windows Admin Center: vMode is in Private Preview | Microsoft Community Hub techcommunity.microsoft.com
  3. Windows Server Insiders Get Trusted Launch for Hyper-V VMs windowsreport.com