ConnectWise ScreenConnect

ConnectWise ScreenConnect is commercial remote support software for MSPs, internal help desks and IT departments that need both quick attended sessions and permanent unattended access to managed machines. Most people searching for a ScreenConnect download are either technicians setting up an instance or end users who were sent a session link; this page covers both sides.

ScreenConnect runs as a cloud service hosted by ConnectWise or as an on-premises server you install yourself. The product was sold for several years as ConnectWise Control and has since returned to the ScreenConnect name. It is a paid product; there is no free edition.

ScreenConnect at a glance

What it does

• Support sessions for one-off attended help: the user joins with a code or link and runs a small guest client.
• Access sessions for unattended machines: a persistent access agent keeps the device available in your console.
• Meeting sessions for presenting your screen to several participants.
• Backstage mode on Windows guests, so you can open a command prompt, Task Manager or registry tools in the background without interrupting the user.
• Toolbox of approved utilities and a Commands tab for running shell commands on the remote machine.
• File transfer, clipboard, multi-monitor control, and reboots (including into Safe Mode with networking) that reconnect automatically.
• Role-based permissions, audit logs and optional session video recording (extended auditing).
• Extensions and integrations with PSA/RMM tools, including other ConnectWise products.

How IT teams use it

Start an attended support session

1. In the host web page open Support and create a new session with a name or code.
2. Send the user the invitation link or ask them to enter the code on your instance’s guest page.
3. The user runs the guest client and approves the connection; your host client opens the session.
4. When finished, end the session so the temporary client removes itself.

Roll out unattended access agents

1. Go to Access and click Build and create an installer (MSI for Windows, PKG for macOS, DEB, RPM or SH for Linux) with the Company, Site, Department and Device Type custom properties filled in, so devices land in the right session groups.
2. Deploy the MSI with your software distribution tool, for example:

msiexec /i "ScreenConnect.ClientSetup.msi" /qn

3. Check that devices appear under Access, then restrict who can join them with roles rather than giving every technician full control.

Patch an on-premises server

1. Read the security bulletins on the ConnectWise Trust Center before each upgrade.
2. Back up the installation folder (C:Program Files (x86)ScreenConnect) including web.config and the App_Data databases.
3. Run the new server installer, check Administration > Status, and then update host clients and access agents.

Install and first run

Cloud. ConnectWise hosts and patches the server; you sign in to your instance and start building installers. Cloud instances were upgraded automatically to the fixed build after the September 2026 bulletin.

On-premises server. Supported on 64-bit Windows 10, Windows 11 and Windows Server 2016, 2019, 2022 and 2025, with .NET Framework 4.7.2 or later. Inbound ports are TCP 8040 (web server) and TCP 8041 (relay); the server also needs outbound HTTPS to license.screenconnect.com for licence validation. ConnectWise suggests roughly 2 GB of RAM per 10 concurrent sessions, an SSD, and 10–15 GB of disk, more if you record sessions. On-premises partners must now sign their own access installers with a code-signing certificate that can be used with Azure Key Vault; unsigned clients are likely to be flagged by endpoint protection.

Host client. Windows 10/11 and Server 2016 or later, macOS 10.12 or later (only the current and previous macOS releases are guaranteed), and common Linux distributions.

Guest client. Windows 10/11 and Server 2016–2025, macOS 12.7.1 or later, and Linux with a Java runtime (JRE 1.9+) and a desktop such as GNOME, KDE Plasma or MATE. Desktops using XWayland may show a black screen. On macOS the user must grant Screen Recording and Accessibility in Privacy & Security, or you will see the screen but not be able to control it.

Limitations

• No free edition and no standalone public installer: clients are generated by each instance.
• On-premises servers run only on Windows, and you are responsible for patching them promptly.
• Security history matters: in February 2024 an authentication bypass (CVE-2024-1709) was widely exploited on unpatched on-premises servers, and in September 2026 version 26.6.5 fixed CVE-2026-84869 (CVSS 9.9), which allowed files to be transferred and run through an active session without authorisation. ConnectWise rated it Priority 1; on-premises partners had to update manually or disable the TransferFiles permission until they could.
• Attackers also use legitimate ScreenConnect instances in phishing; tell users to accept sessions only from your own instance.
• Linux guests rely on Java and can struggle on Wayland.

ScreenConnect vs alternatives

TeamViewer is easier for one-off sessions and has wider consumer recognition, but MSP-style unattended management needs its paid business tiers. LogMeIn Resolve (formerly GoTo Resolve) combines remote support with ticketing and has a free plan. If you want something free and self-hosted, RustDesk with your own server or MeshCentral cover remote control and unattended access, though without ScreenConnect’s toolbox, backstage mode and PSA integrations.

FAQ

Is ScreenConnect free?

No. ScreenConnect is a commercial product for cloud or on-premises use. ConnectWise offers a trial, but there is no permanently free edition.

Where do I get the ScreenConnect client download?

Client installers are built by your ScreenConnect instance. Technicians create them on the Access page, and end users receive a session link or code from their support provider.

Does ScreenConnect work on Mac?

Yes. There are host and guest clients for macOS. The guest needs Screen Recording and Accessibility permissions granted in System Settings before you can view and control the Mac.

How do I remove the ScreenConnect client?

A technician can end and uninstall the session from the host page. Users can also uninstall the “ScreenConnect Client” entry from installed apps; if you did not install it yourself, ask your IT provider first.

What was the ScreenConnect vulnerability?

The most recent critical one, CVE-2026-84869 (CVSS 9.9), was fixed in 26.6.5 on 8 September 2026. Earlier, CVE-2024-1709 was mass-exploited in 2024. Keep on-premises servers on the latest stable build.

ScreenConnect vs TeamViewer: which is better for an MSP?

ScreenConnect is built around MSP workflows: unattended agents with custom properties, backstage tools, roles and self-hosting. TeamViewer is quicker to start with and has broader device support, but neither is free for business use.

Is ConnectWise Control the same as ScreenConnect?

Yes. ConnectWise Control was the product’s name for several years; it is now called ConnectWise ScreenConnect again.

Last checked against official sources: 1 October 2026 (developer website: screenconnect.com). Versions and licence terms change — confirm on the developer's site before deploying in production.