Screen share shows error when selecting window / monitor source

TeamSpeak 6 Client Suggestions and Feedback
1

Hello there.

I’m actually testing the last update of the server for TS6.
Everything is working so far except for one thing.
I can stream my camera (it’s OBS camera) but whenever I click on an app in the list or monitor it say “error”. (no message except one line in the client log, only the sound)
At worst I can simply open OBS and decide to display the app there as a camera on TS6 client.

Is there a requirement I missed or a settings somewhere? I’m admin of the server.
Edit: More info. I’m on W11 to try it in Local on my own pc. Not on a server yet.

Thank you.

2

Currently the client handles all of the screen sharing, meaning it should not be the servers fault.

Could you also provide your system specs and a screenshot of the error message?
And a fresh pair of logs would be useful:

2 Likes
3 
[2025-12-10 19:54:01.464] [info] Notifications_Windows ctor
[2025-12-10 19:54:01.478] [info] TeamSpeak Client 6.0.0-beta3.3 (2025-12-09 10:34:50)
[2025-12-10 19:54:01.478] [info] SystemInformation: Windows 11 (26200) x64 (AMD or Intel) Binary: 64bit
[2025-12-10 19:54:02.007] [warning] sync_event, account status change: 2
[2025-12-10 19:54:03.008] [info] Hot Reload!
[2025-12-10 19:54:03.244] [info] Initialized with 8 channels in 32bit, 48kHz. - Haut-parleurs (CORSAIR HS80 RGB USB Gaming Headset)
[2025-12-10 19:54:03.245] [info] set device for AudioBridge.
[2025-12-10 19:54:04.875] [info] Initialized with 1 channels in 32bit, 48kHz. - Microphone (CORSAIR HS80 RGB USB Gaming Headset)
[2025-12-10 19:54:04.876] [info] Connecting to localhost:9987
[2025-12-10 19:54:04.876] [info] Trying to resolve to localhost:9987
[2025-12-10 19:54:04.880] [info] A/AAAA DNS resolve successful, "localhost" =(h: 127.0.0.1 p:0)
[2025-12-10 19:54:04.881] [info] Connecting to resolved address 127.0.0.1:9987
[2025-12-10 19:54:04.884] [info] server sent ciphers:35
[2025-12-10 19:54:04.884] [info] Selected cipher:1
[2025-12-10 19:54:09.088] [error] Failed to create DesktopCapturer
[2025-12-10 19:54:16.545] [error] Failed to create DesktopCapturer
[2025-12-10 19:54:21.327] [warning] Terminating RPC channel
[2025-12-10 19:54:21.327] [warning] RPC channel terminated
[2025-12-10 19:54:21.327] [warning] Terminating RPC channel
[2025-12-10 19:54:21.327] [warning] RPC channel terminated

Nothing else worth noting, it repeat the last 2 lines until I quit.
About my spec:
Windows11 pro 25h2 build 26200.7462
AMD ryzen 9 7950X3D
RTX 4080
All drivers are up to date.

If you need more information let me know.

Thank you.

4

I’ve reached out to our developers, and in this case, the logs you provided are insufficient.

However this is not your fault, this is not logged on the client side. For the next update, we have added more logging in this area, which we plan to release next week. We would then like to get new logs from you. :slight_smile:

2 Likes
5

Then I’ll wait for it.
I will either reply again with the new log or update my post if I can fix it before the said client’s update.

2 Likes
6

Just wanna mention that the update is now out. Due to holidays we’ve fast tracked it.

3 Likes
7 
[2025-12-11 20:52:25.103] [info] Notifications_Windows ctor
[2025-12-11 20:52:25.116] [info] TeamSpeak Client 6.0.0-beta3.4 (2025-12-11 14:15:03)
[2025-12-11 20:52:25.116] [info] SystemInformation: Windows 11 (26200) x64 (AMD or Intel) Binary: 64bit
[2025-12-11 20:52:25.645] [warning] sync_event, account status change: 2
[2025-12-11 20:52:25.757] [info] Hot Reload!
[2025-12-11 20:52:26.035] [info] Initialized with 8 channels in 32bit, 48kHz. - Haut-parleurs (CORSAIR HS80 RGB USB Gaming Headset)
[2025-12-11 20:52:26.036] [info] set device for AudioBridge.
[2025-12-11 20:52:28.970] [info] Initialized with 1 channels in 32bit, 48kHz. - Microphone (CORSAIR HS80 RGB USB Gaming Headset)
[2025-12-11 20:52:33.308] [info] Connecting to localhost:9987
[2025-12-11 20:52:33.308] [info] Trying to resolve to localhost:9987
[2025-12-11 20:52:33.313] [info] A/AAAA DNS resolve successful, "localhost" =(h: 127.0.0.1 p:0)
[2025-12-11 20:52:33.313] [info] Connecting to resolved address 127.0.0.1:9987
[2025-12-11 20:52:33.316] [info] server sent ciphers:35
[2025-12-11 20:52:33.317] [info] Selected cipher:1
[2025-12-11 20:52:47.109] [error] Failed to select source id: 264740
[2025-12-11 20:52:47.109] [error] Failed to select source for capturer: WGC
[2025-12-11 20:52:47.109] [error] Failed to create DesktopCapturer
[2025-12-11 20:52:48.768] [error] Failed to select source id: 460124
[2025-12-11 20:52:48.768] [error] Failed to select source for capturer: WGC
[2025-12-11 20:52:48.768] [error] Failed to create DesktopCapturer
[2025-12-11 20:52:50.139] [error] Failed to select source id: 1378868
[2025-12-11 20:52:50.139] [error] Failed to select source for capturer: WGC
[2025-12-11 20:52:50.139] [error] Failed to create DesktopCapturer
[2025-12-11 20:52:51.552] [error] Failed to select source id: 920200
[2025-12-11 20:52:51.552] [error] Failed to select source for capturer: WGC
[2025-12-11 20:52:51.552] [error] Failed to create DesktopCapturer
[2025-12-11 20:52:55.113] [info] starting download for http://update.teamspeak.com/windows/x64/latest/info.json
[2025-12-11 20:52:55.346] [info] connected to push system.
[2025-12-11 20:53:06.288] [error] Failed to select source id: 0
[2025-12-11 20:53:06.288] [error] Failed to select source for capturer: WGC
[2025-12-11 20:53:06.288] [error] Failed to create DesktopCapturer
[2025-12-11 20:53:07.045] [error] Failed to select source id: 1
[2025-12-11 20:53:07.045] [error] Failed to select source for capturer: WGC
[2025-12-11 20:53:07.045] [error] Failed to create DesktopCapturer
[2025-12-11 20:53:07.780] [error] Failed to select source id: 1
[2025-12-11 20:53:07.780] [error] Failed to select source for capturer: WGC
[2025-12-11 20:53:07.780] [error] Failed to create DesktopCapturer
[2025-12-11 20:53:53.205] [warning] Terminating RPC channel
[2025-12-11 20:53:53.205] [warning] RPC channel terminated
[2025-12-11 20:53:53.205] [warning] Terminating RPC channel
[2025-12-11 20:53:53.205] [warning] RPC channel terminated
//Repeat the [warning] until I close the client

[2025-12-11 20:53:53.205] [info] connected to push system.
[2025-12-11 20:53:53.205] [info] disconnected from push system.
[2025-12-11 20:53:53.207] [warning] Terminating RPC channel
[2025-12-11 20:53:53.207] [warning] RPC channel terminated
[2025-12-11 20:53:53.313] [info] Notifications_Windows dtor

Hello, here is the new log.

id 0 and 1 are monitor 1 and 2.
Every other ids are either Edge, Discord (yes, sorry) and ts3 and 6.
The only one “working” is the Files explorer and giving me what is, I guess, the loading screen infinitly (rotating blue clock) at the following line:
”[2025-12-11 20:52:55.113] [info] starting download for http://update.teamspeak.com/windows/x64/latest/info.json”

I tried with and without hardware acceleration with same result.
Launching as pc administrator too.

Thank you.

1 Like
8

Thank you I’ll forward this, I expect to have an update on Tuesday :slight_smile:

This is just the message that the client auto updater is fetching for new updates. So it can be ignored.

2 Likes
9

Make sense. I was confused for a moment. It appear in the right order (since the file exlorer is the last in my list before I switch to the monitor tab, and it’s the moment I should have click on it).
I must have a crazy timing, I did try multiple times with same result and the same line right before monitor tab I end up believing it was for the kinda sucessful process.
Now I feel as dumb as when I was asking about server requirement when it’s p2p.

Anyway thanks for your patience. I’m looking forward to it.

1 Like
10

Thanks for the logs. Given that the File-Explorer is somewhat ‘working’, I’d tend to think this might be a permissions issue. Could you retry with elevated permissions for the client (just to confirm)?

2 Likes
11

I was about to edit my message about it.
I just tried to give the client as much permissions as possible (firewall, anything connection related, etc), same result.
To be sure I even tried on another random server since I never tried before (the csgo on the main page I think) and I can’t stream either.

Edit: Checked again, to be sure it was the right path and not ts3, but yes ts6 have every freedom as far as I know.
I tried closing ts3 to be sure too.

Edit2: Ok so … Since it was installed and launching as administrater by default and actually never tried without that.
Launching the client without that, it’s working almost flawlessly he doesn’t like my monitor with hdr, it’s flashing, i can life with that for now.
It was actually to much freedom, he couldn’t decide what to do and chose to stay still to avoid responsabilities.
(Just to clarify; right click priority > compatibility tab > Execute as administrator unticked > working now)

2 Likes
12

Consider me stumped - thanks Windows, I guess?

4 Likes
13

Hi guys

I cannot stream always says error but ı can watch others stream what should ı do ?

I have the latest version

14

Please try starting the Client without admin mode. Check your desktop shortcut for this setting.

2 Likes
15

Hey,

like the title says, on my community server using the TS 6.0.0-beta3.4 client, i am not able to start a stream. When i click on a source, like a game, the “error” sound plays. This happens for all options, also when i try to stream a monitor, after that i am not able to start the stream as no source is selected. My friend can all start a stream and it works fine. I can also watch streams from others.

I found a log file that throws this error multiple times when i click on the streaming source:

[8300:19576:0103/164055.693:WARNING:..\571da4\1\chromium\src\chrome\browser\media\prefs\capture_device_ranking.h:255] Can’t initialize the value of media.video_input.user_preference_ranking because media.default_video_capture_Device isn’t registered or is empty

[8300:20744:0103/165245.701:ERROR:..\571da4\1\chromium\src\google_apis\gcm\engine\registration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT

As chromium is mentioned in the error message, here the full versions in the TS6 client:
Version: 6.0.0-beta3.4
Build-Nummer: 1765462503
Build-Datum: 11.12.2025, 15:15:03
Chromium-Version: 143.0.7499.0

I tried to google it with the chromium, but i stuck at this point and want to share the problem.

16

Can you check if your desktop shortcut is starting the client in admin mode? If so turn it off and try it again.

2 Likes
17

good idea, but unfortunately does not help. Same behavior.

I also tried to reinstall TS6, had also no change. But i am not sure if was a completely clean install.

18

Do you know when this issue started to appear?

Can you post a fresh client log?

2 Likes
19

I send you the log file via DM.

I think the error appeared since the last client update, i tried to tinker with the problem a bit for myself or i thought a hotfix will appear soon, then i realized that i am the only one with the problem and here I am :smiley:

1 Like
20

okay, so the solution was to disable “run as admin”. It worked again after that. I was reading Leons answer wrong.

its the same solution as described in this thread: Screen share shows error when selecting window / monitor source - #11 by Jeycht

1 Like