When Xbox Game Bar refuses to record

One thing to establish before troubleshooting anything: Game Bar will not record File Explorer, the desktop, or various system windows. That is intentional. If that was your target, the tool is behaving correctly and no setting will change it.

Recording is switched off separately from the overlay

The overlay opening tells you nothing about whether capture is enabled, because they are independent settings. This catches more people than any other cause.

Settings, then Gaming, then Captures. Confirm recording is on. Recent Windows builds put the maximum recording length and the audio capture options on this same page, both of which are worth a glance while you are here.

One level up, under Gaming and then Xbox Game Bar, check the Game Bar itself is enabled and that its keyboard shortcut has not been claimed by some other application.

You used the shortcut for the other feature

Two capabilities get conflated constantly. Windows with Alt and R begins recording from now. Windows with Alt and G saves what already happened — and it can only do that if background recording was running the whole time.

Pressing the second one after something worth keeping, and receiving nothing, means background recording was off. It sits in the same Captures page and consumes performance while active, which is precisely why it ships disabled.

Windows has not classified the program as a game

Game Bar was designed around games and its treatment of everything else is inconsistent. Some applications capture normally, some yield a black rectangle, some are declined outright.

There is a manual override worth knowing. With the program focused, open the overlay and find the checkbox declaring that this is a game. Ticking it makes Windows treat the window as fair game for capture.

It resolves many cases and not all. Programs running with elevated privileges, or rendering through unusual means, can still be refused regardless.

The hardware encoder is unavailable

Capture leans on the video encoder built into your graphics card. If the driver is stale, or another program has already claimed the encoder, recording fails without producing any error worth reading.

Shut down everything else capable of capturing — OBS, the NVIDIA or AMD overlay, any streaming software — and try with Game Bar alone. Success at that point identifies the culprit.

Failure at that point points at the driver, and the fix is updating it from the manufacturer rather than through Windows Update, which is habitually several months behind.

The clips exist somewhere you have not checked

Sometimes everything works and the files are simply elsewhere. The default destination is a Captures folder within Videos in your user profile.

If that folder was relocated, pointed at cloud storage, or lives on a drive that has run out of room, recording can fail with no visible complaint. Verify the destination exists and has space.

Knowing when to stop

Game Bar is convenient within a narrow band. No desktop capture, no choosing an arbitrary window, minimal control over quality, and on certain hardware pairings it never behaves regardless of what you change.

Having worked through this list without result, the sensible response is a different tool rather than another hour of settings. OBS is free, captures anything visible including the desktop, and never asks Windows whether your program counts as a game.

Once a recording exists

Game Bar produces MP4 files that are almost always larger than whatever you intend to do with them. A few minutes at 1080p60 comfortably exceeds what a chat platform or a mail server will carry.

Reduce it to the part that mattered before anything else — duration drives size harder than quality does, so begin with the video trimmer.

When a Discord server declines the upload, the size cap is why — handle it with compress for Discord.

For a mail attachment or any general limit, use the video compressor.

Common questions