ShellEx.info
Discord, Slack, Teams shell handlers slowing Explorer
Published September 2026, Windows 11 24H2 / 25H2
Chat apps want to be everywhere: Share to Teams, Copy link, Open in Slack, Discord overlays. Some of that lives inside the app window. Some of it registers as shell extensions that run when Explorer builds a context menu. On a busy work PC you can end up with Teams-related handlers, OneDrive/Office companions, and a leftover Electron helper all answering the same right-click.
This guide focuses on isolating Discord, Slack, and Microsoft Teams (plus nearby Microsoft 365 pieces) when the symptom is Explorer lag, not notification spam.
What you are actually hunting
Be precise. Many “Teams made Explorer slow” reports are really:
- OneDrive icon overlays and context menus on work files
- Office shell extensions (previous versions, Share)
- Teams meeting add-ins inside Outlook (not Explorer)
- True Explorer context menu handlers from a collaboration client
Discord and Slack are less aggressive than classic WinRAR, but machine-wide installs, Share extensions, or partner tools can still appear in ShellExView. Treat product names as search hints, not guarantees.
Baseline method for any third-party menu lag: Disable shell extensions on Windows 11 and Windows 11 context menu slow fix.
Reproduce with folder contrast
- Right-click a file on the local Desktop (not cloud). Time it.
- Right-click a file inside a OneDrive - Company or Teams-synced library path. Time it.
- Right-click empty desktop background. Time it.
Interpretation:
| Pattern | Likely area |
|---|---|
| Slow everywhere | Global context menu handler |
| Slow only in synced/work folders | Cloud / OneDrive / share handlers |
| Slow only on desktop background | Desktop Directory\Background handlers |
| Slow after opening Teams/Discord | Helper re-registered or woke a service |
ShellExView pass for chat and collab apps
- Open ShellExView as Administrator.
- Hide Microsoft extensions temporarily except when investigating Teams. Teams/OneDrive often ship as Microsoft-signed. For that pass, clear “Hide All Microsoft Extensions” and filter by name instead.
- Search for:
Discord,Slack,Teams,OneDrive,SharePoint,Office. - Disable Context Menu entries you do not need (F7). Prefer one change at a time when you are documenting results; use binary search when the list is long.
- Restart Explorer. Retest both local and work folders.
Verify odd DLL names with the DLL checker.
Binary search (recommended on office PCs)
Work images often have 40+ handlers:
- Disable half of context menu extensions (include Microsoft share/OneDrive entries in the pool if work folders are slow).
- Restart Explorer; test the slow folder.
- Keep halving until one handler (or a small vendor group) explains the delay.
- Re-enable the rest.
If the winner is OneDrive rather than Teams, fix overlays and menus using the same disable approach; Teams can stay running.
App-side toggles worth trying first
Microsoft Teams
- In Teams, open Settings and look for options related to startup, notifications, and any Windows integration / presence features.
- Prevent Teams from launching at login if you do not need instant presence (Task Manager → Startup).
- Prefer the store/new Teams client updates; old classic Teams leftovers sometimes leave Explorer noise after migration. Uninstall classic Teams if both are present.
Teams channel files open through OneDrive/SharePoint paths. If lag is folder-specific, disable OneDrive context menus for a test rather than uninstalling Teams.
Slack
- Slack Preferences → disable launch on login for a test.
- Check whether any Slack Share/helper companion was installed by your company (rare, but shows in Apps list).
- Use ShellExView for any Slack-labeled context menu rows.
Discord
- Discord Settings → Windows settings: turn off Open Discord at startup for testing.
- Disable hardware acceleration only if you are chasing GPU issues; it does not fix shell menus.
- In ShellExView, disable Discord-labeled shell entries if present. Overlay hooks inside games are not the same as Explorer context menus; do not confuse the two.
Distinguishing overlay vs context menu
Icon overlays (green checks, sync badges) and context menus are different shell types in ShellExView.
- Overlays: slow folder painting and CPU in Explorer windows.
- Context menus: slow right-click.
If click is slow but icons are fine, prioritize Context Menu type. If both hurt, disable overlays second. On Windows 11 24H2/25H2, overlay limits still apply; crowding overlays with OneDrive + Dropbox + Google Drive worsens everything around work folders where Teams content lives.
When Event Viewer helps
If Explorer restarts when you right-click a Teams file:
- Event Viewer → Windows Logs → Application.
- Look for Application Error on
explorer.exe. - Note Faulting module name.
- Disable that DLL in ShellExView.
Details: Find which shell extension is crashing Explorer.
Keep chat without Explorer tax
- Use Share from inside Teams/Slack/Discord, not from Explorer.
- Pin apps to the taskbar.
- Leave OneDrive syncing but drop its context menu if work-folder right-click is the pain point.
- After major Teams or Office updates, re-check ShellExView; updates re-enable handlers.
If chat apps are clean and lag remains, inspect archivers and Adobe next, or run a full binary search across non-essential handlers.