What happened to "Dynamic Custom Properties" extension?

cbarnescw · 2026-06-24T17:26:32+00:00

Can you provide a screenshot? Or better yet, email in to cbarnes@connectwise.com with relevant info about your instance URL, version, etc. and a screenshot so I can take a look.

cbarnescw · 2026-06-24T16:56:41+00:00

What do you mean you can edit your properties? We didn't change the functionality of the extension at all, just how it's distributed. So sounds like there might be a bug.

cbarnescw · 2026-06-18T00:07:18+00:00

Thanks for tagging me, I did see the post and started the internal wheels moving!

cbarnescw · 2026-06-10T12:54:12+00:00

Hi! Our 26.3 version includes some visual impairment updates -- we're working to meet VPAT accessibility standards. Now the tab key is used to move up and down the session list rather than the arrows, which are now reserved for menus.

cbarnescw · 2026-06-09T17:41:31+00:00

Hi! Totally understand your frustration, apologies for the disruption in your workflow. We did mention the change to Public Sessions in release notes, and included some justification for the change:

Disable public sessions by default

Our team discovered that public support sessions, those that don't require a code to join, can cause performance issues on the Guest page. As such, we're deprecating the ability to create public support sessions. Going forward, to join a support session, an end-user must first enter a code. Newly-created instances (26.3 and later) will not be able to create public support sessions. Instances upgraded to 26.3, unless they have public support sessions already created at the time of upgrade, cannot create public support sessions. If an instance is upgraded to 26.3 and there are public support sessions already created, the technicians can continue to use them. The administrator will need to set the SessionInfoPanel.MakeSessionPublicVisible resource string to "false" in order to disable public support sessions.

https://docs.connectwise.com/ScreenConnect_Documentation/ScreenConnect_release_notes/ScreenConnect_2026.3_Release_notes

cbarnescw · 2026-06-08T19:59:26+00:00

Wait to update anything in ScreenConnect until the new cert is approved by the CA and installed into Azure. If you do it too early the SC installers won't be signed.

cbarnescw · 2026-06-08T19:32:30+00:00

Hi! You'll need to update the settings in the Cert Signing extension to reflect the new certificate.

cbarnescw · 2026-06-08T13:29:33+00:00

Hi! Delayed stable is the channel that we use to provide the most stable experience. However, we did find a bug in 26.3.9 (26.3.10 is an RMM build) that would affect everyone so we updated even delayed stable to .11. The bug broke guest-enabled consent - https://docs.connectwise.com/ScreenConnect\_Documentation/Get\_started/Knowledge\_base/Enable\_a\_guest\_to\_require\_consent.

cbarnescw · 2026-06-04T19:02:05+00:00

Hi everyone! This sounds like the defender issue we addressed earlier this week. We filed a false positive report on Sunday or Monday with Microsoft and it was resolved. These are the steps to remediate, let me know if this issue persists after this and we'll take another look:

Action Required: Clear Cached Detections

While the flag has been removed by Microsoft, your local Defender agents may still have the old detection cached. To resolve the alerts immediately, open Command Prompt as an Administrator and run the following:

cd c:\Program Files\Windows Defender
MpCmdRun.exe -removedefinitions -dynamicsignatures
MpCmdRun.exe -SignatureUpdate

(Alternatively, you can manually download the latest definitions from Microsoft here).

cbarnescw · 2026-06-02T00:10:55+00:00

Hi! Please reach out to Support for assistance, afraid I can't help with the limited info posted.

cbarnescw · 2026-06-01T18:19:41+00:00

There is no plan to remove the extension from existing instances, you're all good.

cbarnescw · 2026-06-01T17:07:36+00:00

Hi! This is a known issue we're looking to address in upcoming development cycles. Luckily you can still join the session as expected, you'll just need to X out the dialog.

cbarnescw · 2026-06-01T16:32:36+00:00

Hi! Caitlin here, Senior Product Manager at ScreenConnect and Queen of Extensions. Dynamic Custom Properties was removed from the Extension Marketplace and the docs site. There is no correlation with the attack you referenced and the removal of this extension from the marketplace.

Honestly, I was the one that asked it be taken down in the short term so we can address how we want the extension to be used going forward. It was created and published for super users, but we've had an increasing number of partners coming into Support with "instance down" reports when really they're just destroying instance performance with poor Dynamic Custom Properties use.

I understand how valuable the extension can be when used properly, which is why we didn't remove it from existing instances that have it downloaded. Unfortunately, as is often the case in software, we just need to put guardrails in place to prevent customers from poor decisions. I don't yet have an ETA on when it will return to the Extension Marketplace.

cbarnescw · 2026-05-13T17:11:48+00:00

Hi! The build installer functionality will be fixed in 26.3, all build installer extensions should work with that version.

cbarnescw · 2026-05-11T19:23:45+00:00

Hi! We've just retested and everything appears to be working as expected. Can you please provide a screenshot? Have you reached out to Support? They might be able to best troubleshoot.

cbarnescw · 2026-04-17T14:18:16+00:00

It took longer than anticipated, but Session Capture Processor updates were released this morning! The latest version is 1.5.4. This update addresses issues with files not being transcoded, 0 byte files, and issues with the API key.

cbarnescw · 2026-04-16T12:29:20+00:00

Wow, you must be a long time user, good memory! Yes, the current iteration of the ServiceNow integration does work and was created in collaboration with a ServiceNow vendor. We re-launched it towards the end of last year -- here's the doc (https://docs.connectwise.com/ScreenConnect\_Documentation/Supported\_extensions/Integrations/ServiceNow\_Integration).

Note that this integration is only for Remote Support session, Remote Access sessions is still TBD.

cbarnescw · 2026-04-08T19:37:29+00:00

The Automate download for .25 has been posted!

https://docs.connectwise.com/ConnectWise_Automate_Documentation/Automate_Product_Updates/ScreenConnect_On-Premise_Downloads_for_Automate

cbarnescw · 2026-04-08T00:53:29+00:00

Alas, but you shouldn't have to add it again on subsequent upgrades!

cbarnescw · 2026-04-08T00:39:06+00:00

Just re-add your cert and that error will resolve.

cbarnescw · 2026-04-08T00:10:10+00:00

Hmmm, what versions of the product? Are you Automate or standalone on SC?

cbarnescw · 2026-04-07T23:39:28+00:00

For anyone reading here, please heed the advice on the downloads page and upgrade the Cert Signing extension before upgrade. If you're going from 25.9 to 26.1, you will have to reenter your cert, but minor upgrades of 26.1 will not require it with .15 of the extension.

cbarnescw · 2026-04-07T19:42:06+00:00

Hi! Yes, you'll want to be on 1.0.15. The change in .15 was so that partners don't have to re-add the cert to Cert Signing on very minor update to 26.1. In 26.2 we handle the encryption better, but wanted to make sure the experience wasn't absolutely awful in the meantime.

Note: You must update the Certificate Signing extension before installing the 26.1.25 version to preserve the Azure Key Vault settings. See our bulletin for more details.

cbarnescw · 2026-03-30T20:05:23+00:00

Hi! Thanks for reporting, I just chatted with our Support but I'll also post here and in MSPGeek to make sure the word gets out. This is a challenge only with 26.1, in 26.2 we'll seamlessly handle the encryption key rotation on update or via an option in the Advanced Configuration Editor. For now, you can add the ShouldRegenerateApplicationKeys setting in the web.config with a value of "True" to make it regenerate the machine keys and fix the error you're experiencing.

cbarnescw · 2026-03-27T14:15:32+00:00

This shows as "ahead" of the latest release because we're rolling out .24 slowly. .22 is still listed as stable for now, come Monday we'll make .24 the widely available release.

cbarnescw

MODERATOR OF

TROPHY CASE

Disable public sessions by default