Windows 10, any idea why? I have to alt + ctrl + del and restart it or even restart PC 
cant alt tab or anything after screen sharing for a little bit longer.
Iām guessing this is an issue of insufficient RAM and therefore the explorer is restarting / crashing.
Can you please provide more system information and keep an eye on the task manager for any overloads?
Stream settings as well as user count would be good to investigate this further.
2 Likes
Hey,
Usage isnt so big
Its under playing, streaming and other activites. And file explorer is not working at the moment ;p
Iāve got 32gb of ddr5 with ryzen 9800x3d + rtx 4080 so PC shouldnt be a problem.
I use Cisco OpenH264
hardware acceleration is on
AV1:
Nvidia NVENC in coding and decoding
H264
Cisco in both, nothing else changed.
Stream quality is good, just my file explorer is freezing after like 20-30 min xD
1 Like
Also having this problem as well as another user in my play group
I can also second this, though I did come across this post on Reddit talking about it:
Reddit Post
Iām currently using the ādisable-gpuā but havenāt tested it just yet.
Also have another friend with the same issue currently on Windows 10.
1 Like
Setup:
- Windows 10 Pro x64 (extended security updates enrollment) up to date.
- Teamspeak client 6 beta 6.0.0-beta3.4
- Server teamspeak 6.0.0 beta-8 self hosted on Oracle Linux VM (Oracle-Linux-9.7-aarch64-2026.01.29-0) and on sandbox Box64 to convert instructions from amd64 to arm64 (VM architecture)
- Screen sharing with default settings P2P mode, audio settings seem irrelevant, happens sharing audio or not.
Issue: Upon Screen sharing, Start Menu responsiveness starts to degrade. The more time you share screen, for example FFXIV with friends or whole screen, the more it takes Start Menu to open. This starts to improve slowly upon stopping the screen share. The problem can slowly solve itself, but it can take whole minutes to open the menu the more yo share screen. Even to the point that i need to shutdown my PC from cmd with shutdown command.
Win + R shortcut is unnafected, but Win + Shift + S for screen capture is not responsive either. Start menu does not react upon clicking on it or using Windows Key when the problem is ongoing.
Webcam video feed seems to have no impact over this issue, itās not problematic, only capturing monitor screen.
Anything i can help you can ask me.
1 Like
What PC specs are you running?
3 Likes
Let share msinfo32 screenshots, it should be faster. I scrubbed it of personal info.
I have been sharing screen for tabletop simulator the whole screen for a bunch of hours and it didnāt cause any issues, so it may be related to the amount of āmovementā of the shared screen, if that makes sense at all, idk, iām not a system programmerā¦ 
Upon sharing screen for more than half an hour with Honkai: Star Rail running, the start menu did not degrade at all, so i donāt know if it could be an issue in my system. This happened multiple days and this is the first time it didnāt reproduce.
Will update this answer if i manage to reproduce it again.
UPDATE: Streaming Final Fantasy XIV application seemed to degrade a bit the Start menu responsiveness. The more I screen share it as application the more it degrades.
This is happening to me if I leave a stream running, even if there are no viewers and nobody else in the server at all. If I can get to task manager to restart the Windows Explorer task, it works perfectly fine after the task comes back up, then starts to slowly degrade again.
The first interaction with Explorer pushes it to use close to 1 entire CPU core, then the CPU usage drops and it becomes responsive again. Itās not totally consistent but it seems like over time the duration that Explorer sits at high CPU usage and stays unresponsive grows and also the amount of time it stays responsive shrinks.
Having this issue too on Windows 11 and my friend reported this issue with Windows 10. Nothing out of the ordinary in Task Manager.
To fix, I have to press ALT+CTRL+DEL and click around then my other apps become responsive again.
I can confirm that the gpu launch param did not work for me on Windows 10 sadly.
Thanks for all the feedback Iāll forward this to QA to further investigate
5 Likes
I can confirm that Iām having the same symptoms on windows 10.
Same issue here! At first, I thought it was FFXIV, but after further testing, it seems that screen sharing is the root cause, and FF is making the slowdown significantly worse. In fact, I couldnāt do anything in Windows at all. The Start menu wasnāt working, there was no Alt+Tab, Task Manager wouldnāt start and there was no taskbar. Restarting Windows Explorer fixed it at first, but after a few times it got to the point where it was slowing down the restart as well (up to multiple minutes). Even after stopping the stream and closing TeamSpeak, the drop in performance stayed until I restarted Explorer. There was no visible high overload and the CPU, RAM and GPU usage stayed at around 50%. I use Cisco OpenH.264 with the NVIDIA NVENC H.264 encoder and the default settings.
Some other things I tested:
- Nobody has to actually watch the stream.
- The same issue occurs with software encoding.
- After ending the stream, opening the Start menu results in 15% CPU usage on Explorer while using around 150MB RAM. After restarting and opening the menu, the CPU usage hits at max 2% with 60MB RAM.
- During streaming, the RAM usage of Windows Explorer slowly grows by roughly 0.1ā0.2 MB per second. This starts ca. 5 seconds after starting the stream. (I could actually observe this live: stream starts ā Explorer usage grows; I stop the stream ā it halts; I start the stream again ā it starts growing again)
- It only happens when streaming a window. I tested this with my browser window with an open YouTube video (no difference if it was playing or not), both with and without hardware acceleration (both chrome canary and the normal version of chrome), and there was no difference (also tried a plain notepad window: same growth). Streaming the whole screen works fine.
I hope some of this information is helpful. If you need anything else, please let me know.
Here are my specs:
OS Name Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
Processor Intel(R) Coreā¢ i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BaseBoard Product MPG Z390 GAMING PRO CARBON AC (MS-7B17)
Installed Physical Memory (RAM) 32.0 GB
Name NVIDIA GeForce RTX 2080
Driver Version 32.0.15.9186
Can confirm that I am also experiencing the same issue. I was able to fix this without a reboot.
- Open Tasks Manager
- Find āexplorer.exeā
- Right click it and click ārestartā
- If you did not see your taskbar disappear/reappear, attempt to restart it again. (you may need to open file explorer to have explorer.exe appear back in task list)
In my case looks like update to Win11 (+ debloat ofc :P) fixed the problem 
Also experiencing the same issue.
Windows 10
32GB RAM
2080 Ti
i5 8600K,
Dual monitors 1440p + 1080p. Game on 1440p monitor, TS window on secondary 1080p monitor.
Issue starts while streaming EDF6, Peak or Mass Effect LE, and doesnāt resolve until explorer.exe is restarted. Was only streaming at 720p 60.
We currently suspect that the issue, especially the Windows Explorer hanging, is related to Windows Graphics Capture (WGC).
Based on our analysis, WGC capturing may lead to instability in certain environments, which could explain the behavior you are seeing. As a precautionary measure, we have temporarily disabled WGC.
Please retest the issue once the next version is available. In that build, WGC will be disabled by default. If you would like to continue using capture, please switch to DXGI and verify whether the problem still occurs.
We would appreciate your feedback after testing the updated version.
5 Likes
Hello,
My friends have been experiencing heavy lag on the Windows 10 Explorer when they screenshare, there is also a yellow border on the window they are streaming.
I know the yellow border is caused by the Windows api used for capture, that unfortunatelly cannot be turned off on Windows 10.
Can the lag be fixed by our end? If no, can you update the client to fix this issue and, if possible, add more capture methods that dont rely on the Windows api for capture?
Thank you.
This issue should get resolved with the next update.
4 Likes