Windows Admin Center File not found

Handian Sudianto 7,471 Reputation points
2026-09-21T03:24:40.99+00:00

My server onborded to azure arc and if i open windows admin center for this host i got below error. If i open windows admin center for anither host then it's work normally.

User's image

Azure Arc
Azure Arc

A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.

0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Senthil kumar 2,500 Reputation points
    2026-09-21T05:23:03.2033333+00:00

    Hi @Handian Sudianto

    1. Restart the Azure connected machines.

    Go to Powershell use below commands 

    Restart-Service himds
   Restart-Service ArcService
    • Clear WAC gateway 
        Remove-Item "C:\ProgramData\Microsoft\ServerManagementGateway\Cache" -Recurse -Force
  Restart-Service ServerManagementGateway
    • Re-register the server with Azure arc 
        azcmagent disconnect
  azcmagent connect --resource-group <RG> --tenant-id <TenantID> --location <Region>
    • check WINRM listener

      winrm enumerate winrm/config/listener If only HTTPS is listed, ensure WAC is configured for HTTPS or add HTTP: winrm create winrm/config/Listener?Address=*+Transport=HTTP

    • Update windows admin center extension

      In Azure Portal → Azure Arc → your server → Extensions → Windows Admin Center Click Update or Reinstall.

    Thanks

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-21T03:24:59.9533333+00:00

    For a "File not found" / 404 error on Windows Admin Center for an Azure Arc-enabled server, use this troubleshooting path on the affected server:

    1. Check the Azure Connected Machine Agent version
      • Versions 1.35 and 1.36 break Windows Admin Center connectivity.
      • Update the Arc agent to 1.37 or later.
    2. Restart the HIMDS service
      • RDP to the server.
      • Open PowerShell as Administrator and run:
         Restart-Service -Name himds
    3. Verify the AdminCenter extension version
      • In Azure portal, open the Arc-enabled server.
      • Go to Extensions.
      • Confirm the AdminCenter extension is 0.0.0.169 or higher.
      • If it is lower, uninstall and reinstall the extension.
    4. Confirm the Windows Admin Center service is running
      • RDP to the server.
      • Open Task Manager (Ctrl+Shift+Esc) > Services.
      • Verify ServerManagementGateway / Windows Admin Center is running.
      • If it is stopped, start it.
    5. Verify the reverse proxy port is enabled in Arc
      • RDP to the server.
      • Open PowerShell as Administrator and run:
         azcmagent config list
      • Check that the Windows Admin Center port appears under incomingconnections.ports.
      • If it is missing, set it:
         azcmagent config set incomingconnections.ports <port>
      • If Windows Admin Center was installed on port 443, that port must appear in the output.
    6. Check outbound connectivity from the server The server must have outbound access to:
      • *.wac.azure.com
      • *.waconazure.com
      • pas.windows.net
      • *.servicebus.windows.net
    7. If the extension installation is unhealthy, test service reachability Run from PowerShell on the server: 
         Invoke-RestMethod -Method GET -Uri https://<your_region>.service.waconazure.com
      Expected result: 
         Microsoft Certificate and DNS service for Windows Admin Center in the Azure Portal
      If this fails, check firewall rules blocking outbound traffic.
    8. If one tool or page fails to load
      • Switch to another Windows Admin Center tool and then return.
      • If no tools load, close the blade and reconnect.
    9. If the problem continues, reinstall the extension
      • In Azure portal, go to the Arc-enabled server.
      • Open Extensions.
      • Uninstall the Admin Center extension.
      • Then go back to Windows Admin Center and install it again.
    10. If still failing, collect logs for support
    • In Azure portal: Settings > Extensions > AdminCenter > View Detailed Status
    • On the server, run:
    azcmagent logs
    • If a network trace is collected, review it first because it can contain sensitive data.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.