What changed and why it matters
Game Capture works by injecting a small, signed module so OBS can read frames directly from your game. OBS 31.1.2 ships an updated code signing certificate for this module. Anti-cheat systems check signatures to decide what to allow. When a certificate rolls over, a few titles may react conservatively until whitelists update. That is why a stream that worked yesterday might request a different capture mode today. See the official background note for context.
Avoid anti-cheat headaches in 5 steps
- Switch the source to Window Capture or Display Capture for that session.
- Launch the game without overlays such as FPS counters, RGB controllers, or capture utilities that also hook.
- Run OBS and the game at the same privilege level either both admin or both standard user to avoid elevation mismatches.
- Check the game’s anti-cheat status page for recent updates. Many teams whitelist new signatures on a rolling basis.
- Third-party shader injectors and reshade style tools.
- Monitoring overlays such as GPU, chat, or stats that draw on top of games.
- Outdated OBS plugins that install their own capture helpers.
Compatibility checklist
| Area | Risk | What to check |
|---|---|---|
| Privilege level | Medium | OBS and game should both run as admin or both standard. Mismatches block hooks. |
| Overlays | High | Disable competing overlays and injectors during diagnosis. |
| Game anti-cheat | Varies | Check recent patches and known compatibility notes in support pages. |
| OBS version | Low | Verify 31.1.2 or newer so the updated certificate is present. |
| Plugins | Medium | Remove or update old capture helpers that may be blocked by anti-cheat. |
FAQ for common capture errors
Why did my capture break overnight
You likely updated OBS or your game’s anti-cheat refreshed rules. The new certificate is valid, but some titles take time to update whitelists. Use Window Capture for that game temporarily and watch for patches.
Is this a security risk
No. Certificate rotation is normal hygiene. The issue is simply that strict anti-cheats verify signer identities and may require updates when those identities change.
Can I roll back to an older OBS
You can, but it is better to update and use fallbacks. Older builds will eventually age out of support. Keep a portable copy of a known-good version only as a last resort and report the incompatible title on the forums.
What about Windows on Arm
OBS 31.1 introduced Windows on Arm support in an experimental state. Certificate behavior follows the same principles, but always confirm drivers and plugins on Arm devices. See the WoA FAQ.
Bottom line
The OBS 31.1.2 capture certificate update is routine, but it intersects with strict anti-cheat policies in some games. Update OBS, check your logs and signature, use per-title fallbacks, audit overlays, and escalate with clean diagnostics. Keep an eye on the release feed and the KB article for hotfixes and game-specific notes. With these practices you can stream reliably while the ecosystem refreshes whitelists.