How to fix rollback problem in nova client session.

Hello Diana Jones, You are attempting to install the Azure Connected Machine Agent (MSI):

• Installation completes to 100%
• Then performs a rollback
• Issue occurs both Manual install (double-click MSI) and Software Center (SCCM) deployment

This confirms the issue is not deployment method-related, but a machine-level failure during installation finalization (post-install actions).

This behavior is consistent with a known Azure Connected Machine Agent installation issue combined with standard Windows Installer behavior:

• The MSI appears to finish, but:
  • Final service configuration fails (Arc services)
  • MSI triggers automatic rollback
• Common in:
  • Older agent versions (< v1.57)
  • Installations launched via double-click (non-elevated/UAC path)

Known Arc Agent MSI Limitation

Microsoft release notes state:

• Launching the installer via double-click + UAC may fail to properly configure Arc services https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-release-notes

This leads to:

• Service registration failure (HIMDS / GCArcService / ExtensionService)
• MSI completes UI but fails at final action → rollback

MSI executes installation in steps, If any final action fails, installer Returns“Return value 3” or Triggers full rollback automatically.

Use Proper Installation Method:

Use elevated command:

msiexec /i AzureConnectedMachineAgent.msi /l*v 
C:\Support\Logs\azcmagentsetup.log

Ensures:

• Proper privilege context
• Prevents service configuration failure

Use Latest Agent Version

Download latest MSI https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-release-notes Recommended version ≥ 1.57 and Avoid older installer defects

Check MSI Verbose Log (Mandatory for RCA):

Open log: C:\Support\Logs\azcmagentsetup.log Search Return value 3, Check lines immediately above it That line = actual failure cause.

Clean Existing/Corrupt Installation: Check if agent exists:

Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall |
Where-Object {$_.DisplayName -like "*Connected Machine*"}

If found msiexec /x {GUID} /quiet

Then manually remove leftovers: C:\Program Files\AzureConnectedMachineAgent and C:\ProgramData\AzureConnectedMachineAgent, then Reboot and retry install

Validate Service Creation Issues

Check:

• Event Viewer → System / Application logs
• Errors related to:
  • GCArcService
    • HIMDS

If timeout observed:

HKLM\SYSTEM\CurrentControlSet\Control
ServicesPipeTimeout = 120000

Temporarily Disable Security Blocking

• Antivirus / EDR (Defender, CrowdStrike, etc.)
• Especially important in SCCM scenarios

Microsoft explicitly recommends excluding install paths during agent installation https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-overview

Hope this helps, If you have any question, please do let us know, thanks

hi & thx for sharing urs issue here at Q&A portal,

An MSI rollback at 100% just means the install hit an error near the end and Windows Installer undid the changes. The UI won’t tell u why, so first get the MSI log. Run the installer from an elevated Command Prompt

msiexec /i AzureConnectedMachineAgent.msi /L*v C:\Temp\AzureArcAgent-install.log

Then search the log for

Return value 3

The lines just above that are usually the actual failure. Could be an old Arc agent install, pending reboot, blocked service creation, missing permissions, proxy/TLS issue, or endpoint security killing the install.

Before retrying

reboot

Then check if an old agent is already installed

sc query himds

If it exists, uninstall the old Azure Connected Machine agent first from Apps & Features, reboot, then install the current MSI as admin. check %TEMP% and C:\Windows\Temp are writable

enough free disk space AV/EDR isn’t blocking AzureConnectedMachineAgent.msi, azcmagent.exe, or service creation

Windows Installer service is running the machine can reach Azure Arc endpoints if the installer gets as far as registration

For Software Center, pull the client-side logs too C:\Windows\CCM\Logs\AppEnforce.log

C:\Windows\CCM\Logs\ExecMgr.log

AppEnforce.log normally shows the MSI exit code and exact command SCCM used.

Don’t keep retrying blind. Post the section around Return value 3 from the verbose MSI log, plus the MSI exit code from AppEnforce.log, and the real cause should be visible.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/