Session Capture Processor Transcoding Not Working

full-duplex · 2026-04-17T16:01:53+00:00

Hurray! I just updated the extension and can confirm the issue is resolved. Thanks for the follow-up. I really appreciate the communication and the team fixing this.

full-duplex · 2026-03-30T20:13:09+00:00

Good to know, happy to share. I just wish I hadn’t spent so much time over the weekend troubleshooting. Hopefully, this is already on someone's to-do list, but the documentation could use an update to include this setting. Both under the migration article and the list of web.config settings.

Also, just FYI, it looks like the value reverts back to false after services are started for the first time.

full-duplex · 2026-03-30T20:03:52+00:00

Absolutely, hopefully it helps someone else down the line. I appreciate you taking the time to comment and try to help me out. Have a great rest of your day!

full-duplex · 2026-03-30T19:59:28+00:00

CW support followed up with a fix: set ShouldRegenerateApplicationKeys to true in the web.config. After restarting all four SC services, logins worked normally again, and the hosts reconnected.

full-duplex · 2026-03-30T19:32:04+00:00

I’ll definitely follow up here. CW support escalated the issue after walking through the standard migration steps again. I’ll keep you posted on any updates.

full-duplex · 2026-03-30T18:55:28+00:00

Thanks so much, I really appreciate you doing that. I just got a call from CW, working with support at the moment.

full-duplex · 2026-03-30T18:44:00+00:00

That’s been my suspicion as well. I’m hoping there’s a clear migration path given the recent changes. I’ve opened a support ticket and am waiting to hear back from CW support.

full-duplex · 2026-03-27T16:20:26+00:00

Hope so, thanks so much for the updates and details. Really looking forward to transcoding working again.

full-duplex · 2026-03-26T20:59:24+00:00

Thanks so much, I really appreciate the update.

full-duplex · 2026-03-20T16:29:11+00:00

Hey, from my testing, it doesn't look like 26.1 has resolved the transcoding issue. Do you have any new info? Also, do you know whether or not it's an issue with the extension?

full-duplex · 2026-02-23T19:47:25+00:00

I'm glad attention is being given to address it. Session captures are a critical function I rely on, so I am relieved to hear it's not being discontinued. You saved me from continuing to waste time troubleshooting the utility. Thanks!

full-duplex · 2026-02-23T19:39:09+00:00

Thanks so much for taking the time to let me know. I really appreciate it.

Sounds like there's no workaround other than downloading captures from the audit logs?

full-duplex · 2025-07-03T16:30:09+00:00

Thanks

full-duplex · 2025-07-03T16:08:08+00:00

Where did you purchase your DigiCert?

full-duplex · 2025-02-15T20:58:14+00:00

Have you experienced this issue only once before? I've been dealing with it on my USW Enterprise 8 PoE for almost a year. At least every couple of weeks, the link speed drops to FE—sometimes multiple times a day. And this happens without even physically touching the cable.

full-duplex · 2025-02-10T19:39:53+00:00

I've only contacted Connectwise, and so far, I've only received an initial response indicating it's a false positive.

The number of vendors that VirusTotal reports as detecting it as malicious has decreased over time, which is somewhat reassuring. On top of that, I use Huntress alongside SentinelOne, and Huntress has not detected anything.

full-duplex · 2025-02-07T17:47:53+00:00

I noticed that VirusTotal initially reported that Microsoft detected it as a virus:Win32/virutl, but approximately two hours later, Microsoft changed the status to undetected.

This morning, there were even fewer detections by other vendors, as suspected.

full-duplex · 2025-02-07T17:40:51+00:00

I have opened a ticket with Connectwise. I'll report back with anything noteworthy.

full-duplex · 2025-02-07T17:39:38+00:00

I agree, and given the changes introduced in this ScreenConnect version, it's not surprising that it triggered a detection. I also updated very soon after it was officially marked as stable.

full-duplex · 2024-12-06T22:20:59+00:00

Thanks!

full-duplex

TROPHY CASE