Issue with Azure Arc Resource Bridge on Re-Onboarded Hyper-V Host

figured it out thanks

PS C:\Windows\system32> Get-Service | Where-Object {

$_.Name -match "arc|aks|kube|hybrid|resource"

} | Select Name, Status

Name Status

ArcProxy Running

GCArcService Running

WSearch Stopped

PS C:\Windows\system32> Get-WindowsFeature | Where-Object {

$_.Name -match "Hyper-V|Containers"

}

Display Name Name Install State

[X] Hyper-V Hyper-V Installed

[ ] Containers Containers Available

    [X] Hyper-V Management Tools                    RSAT-Hyper-V-Tools             Installed

        [X] Hyper-V GUI Management Tools            Hyper-V-Tools                  Installed

        [X] Hyper-V Module for Windows PowerShell   Hyper-V-PowerShell             Installed

PS C:\Windows\system32> Get-HnsNetwork | Select Name, Type

Get-HnsNetwork : The term 'Get-HnsNetwork' is not recognized as the name of a cmdlet, function, script file, or

operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try

again.

At line:1 char:1

• Get-HnsNetwork | Select Name, Type

• 
      + CategoryInfo          : ObjectNotFound: (Get-HnsNetwork:String) [], CommandNotFoundException
  
      + FullyQualifiedErrorId : CommandNotFoundException
  
  

Hi ,

i don't have anything from Azure side, the issue is from the host itself. it seems there are some elements residue. no VMs on hyperv available or something.

what shall i do ? any commands i can run to see whats remaining ?

thanks

Hello Karim, Hey Karim – it sounds like even though you deleted the old subscription, there’s still a leftover Arc Resource Bridge deployment sitting on that Hyper-V host, and that’s why the hybrid-AKS extension sees “an Arc Resource Bridge instance is already setup.” You’ll need to do a two-part cleanup: one on the Azure side, and one on the Hyper-V host itself. Here’s what you can try:

1. Clean up in Azure • If you see any “Arc Resource Bridge” or “Azure Kubernetes Service hybrid” resources in your new subscription’s resource group, delete them. – CLI example (replace placeholders):

      
      az connectedmachine extension delete \
      
      
      --resource-group MyRG \
      
      
      --machine-name MyHostName \
      
      
      --name AzureKubernetesServiceHybrid  
      
   

   – Or, if you used the appliance resource model:

      
      az arcappliance delete \
      
      
        --resource-group MyRG \
      
      
        --name MyBridgeName \
      
      
        --yes  
      
   

   • Confirm there are no appliances or extensions registered for that host:

      
      az connectedmachine list --resource-group MyRG  
      
      az arcappliance list   --resource-group MyRG  
      
   

2. Tear down the old Resource Bridge on the Hyper-V host a. Open Hyper-V Manager (or use PowerShell) and look for any VM named something like “ArcResourceBridge” or similar. Shut it down and delete it, plus its virtual hard disks. b. Remove any virtual switches that were created for the bridge:

      
      Get-VMSwitch | Where-Object Name -Like "ArcBridge*" | Remove-VMSwitch -Force
      
   

   c. Stop and uninstall the Connected Machine & Kubernetes agents: – Stop service:

       ```powershell
      
      
       Stop-Service -Name AzureConnectedMachineAgent -Force
      
      
   

         – Uninstall the agent (use Control Panel or msiexec/uninstall string):  
      
      ```yaml
       ```powershell
      
      
       msiexec /x {AzureConnectedMachineAgent-ProductCode} /qn
      
      
   

      d. Remove any leftover folders:  
      
      ```powershell
      
      Remove-Item -Recurse -Force C:\ProgramData\AzureConnectedMachine
      
      Remove-Item -Recurse -Force C:\ProgramData\AzureConnectedMachine\KubernetesAgent
      
   

3. Reboot the Hyper-V host A full restart ensures no bits of the old bridge are still in memory or locked by services.
4. Re-onboard & add the AKS hybrid extension • In Windows Admin Center, go through the Azure Arc onboarding wizard again to register the server. • Once it’s successfully Arc-enabled, add the “Azure Kubernetes Service hybrid” extension. It should now deploy a fresh resource bridge VM.

If after those steps you still see the same error, can you share:

• The output of Get-VM and Get-VMSwitch on your Hyper-V host to confirm all bridge VMs/switches are gone

• The result of az connectedmachine list --resource-group <YourRG> and az arcappliance list --resource-group <YourRG>

• Any logs from C:\ProgramData\AzureConnectedMachine\Logs\ (or via az arcappliance logs)

That info will help pinpoint any stray configuration sticking around. Let me know!