Welcome to the ConnectWise Control Bug Report Portal

If you do not have an account, click "Sign in/ Sign up" to get started.


  • Search for an existing bug report before adding your own. This helps us prevent duplicate entries and improve bug tracking.
  • If you find a matching bug report, give it a thumbs up and throw in a comment with more details about the problem.
  • If you can't find a request for an item you need, create your own bug report. Provide as many details as you can, especially:
    • Software version of the server, host client, and guest client
    • Operating systems affected
    • Any error messages
    • Screenshots


  • No spam, advertising, or self-promotion.
  • No offensive posts, links, or images.
  • Only one request per post.
  • Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.

Thank you for sharing your thoughts with us!


The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

aodinfo 8 months ago updated by Kevin G 1 month ago 62
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Known issue

Portal not responding

Phil K 1 year ago updated by Caitlin M Barnes (Product Manager) 5 months ago 518

Hi All, 

A public pre-release of 20.2 Linux is available for download here. Please check out our Linux specific output stream for details on that release. We also have a separate page for Linux bug reports. This thread will now be closed. 


Session Window opens tiny on 4K Monitor

Karama 1 year ago updated by Eric Davis 9 months ago 20

Since upgrade to 19.5 when i open a client session the session Window is tiny and i have to resize it larger to make it usable.  When i close the session and re-open it opens tiny again, it does this no matter what computer i click on and start a session.  Nothing has changed on my computer.  Wasn't doing this before upgrade to 19.5


Complicated process required to control macOS 10.14 (Mojave) clients

sgtpoliteness 2 years ago updated by David Geddes 2 years ago 75

Setting up Connectwise Control on macOS 10.14 (Mojave) clients is difficult and requires many extra steps as compared with previous macOS versions.

To set up Connectwise  Control on a brand new install of macOS 10.14, these steps are required:

  1. Install .pkg as normal (this allow remote viewing but no control)
  2. Reboot macOS computer
  3. After reboot, attempt remote control, this will prompt a popup asking if the macOS computer wants to allow
  4. Click "Open System Preferences"
  5. Click lock (bottom left), enter computer password
  6. Check box next to "screnconnect-xxxxxxxxx"
  7. Reboot
  8. Remote control again works

In cases where remote control was working on a macOS 10.14 computer where Connectwise upgraded from 6.6 to 6.7, connectwise software must first be removed using these steps:

  1. From Access website, select session > End > Uninstall and end
  2. On macOS computer, open system preferences > accessibility
  3. Click lock (bottom left), enter computer password
  4. select "screenconnect-xxxxxxxxx", click - to remove
  5. Reboot
  6. Install using steps above

I believe this complexity is due in part to some sort of increased system security in the new macOS.  Still, it seems much of this could be streamlined.


Machine preview showing other devices

Poynter 3 years ago updated by SR Smith 3 years ago 41

On access page other machines are being displayed in the preview window. These cycle through until the correct machine is shown. The wrong organisation name is also displayed.

When generating a new adhoc support session, a preview window appears before you can choose the session settings. 



6.9.21027.6898 Client not compatible with Server 2003

T Stine 2 years ago updated by Eric Davis 2 years ago 22

The Host is greeted with a grey screen when attempting to connect to a 2003 server.

Last known working version: 6.8.20124.6845

Eric Davis 2 years ago

This should be fixed in the latest 6.9 release. Please let us know if there are still any issues.



6.9.20755.6879 - Guests Disappear until restarting services

ben 2 years ago updated by Eric Davis 2 years ago 64

Since updating to 6.9.20755.6879, we noticed that some guests disappear until restarting the ScreenConnect Web Server and ScreenConnect Relay services.

Known issue

TLS 1.3 seems to breaks screenconnect when using ssl on mono

stylnchris 3 years ago updated by DaveE 1 year ago 136

TLS 1.3 seems to breaks screenconnect  when using ssl on mono.

Disabling it in chrome/firefox seems to be a quick fix, however at some point im guessing it would be better for mono to support TLS 1.3. 

Version 6.5.16479.6613

Under review

Server 2019 VM not refreshing display unless the console is live

TheScottyQ 2 years ago updated by Bill Townsend 8 months ago 13

We have a 2019 Clustered HyperV environment where the guests do not show a live display unless the console is live from the HOST 

Keys and Mouse seem to be being passed through because if we send a CTRL+ALT+DEL to the guest and refresh the screenshot you can see it has been passed through to the guest, the display on the session just does not refresh for the host 

Screenconnect Version - 19.2.24707.7131 (not listed below) 


SAML fails due to too many groups

MartinT 2 years ago updated 9 months ago 6

Environment to reproduce:

Have a SAML server setup and working.

Using ADFS as a backend server.


SAML works for all users with other applications, like ITGlue.

SAML works for most users using Control.

Have user who is a member of 170 AD groups. 


User can't login with SAML to Control. Just acts like he never pushed the button. Address bar URL ends with errorcode 6 after he clicks login with SAML.

SAML reply when replicating the issue comes through as expected.


Remove user from 40 groups and now it works expected.


SAML fails when user a member of too many groups