Blog Post

Windows Admin Center Blog
7 MIN READ

Two modes combined: Windows Admin Center version 2610 is now in public preview!

Davanna-White's avatar
Davanna-White
Icon for Microsoft rankMicrosoft
Sep 18, 2026

October 29th, 2026 update: The public preview build has been refreshed to version 2.8.2.8. This refresh includes an update to .NET to address an out-of-bounds memory write vulnerability.

October 20th, 2026 update: The public preview build has been refreshed to version 2.8.1.6. This refresh includes bugfixes for issues related to Azure registration and sign-in. 

We’ve been working on something big, and now we’d like to share it with you and get your feedback before we release to general availability. The time has come—we’ve combined Windows Admin Center: Administration Mode (aMode) and Windows Admin Center: Virtualization Mode (vMode) into a single installer. Only one mode can be selected per installation, and we don’t support having both modes installed on the same machine.

New features in vMode now available include Azure Arc onboarding, backup and restore, certificate lifecycle management, and more. As with all our releases, we’ve also made bugfixes to improve your overall experience.

Thank you to our customers, partners, and fans for helping us to continue to improve and make Windows Admin Center better! Download the preview build today and leave us feedback on our GitHub.

What’s new in Windows Admin Center 2610 (preview)

Platform

Combined mode installer

Windows Admin Center now provides a unified installer experience for both Administration Mode (aMode) and Virtualization Mode (vMode). Administrators can deploy and configure their preferred management mode from a single installation workflow, reducing setup complexity and streamlining deployment.

  • Simplified installation experience with a single installer
  • Faster deployment and onboarding for new environments
  • Reduced administrative overhead when evaluating or adopting vMode
  • Consistent setup and configuration workflow across Windows Admin Center management experiences

The combined installer helps organizations get started more quickly while providing a more streamlined path to advanced virtualization management capabilities.

 

 

New Azure registration experience

With this release, we’ve redesigned the gateway Azure registration experience. It’s now easier than ever to connect Windows Admin Center to Azure with just a few clicks. We’ve reduced the setup friction by requesting only the permissions needed for the current user and registration task. This new flow does not require tenant-level administrator consent, so teams no longer need to coordinate with a highly privileged tenant administrator before getting started. Administrators can further restrict who can perform Azure operations in Windows Admin Center by assigning appropriate permissions through Azure role-based access control (Azure RBAC).

Access this new experience by navigating to your Windows Admin Center gateway settings and selecting the Register tab.

October 20th, 2026 update: The public preview build has been refreshed to version 2.8.1.6 and includes fixes for the issues previously reported with this experience. 

Key bug fixes

  • Fixed an issue where the installer was failing with “RegCreateKeyEx failed, code 5” (reported in the comments of the last generally available Windows Admin Center release)

Virtualization mode

Haven't been following Windows Admin Center: Virtualization Mode? Read our blog series, documentation, and be sure to check out the release notes for our previous previews before you get started. 

Help us shape the future of storage in Virtualization Mode

We’re looking at what storage experiences we should prioritize next for Windows Admin Center: Virtualization Mode, and we want to make sure we’re focusing on the scenarios that matter most to customers.

If you work with SAN, SMB/file storage, Storage Spaces Direct (S2D), or other storage architectures, please take a few minutes to share your feedback in this survey.

Your input will help us better understand what customers are using today and where you’d like to see us invest next. We'd love to hear from you!

Update on the VM Conversion tool

Microsoft is aware of a change Broadcom has made affecting the availability of the VMware Virtual Disk Development Kit (VDDK) package required by the preview VM Conversion extension in Windows Admin Center. We are actively evaluating options to continue supporting customers desire to migrate away from Broadcom. However, at this time we do not have an alternative available and would recommend customers discontinue evaluation of the preview VM Conversion tool until we can provide an update. As the options under evaluation all require significant rework of the extension’s implementation, we have removed the extension from the extension feed. Customers who need to proceed with migrations can consider System Center Virtual Machine Manager (SCVMM) for migrations to Windows Server with Hyper-V, or Azure Migrate (agent-based) for migrations to Azure. 

We hope to provide you with another update soon.

Azure Arc onboarding

Connecting your virtualization environment to Azure is now easier than ever. vMode provides a streamlined Azure Arc onboarding experience that helps administrators quickly register and connect their infrastructure to Azure while minimizing setup complexity.

By onboarding through Azure Arc, organizations can extend their hybrid management capabilities, gain greater visibility into their infrastructure, and take advantage of Azure-powered services and experiences directly from their connected environment.

 

 

Key benefits:

  • Faster onboarding to Azure Arc
  • Simplified hybrid infrastructure management
  • Enhanced visibility across on-premises and Azure resources
  • Access to Azure-integrated management and operational services

Add resource

Networking improvements

We've made several improvements to the networking experience in vMode to make it easier to configure, validate, and troubleshoot networking when adding resources.

Improved network intent status visibility

The Networking page in the Add Resource workflow now displays the status of existing network intents detected on your hosts. You can review intent health, identify configuration issues earlier in the onboarding process, and troubleshoot intents that need attention.

Refresh networking state without restarting the workflow

If you make networking changes directly on a host while adding a resource, you can now refresh the Networking page to retrieve the latest configuration without exiting and restarting the Add Resource workflow. This makes it easier to resolve networking issues and continue onboarding from where you left off.

Storage VLAN override support

Storage network intent templates now support storage VLAN overrides, giving you more flexibility when configuring storage networks that require VLAN settings that differ from the defaults defined by the intent template.

More flexibility for external storage deployments

The Add Resource workflow no longer requires a storage intent for deployments using external storage. Customers who rely on dedicated storage networking can continue to configure storage intents as needed, while external storage deployments can onboard without configuring a storage intent.

Improved networking diagnostics

We’ve also made it easier to troubleshoot networking issues by including Network ATC Event Logs in vMode Agent logs, providing additional diagnostic information when investigating network intent configuration or validation issues.

Resume/retry functionality

After you begin adding a resource to be managed through vMode, transient issues like loss of connectivity or configuration changes can cause your workflow to fail. Previously, we required you to clean up the workflow and completely restart, going through the Add Resource wizard again. Now, we’ve added the ability to resume workflow steps (in the case of service disruption) and retry steps have failed, as long as rerunning the step won’t disrupt anything else in the wizard.

As part of workflow feature expansion work, we’ve also made two changes to our deployment process. When you begin to deploy your machine to vMode, it will immediately be added to the navigation hierarchy. If you select your object before it’s ready, you’ll be able to see the status of its deployment, similar to how it appears in the workflow status pane. That way if you don’t make it back to the workflow for a while, you’ll know where to find the information you need to get started or rectify any issues if they occur during deployment.

Backup and restore

Protect and recover your vMode environment with built-in backup and restore capabilities. Backup packages capture critical vMode management data, including virtualization inventory, cluster metadata, gateway configuration, certificates, RBAC settings, templates, and operational state, helping ensure business continuity and disaster recovery readiness.

With restore support, administrators can recover a vMode deployment after infrastructure failures, configuration errors, or migration scenarios. Restored environments retain key management settings and virtualization metadata, reducing recovery time and simplifying operational continuity.

Certificate lifecycle management

vMode uses certificates to help secure communication and establish trust between the Windows Admin Center gateway and managed hosts. Self-signed certificates are a great fit for testing because they can be generated quickly without requiring an existing certificate authority or PKI configuration. This makes it easier to evaluate vMode deployment workflows and validate connectivity in non-production environments.

For production environments, however, we now support managing vMode certificates through Active Directory Certificate Services (AD CS) for stronger governance and scalability. Centralized issuance and certificate templates help administrators control certificate configuration and align deployments with existing PKI policies. AD CS also integrates certificates with the organization’s established trust infrastructure. Automated renewal and consistent lifecycle management improve auditing and reduce the risk of service interruptions caused by expired certificates.

To configure your Windows Admin Center gateway to manage certificates using AD CS, navigate to your gateway settings and select the Certificates tab.

Detailed documentation on how to configure certificate templates for use with autorenewal is coming soon.

Live migration

Live migration is a critical virtualization capability that allows a running virtual machine to move from one physical host to another with little or no downtime. This enables administrators to perform hardware maintenance, apply updates, balance workloads, and respond to failures without disrupting applications or users. By eliminating the need to shut down VMs during these operations, live migration improves availability and helps organizations meet business continuity and service-level objectives. It is a foundational technology for highly available and flexible virtualized environments.

Making the live migration experience in the virtual machines tool aware of your vMode managed machines is a small step towards making your virtualization management experience easier than ever. To try it out, navigate to the Virtual Machines tool, select a VM, and then select Manage > Move.

Key bug fixes

  • The GPU tool is now available in vMode
  • Improved agent logging
  • Agent health indicators are now visible in navigation hierarchy

Other improvements

New SDK—now with React support

The Windows Admin Center SDK has been updated to version 6.0.0! This new version features two major updates: commands for upgrading existing Windows Admin Center extensions to Angular 20 as well as commands for creating and testing React-based Windows Admin Center extensions. The documentation for preparing your development environment and creating a tool extension has been updated to reflect these changes.

Known issues

The following issues about this build are known and actively being addressed:

  • [vMode] The Azure Arc-enabled status table may appear inaccurate when collapsed.
  • [vMode] Some links within tool extensions may redirect you to an aMode interface.
  • [both modes] When performing VM live migration, the operation may fail if the source and target nodes have different authentication methods.
  • [both modes] The Azure registration experience may not work correctly at this time.

Happy testing,

Davanna and the Windows Admin Center team

Updated Oct 29, 2026
Version 5.0

22 Comments

  • agoss's avatar
    agoss
    Brass Contributor

    Hello! I was able to get this latest version installed successfully, however we have so far been unable to add our existing clusters due to Network Intent failures. It errors out when deploying them from the wizard, and while it recognizes manually created intents on the cluster it does not see them as valid and so we are unable to proceed with enrollment. 

    • Davanna-White's avatar
      Davanna-White
      Icon for Microsoft rankMicrosoft

      Hey agoss​ , 

      I'm sorry to hear you've been encountering networking failures during your onboarding experience. We are tweaking that experience before we go to general availability with additional validation that will hopefully provide clearer troubleshooting steps in this situation. Is this happening on the "Networking" tab in the Add resource wizard or after you have begun the onboarding workflow? 

      Also tagging my colleague cindywan​ for awareness. 

      • agoss's avatar
        agoss
        Brass Contributor

        Hi Davanna-White​ , thanks for the prompt response! When it fails to deploy from the onboarding wizard, it occurs towards the end - after all the nodes have been configured when it pushes out the intent profiles. The specific error in that scenario is: 

        Failed to add . Network intent creation failed on <cluster-fqdn>: Failed to create network intent 'FAB02_Compute_Management' on target '<cluster-fqdn>': Exception calling "ReadIntentRequestFromStore" with "2" argument(s): "Failed to open local cluster"

        When I create the intent profiles manually on the cluster before enrollment, it detects them during the enrollment wizard but shows 

        Unsuccessful network intent configuration detected
        Remove the intent or update the intent configuration on the target host using Set-NetIntent, then refresh the Existing network intents section. For more information, see the link: Set-NetIntent

        I have confirmed the intents are deployed and valid on the cluster via the Get-NetIntent cmdlet and using the Set-NetIntent cmdlet does not seem to help. 

  • Blakkheim's avatar
    Blakkheim
    Copper Contributor

    Tested on both a new and an existing Windows Server 2025 VM. The installation completed successfully in both scenarios, but the portal does not load at all.

    This is disappointing, as we have been eagerly awaiting this release. Windows Admin Center remains very slow when working with Hyper-V clusters, and the Virtual Machines extension is still in preview. We were hoping this solution would finally offer a stable and responsive management experience for Hyper-V environments.

    • Davanna-White's avatar
      Davanna-White
      Icon for Microsoft rankMicrosoft

      Hey Blakkheim​ , thanks for trying this build out. Are you saying you're not able to make it to the login screen? 

       

      The "preview" tag for the Virtual Machines tool is a bit misleading. We'd implemented a new inventory page, which is the piece of the extension that the "preview" tag applies to-- the entire extension is not in preview. The Virtual machines tool continues to be a very high priority for us, and we're planning on making more improvements in the coming months that will target responsiveness and bring new features. 

      • Blakkheim's avatar
        Blakkheim
        Copper Contributor

        Hi, yes, the page does not load, as if the web server is not running or the page does not exist. I have verified that the services are running. The issue occurs with the installation of WAC 2610 in v-mode. I did not encounter this issue with previous versions when using a-mode.

  • dmutsaers's avatar
    dmutsaers
    Iron Contributor

    Does it support Windows Server 2022/2025 Hyper-Converged Infrastructure with Storage Spaces Direct and Azure Local?

    • Davanna-White's avatar
      Davanna-White
      Icon for Microsoft rankMicrosoft

      Azure Local does not support management with Windows Admin Center vMode. Support for HCI and S2D is on the roadmap but not yet included in this release. 

      • dmutsaers's avatar
        dmutsaers
        Iron Contributor

        Is Azure Local on the roadmap too, or will Azure Local be unsupported in Windows Admin Center vMode?

  • dmutsaers's avatar
    dmutsaers
    Iron Contributor

    Just installed Windows Admin Center 2610 (preview). As always, no access when using a public certificate and FQDN.

  • mark_v's avatar
    mark_v
    Copper Contributor

    Unable to install. I get "This app can't run on your PC."

    Tried installing on Server 2022, 2025 and Windows 11. 

    • Davanna-White's avatar
      Davanna-White
      Icon for Microsoft rankMicrosoft

      Hey mark_v​ , which mode are you trying to install? And have you tried running it as administrator? 

      This issue often arises as a result of your environment/permissions configuration.

      • mark_v's avatar
        mark_v
        Copper Contributor

        I was able to figure this out. It was a permission issue. Thanks so much for your quick reply. I had the previous preview version so I'm looking forward to working with this update. Thanks again.

  • Thanks for sharing, and it is good to see one installer 😊

    Hopefully, this one still supports the same or at least similar unattended installation options as vMode previously 😊

     

    Happy Azure Localling 🤣

    • Davanna-White's avatar
      Davanna-White
      Icon for Microsoft rankMicrosoft

      Hey cblackuk1​ , it sure does! You can install via INI file, and if using the command line you can use /Mode=Administration or /Mode=Virtualization to specify the mode you want to install (if you select Virtualization, we can read the database credentials from your INI file or you can provide them interactively). If this field is omitted and you already have Windows Admin Center installed, we'll default to installing the mode you currently have installed. If the field is omitted and it's a fresh install, we'll install aMode by default. 

      We'll make sure the public documentation has all of this information by the time this version goes GA. 😄