Edge Chromium protocol handler always open these types of links in the associated app

I’ve moved my daily browsing habits to the new Edge that is based on Chromium. I have been using it since the very first release. I am now using the stable beta version.

I noticed about a month or so ago that whenever I tried connecting to a Screenconnect session, the protocol handler would always ask me: This site is trying to open ScreenConnect Client, but it would not have the checkbox to allow me to always open these types of links in the associated app.

Edge Chromium protocol handler with no Always open these types of links in the associated app option

I finally decided to try and figure out if there was an option within Edge to enable this again. After checking the site permissions area, I could not find a setting that would allow this check-box to return.

I started searching the web, and through all the BS Google search results, don’t even get me started with that, I found a few other threads where people were reporting the same thing.

It appears that as of Chrome 77 which Edge Chromium is based on, they removed the option to always open these types of links in the associated app.

Their reasoning is because there was no way to undo the always remember option, they decided it was insecure and a security risk, therefore, they removed it completely.

Here is the thread I found: https://support.google.com/chrome/thread/14194567?hl=en

In the thread, there is a workaround. It entails modifying the preferences file in your default profile.

Hi All, there is a way around this, you can insert a record into the preferences file
found in C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default
The file “Preferences”  contains JSON serttings, our example is for a Web Client Print handler, so just added the below:

You must close all instances of chrome including any running processes before you do this or chrome will overwrite the file and get rid of your changes.

And it works.
NB: you’ll have to check your own scheme names to add.
Hope this helps.


I tried modifying the preferences file for the dev version of Edge that I am running alongside the beta and Canary. I went to: %HOMEPATH%\AppData\Local\Microsoft\Edge Dev\User Data\Default and tried editing the preferences file found there. When I run Edge, I get an error message saying: Profile error – Your preferences file isn’t valid, or was corrupted. We couldn’t recover your settings. It changes the preferences file to preferences.bad and then creates a new Preferences file.

According to this ConnectWise technical bulletin: https://docs.connectwise.com/ConnectWise_Control_Documentation/Technical_support_bulletins/Constant_prompt_to_open_ScreenConnect_Client_in_Chrome, you should be able to add the following: “protocol_handler”: {“excluded_schemes”: {“sc-xxxxxxxxxxxxx”: false}}, to the Preferences file, and it should always remember your choice that you would like to allow this app to run without having click on Open.

I tried it multiple times, placing the code in different areas, making sure the formatting was right. It never worked. I am going to assume that Microsoft block this change. I really don’t know much about how you can modify open-source browsers, but I’d imagine, most if not all that are based on the same source, follow the same guidelines or standards.

If you figure out how to force the new Edge browser to always allow specific protocol handlers to run instead of having to click on Open all the time, please leave me a comment.

8 Replies to “Edge Chromium protocol handler always open these types of links in the associated app”

  1. Psssst, try using the following registry edits to enable the “always open links of this type…” to circumvent the security policy. As always use common sense when disabling security policies…

    For Edge:

    For Chrome:

    For Chromium:

    More on: https://bugs.chromium.org/p/chromium/issues/detail?id=1013598

  2. I was able to get this to work in Edge as of Jan 30 2020. I’ve changed the preferences file to include the excluded_schemes line, but there was another field that had to be deleted that kept resetting the file back. I forget what it was but if you send me a copy of your file from {“prompt_seed” on wards, I can re-identify the entry that needs to be removed. Sorry I can’t be of better help without seeing the file because I was just trying various methods while performing research online.

    For the record, I’m now getting screen connect to open without the prompt in Microsoft Edge after modifying the preferences file.

  3. Here’s the real fix to prevent the protocol extension popup. Whitelist the URL “sc-/*”. The ConnectWise Control Instance ID can be found on the folder name where Control/ScreenConnect has been installed (C:\Program Files (x86)\ScreenConnect Client ().

    The URL Whitelist for Chrome (and Edge Chromium) can be set via GPO at:
    Computer > Policies > Administrative Templates > Google > Google Chrome > Allow access to a list of URLs
    Computer > Policies > Administrative Templates > Microsoft Edge > Define a list of allowed URLs

    Enable the setting and add sc-://* to the URL list.

    Or via Registry at:
    Chrome: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\URLWhitelist
    Edge: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\URLAllowlist

    Registry value:
    String Name: (Example: 10)
    String Value: sc-://* (Example: sc-ehk3a94963acb3a3://*)

    Then fully exit the Chrome browser (close it from the system tray if enabled). No more ScreenConnect prompt.

    1. My comment got sanitized because I used chevrons.
      sc-://* = sc-[ScreenConnect Instance ID]/*

      C:\Program Files (x86)\ScreenConnect Client () = C:\Program Files (x86)\ScreenConnect Client ([ScreenConnect Instance ID])

      Hope that ends up in the comments correctly.

      1. Thank you, everyone! I was able to get it to work via the registry. However, I work with two different instances of Screen Connect and one instance will not kick off the checkbox even with the registry edit. Any ideas?

Leave a Reply to Thomas Cook Cancel reply

Your email address will not be published. Required fields are marked *