VM Guest Agent has the AMA extension installed and enabled, but only the AMAExtHealthMonitor process is running

Hi Daniel Essel

Verify the AMA extension has been correctly installed. You can review the installation logs in the following location:

C:\WindowsAzure\Logs\WaAppAgent.log

Look for any errors or warnings that might point to issues during the extension setup.

Although the registry key exists, the required persistence file does not. We recommend checking the relevant registry settings under:

HKLM\SOFTWARE\Microsoft\Azure\AzureMonitorAgent

Confirm that paths and file references in the registry match expected values and that the referenced file(s) exist on disk.

If the issue persists, please try uninstalling and then reinstalling the AMA extension on the affected VM. This can help regenerate any missing files or resolve potential corruption. You can perform this through the Azure portal or by using Azure CLI/PowerShell.

https://learn.microsoft.com/en-us/troubleshoot/azure/azure-monitor/azure-monitor-agent/ama-windows-installation-issues-prepare-troubleshooting
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-monitor/azure-monitor-agent/ama-windows-installation-issues-detailed-troubleshooting-steps

let us know if any help, we will always help as you needed.!

If the comment is helpful, please click "Upvote it".

Hi Daniel Essel
If you had a chance to see my Answer to your question. If it was helpful, please click "Upvote" and ''accept answer'' on my post let us know Thank you...!

Pranay,

That's the problem, the referenced persistence key file doesn't exist. That's why it's failing to start the AMA core processes.

I've already tried uninstalling and re-installing. I even attempted a reboot before and after and redeployed to a different Azure host.

Thanks,

Danny

Hi Daniel Essel,

Thanks for confirming your steps you followed till now. Since the issue persists even after a reinstallation and reboot, and the missing persistence key file is preventing core AMA processes from starting. please the following steps mentioned below

1. Check File System Permissions Ensure C:\WindowsAzure\Resources has correct NTFS permissions. The AMA agent may fail to write the key file if SYSTEM lacks write access. You can verify with:

icacls "C:\WindowsAzure\Resources" 

2. Perform a Full Clean Reinstall Uninstall the extension via CLI, then manually remove residual folders and registry keys before reinstalling:

  az vm extension delete --name AzureMonitorWindowsAgent

Then delete:

• C:\WindowsAzure\Resources\AMADataStore*
• HKLM\SOFTWARE\Microsoft\Azure\AzureMonitorAgent

Reinstall:

az vm extension set --name AzureMonitorWindowsAgent --version 1.34

If the issue is specific to v1.34.0.0, roll back to v1.33.1:

az vm extension set --name AzureMonitorWindowsAgent --version 1.33.1  

Run AMA Diagnostic Script

Use Microsoft’s support script to collect logs and verify dependencies:

Invoke-WebRequest https://aka.ms/AMAWindowsSupportScript -OutFile AMADiag.ps1

.\AMADiag.ps1

Please let us know if it was helpful, and feel free to reach out if you have any further queries.

Vinay,

Deleting both of these fixed the issue:

• C:\WindowsAzure\Resources\AMADataStore*
• HKLM\SOFTWARE\Microsoft\Azure\AzureMonitorAgent

I'll make note of that for future reference.

Appreciate the support and guidance! This really helpled!

Thanks,

Danny