Arc agent installation fails with error 1603 – GCArcService timeout on Windows 11 26100

Hello Tomas, it looks like your Arc Connected Machine agent installer is rolling back because the GCArcService (the Guest Configuration host service) never comes up within its 30-second startup window, which triggers the MSI’s Error 1603. Here’s what you can try:

1. Increase the Windows service startup timeout
   • Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
   • Add (or edit) a DWORD value named ServicesPipeTimeout and set it to 120000 (decimal)
   • Reboot and then rerun the MSI.
   This gives GCArcService more time to initialize before Windows declares it “failed to start.”
2. Check the GCArcService logs and Event Viewer
   • In Event Viewer → Windows Logs → Application or System, look for errors around GCArcService startup.
   • Under C:\ProgramData\AzureConnectedMachineAgent\Log, see if there’s a GCArcService*.log or any .NET exceptions.
   • Try starting it manually:

     cd "C:\Program Files\AzureConnectedMachineAgent"

     .\GCArcService.exe –service

     and watch for any errors.
3. Verify prerequisites and OS support
   • Make sure .NET Framework 4.7+ is enabled on your Windows 11 box.
   • By design the Azure Connected Machine agent only supports Windows Server and IoT Enterprise OSes. Windows 11 Pro isn’t officially supported for the “servers” agent, so you may run into unexplained service failures (like this one).
4. Disable AV/Endpoint Protection temporarily Sometimes security software can block the service executable. If you have any third-party AV or corporate endpoint protection, pause it during the install.
5. Final workaround: install without Guest Configuration If you don’t need the Guest Configuration extension, you can install the agent, then run:

   azcmagent config set --disable-guest-configuration

   and restart the agent to avoid loading GCArcService altogether.

Let me know what you see in the Event Viewer or the manual service start attempt. If GCArcService logs show a specific exception, share that and we can dig deeper.

Reference docs:

• Troubleshoot Azure Arc “Not Installed” status

https://learn.microsoft.com/azure/azure-arc/servers/troubleshoot-agent-onboard

• Cannot Connect Server to Azure Arc


https://learn.microsoft.com/azure/azure-arc/servers/troubleshoot-networking#windows-tls-configuration-issues

• Azure Arc agent release notes & supported OS

https://learn.microsoft.com/azure/azure-arc/servers/agent-release-notes

Error 1603 with a GCArcService start timeout during Azure Connected Machine agent installation on Windows typically indicates that the Arc services were not configured or started correctly during MSI setup.

For Windows installations, the following points are relevant:

1. Run the installer elevated in a supported way On recent agent versions there is a known issue if the MSI is started only by double‑clicking and accepting UAC:
   • Instead of double‑clicking, either:
     • Right‑click AzureConnectedMachineAgent.msi and select Run as administrator, or
     • Open an elevated PowerShell or Command Prompt and run:

              msiexec.exe /i AzureConnectedMachineAgent.msi /qn /l*v "C:\Support\Logs\Azcmagentsetup.log"
       

   This avoids the condition where Arc services (including GCArcService) are not configured properly and can fail to start.
2. Verify installation logs and service logs
   • The MSI setup log from msiexec (for example C:\Support\Logs\Azcmagentsetup.log) will show the exact point where GCArcService fails.
   • After a failed attempt, check the Arc agent log directory for more detail:
     • %ProgramData%\AzureConnectedMachineAgent\log
   • If the service was created but fails to start, also review:
     • %ProgramData%\AzureConnectedMachineAgent\Log\himds.log
3. Confirm agent resources and services after a successful install attempt When installation succeeds, the following should exist:
   • Directories:
     • %ProgramFiles%\AzureConnectedMachineAgent
     • %ProgramFiles%\AzureConnectedMachineAgent\GCArcService\GC
     • %ProgramData%\AzureConnectedMachineAgent
     • %ProgramData%\GuestConfig
   • Services:
     • GCArcService (Guest configuration Arc Service)
     • ExtensionService
     • himds If GCArcService is missing or cannot be started manually after install, use the logs above to identify the underlying cause.
4. Use the latest agent build and upgrade path
   • Version 1.62 is the current release and includes fixes for configuration reliability and an azcmagent upgrade path. If an older version was ever partially installed, ensure it is fully removed and then install 1.62 from an elevated session.
5. Onboard and test connectivity after installation Once the MSI completes successfully and services are running:
   • Connect the machine with azcmagent from an elevated PowerShell:

          & "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" connect `
            --resource-group "disco.works" `
            --tenant-id "<tenant-id>" `
            --location "northeurope" `
            --subscription-id "<subscription-id>" --verbose
     

   • If connection fails, use the verbose log at:
     • %ProgramData%\AzureConnectedMachineAgent\Log\azcmagent.log and the agent error codes table to interpret any AZCMxxxx codes.

If GCArcService continues to time out even when the MSI is run elevated as above, the next step is to rely on the detailed MSI and Arc logs (Azcmagentsetup.log, himds.log, and azcmagent.log) to identify any environmental or configuration issue preventing the service from starting.

References:

• Azure Arc agent
• Troubleshoot Azure Connected Machine agent connection issues
• What's new with Azure Connected Machine agent
• Connect hybrid machines to Azure using a deployment script
• Connect hybrid machines to Azure by using Azure PowerShell