GameBarPresenceWriter.exe: What It Does and How to Troubleshoot Stutter

What is GameBarPresenceWriter.exe?

GameBarPresenceWriter.exe is associated with Windows and Xbox Game Bar game-presence functionality. Microsoft documents Presence Writer as receiving events when a game gains focus, loses focus, or closes. Depending on enabled Xbox features, the default implementation can update a game’s presence.

Seeing the process in Task Manager does not prove that it is causing high CPU usage, network congestion, or frame-time spikes. Treat it as one variable to test, not an automatic culprit.

Diagnose the stutter before changing Windows

Start by reproducing the problem in a repeatable game scene. Record average FPS and frame-time behavior, CPU and GPU utilization, temperatures, clock speeds, disk activity, and background processes. Change one setting at a time and repeat the same test.

If stutter appears only after 10–30 minutes, investigate temperatures and power limits first. If it happens in only one game, compare another title and consider game-specific settings, shader compilation, or driver profiles.

Step 1: Test Xbox Game Bar and capture settings

Open Settings → Gaming → Xbox Game Bar. If you do not use its widgets or shortcuts, turn it off where your Windows version provides that option. Then open Settings → Gaming → Captures and disable background recording if you do not need it.

Restart Windows, reproduce the same scene, and compare frame-time and system load. This is the lowest-risk test because it avoids protected registry keys. Disabling Xbox Game Bar does not automatically disable Steam Overlay, Discord Overlay, OBS, or GPU-vendor overlay tools.

1. Open Settings → Gaming → Xbox Game Bar and disable features you do not use.
2. Open Settings → Gaming → Captures and turn off background recording if it is unnecessary.
3. Restart and compare frame-time in the same game scene.

Step 2: Consider Game DVR policy only if needed

If the Settings-based test makes no difference and you are comfortable with Windows administration, you can investigate the Game DVR configuration. Back up first: create a restore point, export the relevant registry keys, and record existing values. On managed computers, check with the administrator before changing policy settings.

The AllowGameDVR policy controls Windows Game Recording and Broadcasting. Setting a policy can affect recording features and is not a guaranteed FPS optimization. Do not change registry values simply because the process exists; measure the same workload before and after.

Microsoft reference: ApplicationManagement Policy CSP. Policy availability and behavior can vary by Windows edition and management configuration.

Step 3: Treat Presence Writer registry overrides as a last resort

A commonly circulated workaround targets the Windows Runtime ActivatableClassId registration for Presence Writer. This is a protected system area. Changing ownership, permissions, or activation values can create problems and is not a routine gaming optimization documented by Microsoft.

For most users, skip this step. If an experienced administrator chooses to investigate it, they should first export the exact key, document original values and permissions, create a restore point, and have a tested recovery plan. Do not assume that a hard-coded rollback value matches every Windows build.

Can you terminate the process with taskkill?

You can test a running process by terminating it from an elevated terminal, but this is only a temporary A/B test. Windows or the application stack may launch the component again when its activation conditions are met. A process returning does not by itself indicate malware or a fault.

Avoid repeatedly killing system components as a substitute for identifying the cause. If the change has no repeatable effect on frame-time, restore normal settings and investigate other causes.

taskkill /f /im gamebarpresencewriter.exe

Other common causes of PC game stutter

Uneven motion can occur even when average FPS looks high. Look at frame-time spikes and investigate likely causes systematically rather than applying a long list of tweaks.

• Thermal throttling or CPU/GPU power limits during sustained play.
• Shader or pipeline compilation, especially the first time effects or areas appear.
• GPU saturation, CPU-thread bottlenecks, memory pressure, or storage activity.
• Graphics drivers, game-specific settings, overlays, capture tools, or background applications.
• DPC/ISR latency, unstable RAM, GPU/VRAM errors, or power-delivery problems when symptoms warrant deeper diagnostics.

Frequently asked questions