Introduction

Getting a Windows device into Level takes one install and a few seconds. The Level agent is a lightweight background service that checks in with your account and makes every feature — remote control, monitoring, automation, patch management — available for that device.

This article covers all four Windows install methods, plus advanced parameters for support scenarios.

⚙️ PREREQUISITES

A Level account with permission to add devices
Local administrator rights on the target Windows device
Windows 10+ or Windows Server 2016+ (64-bit)
PowerShell v4+ (for command-based installs)

🎬 VIDEO

Windows Install

Click Add new device in the top-right corner of the Device Listing page. The install modal opens and defaults to Windows.

Selecting a Device Group (Optional)

Before copying your install command or downloading the installer, you can assign the device directly to a group. Click Select a device group, search or browse your group hierarchy, and select one.

The install key embedded in your install command updates automatically to reflect the selected group. If you skip this, the device lands in Ungrouped — you can move it later.

💡 TIP: Assigning a group at install time saves a step post-enrollment, especially if you're deploying to many devices at once. The device picks up all group-level automations and permissions immediately on first check-in.

The Install Key

Every install command and the MSI installer prompt both use an install key — a short token visible in the modal that links new devices to your Level account.

The install key is scoped narrowly by design. If it were ever exposed:

It can't be used to access your account, existing devices, or the Level API
The only thing it can do is add new devices to your account (which then report to you with full remote access)

If you believe your install key has been compromised, contact Level support to rotate it.

ℹ️ NOTE: The install key reflects your selection in real time. Without a group selected, it contains just your account identifier. Select a group and the group's ID is appended — so the key that gets embedded in your install command or shown in the MSI prompt already encodes where the device will land.

Install Methods

The modal has four tabs. Pick the one that fits your workflow.

Installer (MSI)

The standard GUI installer. Download the file, run it, paste in the install key when prompted. Best for one-off manual installs or anyone who wants to see the install wizard.

In the modal, select the Installer tab.
Optionally select a device group.
Click Download installer to download the MSI.
Copy the install key using the copy icon next to the key field.
Run the downloaded MSI and follow the setup wizard.
Enter the install key when prompted.

The device shows up in your Device Listing within 5–10 seconds of the install completing.

One-Line Command

A PowerShell one-liner that downloads and installs the agent silently. Good for remote deployment or when you already have a remote shell open.

In the modal, select the One-line command tab.
Optionally select a device group.
Copy the generated command.
On the target device, open PowerShell as Administrator.
Paste and run the command.

The command downloads the MSI, installs silently, and links the device to your account using the embedded install key — all in one step.

Silent Install

Same PowerShell command as the one-line install, but with /qn appended to the msiexec arguments. This suppresses all installer UI output, making it suitable for scripted deployment where you don't want any dialogs appearing on the target device.

In the modal, select the Silent install tab.
Optionally select a device group.
Copy the generated command.
Run it as Administrator on the target device (or via your deployment tool).

ℹ️ NOTE: Silent install produces no visible output on the target device. The device still appears in Level within 5–10 seconds of completion — that's the easiest way to confirm it worked.

Install via exe (Advanced)

An alternative installer that shows more verbose output during the install process. Primarily useful for troubleshooting failed installs, since you can see exactly where it stalls.

This option isn't shown in the modal by default. Access it by navigating to:

__PRESERVE_CODE_1__

That URL opens the install modal with a fourth tab: Install via exe.

The command downloads install_level.exe from Level's servers and runs it directly. Because it's not a silent installer, you see the full install output in the terminal — which makes it much easier to spot errors.

ℹ️ NOTE: The exe installer is primarily a support tool. Most deployments don't need it. Level support may direct you here when troubleshooting a device that isn't checking in after a standard install.

Force Install (Advanced)

If Level is already partially installed on a device — or a previous install left behind stale files — a standard install may fail silently. The forceInstall parameter forces a clean overwrite of any existing Level install.

ℹ️ NOTE: Both installer=exe and forceInstall=true are URL parameters intended for support scenarios. Level support may link you directly to a pre-configured modal URL when troubleshooting.

Add it to the URL before opening the modal:

__PRESERVE_CODE_6__

This adds LEVEL_FORCE_INSTALL=TRUE to the generated one-line command, silent install command, and exe install command. It doesn't affect the MSI installer tab.

You can combine it with the exe installer for maximum verbosity during a forced reinstall:

__PRESERVE_CODE_8__

⚠️ WARNING: Force install overwrites any existing Level agent configuration on the device. Only use this when a standard install fails or Level support directs you to.

AV/EDR Exclusions

Some antivirus and EDR tools flag Level as a threat. This is a false positive — Level is not malware — but it can block installation or cause the agent to stop functioning after install.

Before deploying to a new environment, add Level to your exclusions.

ℹ️ NOTE: The install modal includes a reminder about this. If you see the device go offline after a successful install, an AV/EDR tool is the most likely cause.

For exclusion paths, certificate details, and tool-specific instructions (including Defender), see AV/EDR False Detections. Level also publishes a detailed breakdown of why EDR tools flag RMM agents at level.io/blog/edrs-distrust-rmms-and-thats-ok.

System Requirements

Requirement	Details
OS	Windows 10+, Windows Server 2016+
Architecture	64-bit only
PowerShell	v4+ (for command-based installs)
Desktop Experience	Required for Windows Server 2012 only

⚠️ WARNING: Windows 7, 8, 8.1, Server 2008, and Server 2012 will no longer be supported after May 4, 2026.

After Install

The device appears in your Device Listing within 5–10 seconds. It'll show its group assignment (or Ungrouped), online status, and start populating hardware inventory within a few minutes.

If the device doesn't appear, see Offline Troubleshooting for next steps.

FAQ

What happens if my install key is leaked or compromised? The install key can't be used to access your account, your existing devices, or the Level API. The only risk is that someone could use it to add devices to your account — giving you remote access to those devices, not them access to yours. If you think the key has been exposed, contact Level support to rotate it.
Can I send technicians or end users an email link to install the agent themselves? No. Level doesn't have an email-based install flow. The agent requires local administrator rights to install, which most end users don't have — so email-driven self-installs aren't reliable. Installation needs to be performed by someone with local admin access, either manually or via a deployment tool.
How do I install Level on a lot of Windows devices at once? Use the one-line command or silent install method with your existing deployment tooling (Intune, GPO, PDQ, etc.), or see MDM / Policy Install for Level-specific guides. The silent install is designed for unattended mass deployment.
The device installed but isn't showing up in Level — what's wrong? Wait 10–15 seconds and refresh. If it still doesn't appear, an AV/EDR tool is the most common culprit — it may have blocked or quarantined the agent during or after install. See AV/EDR False Detections and Offline Troubleshooting.
Can I install Level without specifying a group upfront? Yes. Skip the group selector in the modal and the device lands in Ungrouped. You can assign it to a group from the Device Listing afterward.
What's the difference between the silent install and the one-line command? Both are PowerShell one-liners. Silent install adds /qn to suppress all UI output, making it better suited for automated or scripted deployment. The one-line command may show brief progress output during install.
When would I need the force install option? When a previous Level install left behind files or registry entries that block a fresh install. This usually surfaces as an install that appears to succeed but the device never checks in. Level support will typically direct you to this if it's the right fix.
Who can add devices to Level? Any technician with permission to manage the target device group — or any technician if deploying to Ungrouped. Check Workspace → Permissions if you don't see the Add new device button.