Troubleshooting Cloudamize Agent Access Denied Errors

Overview

This article addresses the Win32Exception: Access is denied error, which can occur during two distinct phases of the Cloudamize lifecycle: the initial installation and the post-installation data upload. While the error message is the same, the causes range from local User Account Control (UAC) and permission restrictions during setup to network security software or EDR (Endpoint Detection and Response) tools blocking data transmission via curl.

Follow the steps below to identify whether the denial is happening at the system level (Installation) or the network level (Connectivity).

Troubleshooting: Stage 1 (Installation)

If the installer fails to complete or rolls back immediately, the system prevents the MSI from creating the necessary environment.

1. Forced Elevation via CLI

Standard administrative users are still subject to UAC restrictions.

Search for CMD, right-click, and select Run as Administrator.
Run the installer with verbose logging enabled: msiexec /i "CloudamizeAgent.msi" /L*V "C:\Cloudamize_Install_Log.txt.txt"
Note: If it fails, open the log and search for Return Value 3. The lines just above this will show the specific folder or registry path denied.

2. Directory Ownership

Previous failed installs may leave orphaned folders that your current user doesn't own.

Folder: Navigate to C:\Program Files (x86)\. If a Cloudamize folder exists, right-click it > Properties > Security > Advanced. Change the Owner to your current admin user and check "Replace owner on subcontainers."

3. Antivirus/EDR "Interprocess" Blocking

Security tools (CrowdStrike, SentinelOne, etc.) often block MSI installers from spawning background services.

Action: Check your EDR console for "Prevention" events. You may need to whitelist the Cloudamize certificate or the path C:\Windows\Installer\*.msi.
Action: Please open an admin PowerShell and run the following command after attempting to execute curl:
CODE
```
Get-MpThreatDetection
```
This will list any executables that Windows Defender has recently blocked.

Troubleshooting: Stage 2 (Connectivity & Upload)

If the agent is installed but logs (found in C:\Program Files (x86)\Cloudamize\log_backup.txt) show Curl.ReportStatus(): Win32Exception = Access is denied:

1. Verify Execution Permissions for Curl

The Cloudamize Agent utilizes a packaged version of the curl utility to transmit data. Even if the service is running, it will fail if the service account does not have the "Read & Execute" permission for the binaries within the installation folder.

Action: Navigate to C:\Program Files (x86)\Cloudamize. Ensure that the service account (usually SYSTEM or a dedicated service user) and the Local Administrators group have Full Control or at least Read & Execute permissions on all files within this directory, specifically curl.exe.

2. Proxy & Firewall Configuration

An "Access Denied" during a curl call often means a local firewall or proxy is refusing the socket connection.

Whitelisting: Ensure outbound Port 443 is open to: am.cloudamize.com (US) or am-de.cloudamize.com (EU).
Manual Test: From the agent folder, run: curl.exe -k https://am.cloudamize.com/cxf/test. If this fails, the block is at the Network/Proxy level.

3. Security Software (EDR/HIPS) Interrogation

Endpoint Detection and Response (EDR) tools may flag the agent's attempt to launch a child process (curl.exe) to an external URL as suspicious behavior.

Action: Review logs in tools such as CrowdStrike, SentinelOne, or Windows Defender. Look for "Process Blocked" or "Unauthorized Execution" events related to the Cloudamize installation path.
Action: Please open an admin PowerShell and run the following command after attempting to execute curl:
CODE
```
Get-MpThreatDetection
```
This will list any executables that Windows Defender has recently blocked.

Data Collection Fallback: If you have applied the fixes above and continue to see "Access is denied," We suggest collecting data by adding the node to the Cloudamize Agentless Data Collector (ADC).

Need Further Support?
If the problems persist, please run the installer with verbose logging enabled: msiexec /i "CloudamizeAgent.msi" /L*V "C:\Cloudamize_Install_Log.txt.txt" and contact us with the details below:

Attach the logfile created using the verbose logging
Email the log file to: helpdesk@cloudamize.com