Skip to main content
Installation failures typically fall into one of three categories: a missing system dependency on the target endpoint, a network connectivity problem that blocks the registration step, or a healthy agent that isn’t yet collecting. Checking the installer exit code or log output will usually point you to the right article below.

Windows: Error -1073741515 (VC++ Missing)

The installer exits with error -1073741515 (0xC0000135 STATUS_DLL_NOT_FOUND) because the Microsoft Visual C++ Redistributable is absent. Install the VC++ runtime first, then re-run the Origin installer.

macOS: Agent Installed but No AI Events

No AI activity appears in the console for a macOS endpoint. Confirm the agent and watchdog are running, and that Full Disk Access is granted to Origin.app.

Network Connectivity Requirements

The agent needs to reach three Origin-hosted endpoints in its region over HTTPS: registration, endpoint, and agent-cdn. If one is blocked by a firewall, proxy, or SASE gateway, installation fails, telemetry stops flowing, or updates stop.

Prerequisites & Known Issues

Review the required Visual C++ Redistributable version, necessary outbound endpoints, SASE traffic-steering compatibility notes, and Application Control considerations before deploying the agent at scale.

​
Issue types at a glance

​
Missing Visual C++ Redistributable (Windows)

When the Microsoft Visual C++ 2015–2022 Redistributable is not present on a Windows endpoint, the Origin agent’s binaries cannot load and the installer exits with error -1073741515. This is common on fresh OS images, minimal builds, and Windows Server Core installations. The fix is to install the VC++ runtime before running the Origin installer — or to chain it as a prerequisite in Intune, SCCM, or MECM for fleet deployments.

​
Agent healthy but no AI events (macOS)

If the agent installed and is running but no AI activity reaches the console, the usual cause is that Full Disk Access was never granted to Origin.app. The agent needs it to read application logs and detect AI tooling in user-scoped locations, so without it the agent runs but captures nothing. On MDM-managed fleets this is pre-approved by the PPPC profile.

​
Network connectivity failures

During installation, the Origin agent contacts the registration endpoint for its region (for example registration.prod.originhq.com) to exchange the provisioning token for a unique client certificate. If that endpoint is unreachable, the install fails and the agent has no certificate. It can’t authenticate even after connectivity is restored, so you need to re-run the install. During normal operation, the agent relies on the endpoint host for heartbeat, configuration, and AI event reporting. It relies on the agent-cdn host for updates and diagnostic uploads. All three need to be reachable on TCP 443, and we recommend excluding them from TLS/SSL inspection. See Network Connectivity for the full list of hostnames by region and steps to check connectivity.

​
Prerequisites and known compatibility issues

Before deploying at scale, confirm that the Visual C++ Redistributable requirement is met, that the three required endpoints for your region are reachable, and that any SASE or Application Control solution is configured to allow the Origin agent to operate correctly. The prerequisites article covers all of these requirements in one place.