SCVMM can't add the Hyper-V host

ejdgr8 · Mar 4, 2026

I currently have a SCVMM but it stucks on BSOD, now I rebuild the SCVMM and I'm trying to add the host but when adding there is a issue.

SCVMM displays cluster nodes as pending/unknown and the VMM Agent setup failed.

We tried installing the agent manually but there's an error.

Steps tried:
Uninstall the Old SCVMM Agent on the Hyper-V Host (rebooted)
Check if there are certificate from old SCVMM (none)

WindowsForum AI · Mar 4, 2026

Hi ejdgr8,
Thanks for the details — SCVMM 2022 managing a Windows Server 2025 Hyper‑V cluster is very likely the root cause.

Key Issue

SCVMM 2022 does NOT support Windows Server 2025 hosts.
When you try to add the cluster:

The VMM agent fails to install
Setup ends with “Setup Wizard ended prematurely”
Hosts remain Pending
Cluster status becomes Unknown

This happens because the VMM 2022 agent does not recognize the Server 2025 Hyper‑V APIs, so the installation aborts.

Supported combinations

SCVMM Version	Supported Hyper‑V Hosts
SCVMM 2019	Server 2016 / 2019
SCVMM 2022	Server...

WindowsForum AI · Mar 4, 2026

Hi ejdgr8,
From your screenshots and description, this looks like a leftover SCVMM agent / trust issue after the SCVMM rebuild. When VMM is rebuilt, Hyper‑V hosts often still contain old agent configuration or registry entries, which causes:

Host stuck in “Pending”
Manual agent install “Setup Wizard ended prematurely”
Cluster status Unknown in VMM

Even if the agent was uninstalled, residual files/registry keys often remain.
Below is the cleanest way to fix it.

Step 1 — Completely remove the old SCVMM agent remnants

Run the following on each Hyper‑V host.

1. Stop the VMM agent service (if present)

Open PowerShell as Administrator:
Stop-Service SCVMMAgent -Force

2. Remove the agent

msiexec /x {8B63C3D2-...}
If that fails, remove it from:
Control Panel → Programs → Microsoft System Center Virtual Machine Manager Agent

Step 2 — Delete leftover folders

Delete these folders if they exist:

Code:

C:\Program Files\Microsoft System Center\Virtual Machine Manager Agent
C:\ProgramData\VMMLogs

Step 3 — Clean registry entries

Open regedit and remove:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Agent
Also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VMM
Delete if present.

Step 4 — Reset WinRM (very important)

SCVMM uses WinRM to push the agent.
Run:
winrm quickconfig
Then reset it:
winrm invoke Restore winrm/Config
Restart the service:
Restart-Service WinRM

Step 5 — Verify firewall rules

Make sure these are open on the Hyper‑V host:

Code:

5985  WinRM HTTP
5986  WinRM HTTPS
8100  VMM Agent

Quick test from SCVMM server:
winrm id -r:hyperv01

Step 6 — Add the host again from SCVMM

In VMM Console:

Code:

Fabric
 → Servers
 → Add Resources
 → Hyper‑V Hosts and Clusters

Use Run As account with local admin rights on the Hyper‑V host.
VMM will push the agent automatically.

Important check (very common after VMM rebuild)

Make sure the SCVMM service account is:

Local Administrator on Hyper‑V hosts
Member of Hyper‑V Administrators

Example:
net localgroup administrators DOMAIN\VMMServiceAccount /add

If the issue still happens

Please check this log on the Hyper‑V host:
C:\ProgramData\VMMLogs\scvmmagent.log
or
C:\Windows\Temp\VMM*.log
The exact error in that log will show why the agent install fails.

✅ One more quick question:

What SCVMM version did you rebuild? (2019 / 2022?)
What Windows Server version are the Hyper‑V hosts?
Is this a Hyper‑V cluster or standalone hosts?

Those details will help narrow it down quickly.
—
Regards,
ChatGPT
WindowsForum Support Assistant

ejdgr8 · Mar 4, 2026

WindowsForum AI said:
Hi ejdgr8,
From your screenshots and description, this looks like a leftover SCVMM agent / trust issue after the SCVMM rebuild. When VMM is rebuilt, Hyper‑V hosts often still contain old agent configuration or registry entries, which causes:

Host stuck in “Pending”

Manual agent install “Setup Wizard ended prematurely”

Cluster status Unknown in VMM

Even if the agent was uninstalled, residual files/registry keys often remain.
Below is the cleanest way to fix it.

Step 1 — Completely remove the old SCVMM agent remnants
Run the following on each Hyper‑V host.

1. Stop the VMM agent service (if present)
Open PowerShell as Administrator:
Stop-Service SCVMMAgent -Force

2. Remove the agent
msiexec /x {8B63C3D2-...}
If that fails, remove it from:
Control Panel → Programs → Microsoft System Center Virtual Machine Manager Agent

Step 2 — Delete leftover folders
Delete these folders if they exist:

Code:

C:\Program Files\Microsoft System Center\Virtual Machine Manager Agent C:\ProgramData\VMMLogs

Step 3 — Clean registry entries
Open regedit and remove:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Agent
Also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VMM
Delete if present.

Step 4 — Reset WinRM (very important)
SCVMM uses WinRM to push the agent.
Run:
winrm quickconfig
Then reset it:
winrm invoke Restore winrm/Config
Restart the service:
Restart-Service WinRM

Step 5 — Verify firewall rules
Make sure these are open on the Hyper‑V host:

Code:

5985 WinRM HTTP 5986 WinRM HTTPS 8100 VMM Agent

Quick test from SCVMM server:
winrm id -r:hyperv01

Step 6 — Add the host again from SCVMM
In VMM Console:

Code:

Fabric → Servers → Add Resources → Hyper‑V Hosts and Clusters

Use Run As account with local admin rights on the Hyper‑V host.
VMM will push the agent automatically.

Important check (very common after VMM rebuild)
Make sure the SCVMM service account is:

Local Administrator on Hyper‑V hosts

Member of Hyper‑V Administrators

Example:
net localgroup administrators DOMAIN\VMMServiceAccount /add

If the issue still happens
Please check this log on the Hyper‑V host:
C:\ProgramData\VMMLogs\scvmmagent.log
or
C:\Windows\Temp\VMM*.log
The exact error in that log will show why the agent install fails.

✅ One more quick question:

What SCVMM version did you rebuild? (2019 / 2022?)

What Windows Server version are the Hyper‑V hosts?

Is this a Hyper‑V cluster or standalone hosts?

Those details will help narrow it down quickly.
—
Regards,
ChatGPT
WindowsForum Support Assistant

The SCVMM Version is 2022
the windows server version are 2025
Hyper-v Cluster enabled

WindowsForum AI · Mar 4, 2026

Hi ejdgr8,
Thanks for the details — SCVMM 2022 managing a Windows Server 2025 Hyper‑V cluster is very likely the root cause.

Key Issue

SCVMM 2022 does NOT support Windows Server 2025 hosts.
When you try to add the cluster:

The VMM agent fails to install
Setup ends with “Setup Wizard ended prematurely”
Hosts remain Pending
Cluster status becomes Unknown

This happens because the VMM 2022 agent does not recognize the Server 2025 Hyper‑V APIs, so the installation aborts.

Supported combinations

SCVMM Version	Supported Hyper‑V Hosts
SCVMM 2019	Server 2016 / 2019
SCVMM 2022	Server 2019 / 2022
System Center 2025 (VMM 2025)	Server 2025

Your current combination

Code:

SCVMM 2022
Hyper‑V Host: Windows Server 2025

This is unsupported, which explains the agent installation failure.

Recommended Fix

You have two options:
Option 1 — Upgrade VMM (Recommended)
Upgrade to System Center VMM 2025, which supports Windows Server 2025 clusters.
Option 2 — Downgrade Hyper‑V hosts
Reinstall hosts with:
Windows Server 2022
Then SCVMM 2022 will manage them normally.

Quick confirmation test

On the Hyper‑V host run:
systeminfo | findstr /B /C:"OS Name"
If it shows Windows Server 2025, that confirms the incompatibility.

Why replication also failed earlier

Your earlier Hyper‑V replication error can also occur when management stack versions don't match, which fits this environment.

✅ Best path in production environments now:
Upgrade your management stack:
SCVMM 2022 → System Center VMM 2025
so it can properly manage the Server 2025 Hyper‑V cluster.

If you'd like, I can also show you a clean upgrade path from SCVMM 2022 → SCVMM 2025 without losing your fabric configuration (clusters, networking, library, etc.). It’s about a 15–20 minute upgrade if SQL is healthy.

SCVMM can't add the Hyper-V host

ejdgr8

Member

Key Issue​

Supported combinations​

WindowsForum AI

AI

Step 1 — Completely remove the old SCVMM agent remnants​

1. Stop the VMM agent service (if present)​

2. Remove the agent​

Step 2 — Delete leftover folders​

Step 3 — Clean registry entries​

Step 4 — Reset WinRM (very important)​

Step 5 — Verify firewall rules​

Step 6 — Add the host again from SCVMM​

Important check (very common after VMM rebuild)​

If the issue still happens​

ejdgr8

Member

Step 1 — Completely remove the old SCVMM agent remnants​

1. Stop the VMM agent service (if present)​

2. Remove the agent​

Step 2 — Delete leftover folders​

Step 3 — Clean registry entries​

Step 4 — Reset WinRM (very important)​

Step 5 — Verify firewall rules​

Step 6 — Add the host again from SCVMM​

Important check (very common after VMM rebuild)​

If the issue still happens​

WindowsForum AI

AI

Key Issue​

Supported combinations​

Your current combination​

Recommended Fix​

Quick confirmation test​

Why replication also failed earlier​

Key Issue

Supported combinations

Step 1 — Completely remove the old SCVMM agent remnants

1. Stop the VMM agent service (if present)

2. Remove the agent

Step 2 — Delete leftover folders

Step 3 — Clean registry entries

Step 4 — Reset WinRM (very important)

Step 5 — Verify firewall rules

Step 6 — Add the host again from SCVMM

Important check (very common after VMM rebuild)

If the issue still happens

Step 1 — Completely remove the old SCVMM agent remnants

1. Stop the VMM agent service (if present)

2. Remove the agent

Step 2 — Delete leftover folders

Step 3 — Clean registry entries

Step 4 — Reset WinRM (very important)

Step 5 — Verify firewall rules

Step 6 — Add the host again from SCVMM

Important check (very common after VMM rebuild)

If the issue still happens

Key Issue

Supported combinations

Your current combination

Recommended Fix

Quick confirmation test

Why replication also failed earlier