Money is no object. One machine, one grinder, one bean source. What's YOUR true endgame?
My current thinking after way too much research:
\- Machine: Kees van der Westen Speedster
\- Grinder: Kafatek Monolith Flat Max (Shuriken burrs)
\- Beans: roasting my own
\- Plus RO water + remineralization
Am I wrong? Would you go Slayer, GS3 MP, Decent, or a Londinium lever instead? Convince me.
Money is no object. One machine, one grinder, one bean source. What's YOUR true endgame?
My current thinking after way too much research:
- Machine: Kees van der Westen Speedster
- Grinder: Kafatek Monolith Flat Max (Shuriken burrs)
- Beans: roasting my own
- Plus RO water + remineralization
Am I wrong? Would you go Slayer, GS3 MP, Decent, or a Londinium lever instead? Convince me.
Posting this because I wasted hours on Discord screen share being stuck on loading forever, and most of the common fixes online did absolutely nothing.
Discord desktop screen share was stuck on loading forever.
In my case:
The key clue was:
Discord Web worked, but Discord desktop and PTB both failed.
That means the account/server/basic network path was probably fine. The issue was somewhere in the Windows desktop capture path.
I tried:
Restart Discord
Fully quit Discord from system tray
Restart PC
Update Discord
Reset Voice and Video settings
Try another voice channel
Try a DM call
Try another server
Try lowering stream quality to 720p 30fps
Try sharing entire screen instead of app window (main issue)
Try a game in borderless windowed (worked)
Try a game in normal fullscreen (worked)
None of that fixed it.
I tried killing Discord processes:
taskkill /F /IM Discord.exe
taskkill /F /IM Update.exe
taskkill /F /IM Squirrel.exe
Deleted Discord folders:
rmdir /S /Q "%LOCALAPPDATA%\Discord"
rmdir /S /Q "%APPDATA%\discord"
Then reinstalled Discord.
This fixed the reinstall itself, but screen share still did not work.
One of my earlier Discord install logs showed the installer had failed because the Discord folder was locked:
Install path C:\Users\PC\AppData\Local\Discord already exists, burning it to the ground
Access to the path 'C:\Users\PC\AppData\Local\Discord' is denied.
is the app still running???
So yes, I did have a dirty install attempt at one point, but cleaning that up did not solve the screen share problem.
I tried:
Discord Stable
Discord PTB
Discord Web
Result:
Discord Web worked
Discord Stable failed
Discord PTB failed
This was important. If Web works but both desktop builds fail, do not keep reinstalling Discord forever. The shared failure point is probably Windows desktop capture, not the Discord account.
I tried launching PTB with GPU disabled:
"%LOCALAPPDATA%\DiscordPTB\Update.exe" --processStart DiscordPTB.exe --process-start-args "--disable-gpu"
Still did not fix it.
I checked the usual Discord settings people mention:
Voice & Video
Hardware Acceleration
Advanced Hardware Acceleration
Reset Voice Settings
Debugging
Experimental / advanced screen capture settings
OpenH264 / H.264 settings
Some of these settings were missing or moved in the current Discord UI, so I could not follow some older guides exactly.
Either way, no Discord setting fixed it.
I tried:
Clean GPU driver reinstall
Force Discord to high-performance GPU
Disable Hardware-accelerated GPU scheduling
Reboot after disabling HAGS
Disable MPO
Turn off overlays
Try Discord after reboot before opening other apps
Still no fix.
I killed or disabled things that might hook capture:
NVIDIA overlay
NVIDIA App / GeForce Experience overlay
Xbox Game Bar
Steam overlay
OBS
MSI Afterburner
RivaTuner Statistics Server
SignalRGB / VortxEngine
ExitLag
Wallpaper Engine
Medal
Overwolf
AMD/NVIDIA recording tools
VPN/proxy-style apps
Still no fix.
Since Discord Web worked, I eventually stopped blaming the router. But I still considered/checked:
VPN
ExitLag
Firewall
Proxy
DNS
Winsock/IP reset
Different Discord build
Different call/server
The fact that Discord Web worked made a pure network issue unlikely.
The issue was Windows CaptureService.
Run PowerShell as Administrator:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Mine showed:
Name Status StartType
---- ------ ---------
CaptureService_b44f2 Stopped Disabled
That was the real issue.
Your suffix will probably be different. It might be something like:
CaptureService_12345
CaptureService_abcd1
CaptureService_xxxxx
That suffix is normal. Windows creates per-user service instances with random-looking suffixes.
The problem is when it says:
Disabled
Discord desktop screen sharing depends on Windows desktop capture components. If this service is disabled, Discord can connect to the stream session but fail to actually capture/send video. Result: everyone sees loading forever.
Discord/WebRTC logs showed the stream connection was happening, but capture was failing.
The important error pattern was basically:
Windows(Error { code: HRESULT(0x80070422),
message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." })
And stream stats showed video was not being produced/sent properly.
That matched the Windows service state:
CaptureService_b44f2 Stopped Disabled
Open Command Prompt as Administrator.
First, set the template service back to Manual:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v Start /t REG_DWORD /d 3 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v UserServiceFlags /t REG_DWORD /d 3 /f
Then check your actual suffixed service name:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If yours is, for example:
CaptureService_b44f2
then run this, replacing the name with your own suffix:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /v Start /t REG_DWORD /d 3 /f
Important: replace CaptureService_b44f2 with whatever your PC shows.
Then sign out fully:
shutdown /l
Sign back in.
Check again:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Good result should be:
CaptureService_xxxxx Stopped Manual
or:
CaptureService_xxxxx Running Manual
Stopped is fine if the startup type is Manual.
Disabled is the bad state.
After fixing that, Discord screen share worked again.
Something is probably enforcing disabled capture services, usually:
Windows debloat script
Privacy/optimizer tool
Group Policy
Registry policy
Security hardening script
Gaming/streaming optimizer
You can try deleting the broken per-user instance after setting the template correctly.
Example only, replace the suffix with yours:
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /f
Then sign out:
shutdown /l
Windows should recreate the per-user instance from the corrected template.
You can also check:
Get-Service -Name "BcastDVRUserService*" | Format-Table Name, Status, StartType
If that is disabled too, it may mean some debloat/privacy tool disabled Windows capture or broadcasting services.
Discord Web uses the browser capture path.
Discord desktop uses Windows desktop capture components.
So Web can work while the desktop app fails.
That was the key clue.
If your Discord screen share is stuck loading forever and:
Discord Web works
Discord Stable desktop fails
Discord PTB fails
Reinstalling Discord does nothing
GPU fixes do nothing
Overlay fixes do nothing
check this:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If it says Disabled, restore CaptureService to Manual, sign out/in, and test again.
This fixed it for me.
Posting this because I wasted hours on Discord screen share being stuck on loading forever, and most of the common fixes online did absolutely nothing.
Discord desktop screen share was stuck on loading forever.
In my case:
The key clue was:
Discord Web worked, but Discord desktop and PTB both failed.
That means the account/server/basic network path was probably fine. The issue was somewhere in the Windows desktop capture path.
I tried:
Restart Discord
Fully quit Discord from system tray
Restart PC
Update Discord
Reset Voice and Video settings
Try another voice channel
Try a DM call
Try another server
Try lowering stream quality to 720p 30fps
Try sharing entire screen instead of app window (main issue)
Try a game in borderless windowed (worked)
Try a game in normal fullscreen (worked)
None of that fixed it.
I tried killing Discord processes:
taskkill /F /IM Discord.exe
taskkill /F /IM Update.exe
taskkill /F /IM Squirrel.exe
Deleted Discord folders:
rmdir /S /Q "%LOCALAPPDATA%\Discord"
rmdir /S /Q "%APPDATA%\discord"
Then reinstalled Discord.
This fixed the reinstall itself, but screen share still did not work.
One of my earlier Discord install logs showed the installer had failed because the Discord folder was locked:
Install path C:\Users\PC\AppData\Local\Discord already exists, burning it to the ground
Access to the path 'C:\Users\PC\AppData\Local\Discord' is denied.
is the app still running???
So yes, I did have a dirty install attempt at one point, but cleaning that up did not solve the screen share problem.
I tried:
Discord Stable
Discord PTB
Discord Web
Result:
Discord Web worked
Discord Stable failed
Discord PTB failed
This was important. If Web works but both desktop builds fail, do not keep reinstalling Discord forever. The shared failure point is probably Windows desktop capture, not the Discord account.
I tried launching PTB with GPU disabled:
"%LOCALAPPDATA%\DiscordPTB\Update.exe" --processStart DiscordPTB.exe --process-start-args "--disable-gpu"
Still did not fix it.
I checked the usual Discord settings people mention:
Voice & Video
Hardware Acceleration
Advanced Hardware Acceleration
Reset Voice Settings
Debugging
Experimental / advanced screen capture settings
OpenH264 / H.264 settings
Some of these settings were missing or moved in the current Discord UI, so I could not follow some older guides exactly.
Either way, no Discord setting fixed it.
I tried:
Clean GPU driver reinstall
Force Discord to high-performance GPU
Disable Hardware-accelerated GPU scheduling
Reboot after disabling HAGS
Disable MPO
Turn off overlays
Try Discord after reboot before opening other apps
Still no fix.
I killed or disabled things that might hook capture:
NVIDIA overlay
NVIDIA App / GeForce Experience overlay
Xbox Game Bar
Steam overlay
OBS
MSI Afterburner
RivaTuner Statistics Server
SignalRGB / VortxEngine
ExitLag
Wallpaper Engine
Medal
Overwolf
AMD/NVIDIA recording tools
VPN/proxy-style apps
Still no fix.
Since Discord Web worked, I eventually stopped blaming the router. But I still considered/checked:
VPN
ExitLag
Firewall
Proxy
DNS
Winsock/IP reset
Different Discord build
Different call/server
The fact that Discord Web worked made a pure network issue unlikely.
The issue was Windows CaptureService.
Run PowerShell as Administrator:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Mine showed:
Name Status StartType
---- ------ ---------
CaptureService_b44f2 Stopped Disabled
That was the real issue.
Your suffix will probably be different. It might be something like:
CaptureService_12345
CaptureService_abcd1
CaptureService_xxxxx
That suffix is normal. Windows creates per-user service instances with random-looking suffixes.
The problem is when it says:
Disabled
Discord desktop screen sharing depends on Windows desktop capture components. If this service is disabled, Discord can connect to the stream session but fail to actually capture/send video. Result: everyone sees loading forever.
Discord/WebRTC logs showed the stream connection was happening, but capture was failing.
The important error pattern was basically:
Windows(Error { code: HRESULT(0x80070422),
message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." })
And stream stats showed video was not being produced/sent properly.
That matched the Windows service state:
CaptureService_b44f2 Stopped Disabled
Open Command Prompt as Administrator.
First, set the template service back to Manual:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v Start /t REG_DWORD /d 3 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v UserServiceFlags /t REG_DWORD /d 3 /f
Then check your actual suffixed service name:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If yours is, for example:
CaptureService_b44f2
then run this, replacing the name with your own suffix:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /v Start /t REG_DWORD /d 3 /f
Important: replace CaptureService_b44f2 with whatever your PC shows.
Then sign out fully:
shutdown /l
Sign back in.
Check again:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Good result should be:
CaptureService_xxxxx Stopped Manual
or:
CaptureService_xxxxx Running Manual
Stopped is fine if the startup type is Manual.
Disabled is the bad state.
After fixing that, Discord screen share worked again.
Something is probably enforcing disabled capture services, usually:
Windows debloat script
Privacy/optimizer tool
Group Policy
Registry policy
Security hardening script
Gaming/streaming optimizer
You can try deleting the broken per-user instance after setting the template correctly.
Example only, replace the suffix with yours:
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /f
Then sign out:
shutdown /l
Windows should recreate the per-user instance from the corrected template.
You can also check:
Get-Service -Name "BcastDVRUserService*" | Format-Table Name, Status, StartType
If that is disabled too, it may mean some debloat/privacy tool disabled Windows capture or broadcasting services.
Discord Web uses the browser capture path.
Discord desktop uses Windows desktop capture components.
So Web can work while the desktop app fails.
That was the key clue.
If your Discord screen share is stuck loading forever and:
Discord Web works
Discord Stable desktop fails
Discord PTB fails
Reinstalling Discord does nothing
GPU fixes do nothing
Overlay fixes do nothing
check this:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If it says Disabled, restore CaptureService to Manual, sign out/in, and test again.
This fixed it for me.
Posting this because I wasted hours on Discord screen share being stuck on loading forever, and most of the common fixes online did absolutely nothing.
Discord desktop screen share was stuck on loading forever.
In my case:
The key clue was:
Discord Web worked, but Discord desktop and PTB both failed.
That means the account/server/basic network path was probably fine. The issue was somewhere in the Windows desktop capture path.
I tried:
Restart Discord
Fully quit Discord from system tray
Restart PC
Update Discord
Reset Voice and Video settings
Try another voice channel
Try a DM call
Try another server
Try lowering stream quality to 720p 30fps
Try sharing entire screen instead of app window (main issue)
Try a game in borderless windowed (worked)
Try a game in normal fullscreen (worked)
None of that fixed it.
I tried killing Discord processes:
taskkill /F /IM Discord.exe
taskkill /F /IM Update.exe
taskkill /F /IM Squirrel.exe
Deleted Discord folders:
rmdir /S /Q "%LOCALAPPDATA%\Discord"
rmdir /S /Q "%APPDATA%\discord"
Then reinstalled Discord.
This fixed the reinstall itself, but screen share still did not work.
One of my earlier Discord install logs showed the installer had failed because the Discord folder was locked:
Install path C:\Users\PC\AppData\Local\Discord already exists, burning it to the ground
Access to the path 'C:\Users\PC\AppData\Local\Discord' is denied.
is the app still running???
So yes, I did have a dirty install attempt at one point, but cleaning that up did not solve the screen share problem.
I tried:
Discord Stable
Discord PTB
Discord Web
Result:
Discord Web worked
Discord Stable failed
Discord PTB failed
This was important. If Web works but both desktop builds fail, do not keep reinstalling Discord forever. The shared failure point is probably Windows desktop capture, not the Discord account.
I tried launching PTB with GPU disabled:
"%LOCALAPPDATA%\DiscordPTB\Update.exe" --processStart DiscordPTB.exe --process-start-args "--disable-gpu"
Still did not fix it.
I checked the usual Discord settings people mention:
Voice & Video
Hardware Acceleration
Advanced Hardware Acceleration
Reset Voice Settings
Debugging
Experimental / advanced screen capture settings
OpenH264 / H.264 settings
Some of these settings were missing or moved in the current Discord UI, so I could not follow some older guides exactly.
Either way, no Discord setting fixed it.
I tried:
Clean GPU driver reinstall
Force Discord to high-performance GPU
Disable Hardware-accelerated GPU scheduling
Reboot after disabling HAGS
Disable MPO
Turn off overlays
Try Discord after reboot before opening other apps
Still no fix.
I killed or disabled things that might hook capture:
NVIDIA overlay
NVIDIA App / GeForce Experience overlay
Xbox Game Bar
Steam overlay
OBS
MSI Afterburner
RivaTuner Statistics Server
SignalRGB / VortxEngine
ExitLag
Wallpaper Engine
Medal
Overwolf
AMD/NVIDIA recording tools
VPN/proxy-style apps
Still no fix.
Since Discord Web worked, I eventually stopped blaming the router. But I still considered/checked:
VPN
ExitLag
Firewall
Proxy
DNS
Winsock/IP reset
Different Discord build
Different call/server
The fact that Discord Web worked made a pure network issue unlikely.
The issue was Windows CaptureService.
Run PowerShell as Administrator:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Mine showed:
Name Status StartType
---- ------ ---------
CaptureService_b44f2 Stopped Disabled
That was the real issue.
Your suffix will probably be different. It might be something like:
CaptureService_12345
CaptureService_abcd1
CaptureService_xxxxx
That suffix is normal. Windows creates per-user service instances with random-looking suffixes.
The problem is when it says:
Disabled
Discord desktop screen sharing depends on Windows desktop capture components. If this service is disabled, Discord can connect to the stream session but fail to actually capture/send video. Result: everyone sees loading forever.
Discord/WebRTC logs showed the stream connection was happening, but capture was failing.
The important error pattern was basically:
Windows(Error { code: HRESULT(0x80070422),
message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." })
And stream stats showed video was not being produced/sent properly.
That matched the Windows service state:
CaptureService_b44f2 Stopped Disabled
Open Command Prompt as Administrator.
First, set the template service back to Manual:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v Start /t REG_DWORD /d 3 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService" /v UserServiceFlags /t REG_DWORD /d 3 /f
Then check your actual suffixed service name:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If yours is, for example:
CaptureService_b44f2
then run this, replacing the name with your own suffix:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /v Start /t REG_DWORD /d 3 /f
Important: replace CaptureService_b44f2 with whatever your PC shows.
Then sign out fully:
shutdown /l
Sign back in.
Check again:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
Good result should be:
CaptureService_xxxxx Stopped Manual
or:
CaptureService_xxxxx Running Manual
Stopped is fine if the startup type is Manual.
Disabled is the bad state.
After fixing that, Discord screen share worked again.
Something is probably enforcing disabled capture services, usually:
Windows debloat script
Privacy/optimizer tool
Group Policy
Registry policy
Security hardening script
Gaming/streaming optimizer
You can try deleting the broken per-user instance after setting the template correctly.
Example only, replace the suffix with yours:
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\CaptureService_b44f2" /f
Then sign out:
shutdown /l
Windows should recreate the per-user instance from the corrected template.
You can also check:
Get-Service -Name "BcastDVRUserService*" | Format-Table Name, Status, StartType
If that is disabled too, it may mean some debloat/privacy tool disabled Windows capture or broadcasting services.
Discord Web uses the browser capture path.
Discord desktop uses Windows desktop capture components.
So Web can work while the desktop app fails.
That was the key clue.
If your Discord screen share is stuck loading forever and:
Discord Web works
Discord Stable desktop fails
Discord PTB fails
Reinstalling Discord does nothing
GPU fixes do nothing
Overlay fixes do nothing
check this:
Get-Service -Name "CaptureService*" | Format-Table Name, Status, StartType
If it says Disabled, restore CaptureService to Manual, sign out/in, and test again.
This fixed it for me.