Quick Resume can save time in single-player games, but it can cause connection problems in titles that need an active server session. Xbox now lets you disable it for individual games, which makes it easier to keep the feature where it helps and turn it off where it causes trouble.
Then there’s the other version of this story. You pick up an online shooter through Quick Resume and spend the next several minutes staring at a broken lobby, the client confused about where you are, while the server has already dropped you entirely. Eventually, you close and reopen the game manually, which is what you would’ve done anyway.
Both of those are Quick Resume. Same feature, totally different results depending on what you’re playing.
Xbox now lets players disable Quick Resume for individual games through Quick Resume settings, so selected titles can always launch fresh. So managing the feature means either quitting specific games properly before you walk away, or removing them from the suspended queue after the fact. Once you know where those options live, it takes about ten seconds either way.
What Quick Resume is Saving
Switch away from a game without quitting, and the Series X|S saves a snapshot of your game state to a dedicated section of the console’s SSD. Microsoft’s Velocity Architecture is what makes this fast enough to be useful. Those snapshots stay put for weeks. They survive reboots, system updates, even unplugging the console entirely.
The console can hold several games in this state simultaneously. Xbox 360 and One titles are lighter on the buffer, so more of them fit. Series-native games take up more room.
Where it breaks down is online play. The moment your console goes into low-power mode, any server connection the game had drops. The server doesn’t hold your spot. When Quick Resume brings the game back up, the client is trying to restore a session that the server stopped caring about some time ago. The two can’t sync, and you get the frozen lobby, the dropped connection, or the error screen.
It’s not a software bug exactly. The feature and the game are just working from different assumptions.
How to Remove a Game from Quick Resume
During a session:
Hit the Xbox Guide button, the glowing logo at the centre of your controller. The Guide opens with your game tile sitting at the top. Press the Menu button, which is the small button with three horizontal lines on it. Choose “Quit.” Done. The suspended state clears, and next time you open that game, it boots from the beginning.
From your game library:
Open the Guide and go to “My games and apps.” Inside the Groups section, there’s a group called “Quick Resume.” Every title currently holding a saved state lives here. Find the one you want to clear, press Menu, and select “Remove from Quick Resume.”
Worth knowing: neither of these is permanent. The next time you switch away from that game without quitting, Quick Resume starts saving it again. If you’re playing online games, quitting before you close out needs to become a habit rather than a one-time fix.
Which Games Cause the Most Problems
Some games have a consistently poor history with Quick Resume. Not all online games break, but the ones that need server authentication at launch rather than at reconnection are the most likely offenders.
Games like Call of Duty, EA FC, Destiny 2, Fortnite, PUBG, and Halo Infinite are common examples because they rely heavily on live server state and tend to be less forgiving when resumed mid-session. The session gets suspended, the server moves on, the game can’t reconcile the difference when you come back. A lot of titles will at least drop you back to the main menu cleanly. Some just freeze.
Death Stranding had a more severe version of this in late 2024. Loading the game through Quick Resume actually disabled saving entirely until you fully quit and relaunched from scratch. That’s a different category of problem, because you’re not just dealing with a dropped session. Actual progress can disappear.
Games that patch often carry some risk too, even if they’re single-player. A patch landing while a game is suspended can create a mismatch between the saved state and the new build. Crashes on resume. The safest move with heavy-update titles is to quit before stepping away, especially around known patch windows.
Where Quick Resume Works Best
For a lot of games, Quick Resume is one of the better console features to come out in recent years. Genuinely.
Story games are where it shines. RPGs, narrative adventures, open-world games, puzzle games, anything you play in long offline sessions. Switching to a second game for an hour and coming back to find your first game mid-cutscene is something that sounds minor until it becomes part of your daily routine. PlayStation 5’s rest mode does something similar but doesn’t hold as many titles simultaneously or keep states as reliably across major breaks.
Backwards-compatible titles tend to work well too. Older games don’t have the server authentication demands of modern online titles, so Quick Resume handles them without much friction.
The rule isn’t complicated. Single-player or offline? Leave Quick Resume running. Anything that needs a server to function? Quit properly before you go.
Why Online Games Often Need a Restart
Think about any online product or service you use across multiple devices and tabs. Some platforms reload cleanly when you come back after an extended break, picking up your last state without any intervention. Others, especially those built around live sessions or real-time data, require you to start fresh. When you browse the game selection on BetandPlay, the page reloads your options cleanly each time because it’s not session-dependent in a way that breaks on reconnect. Quick Resume tries to do the same thing at a game-state level, and it works fine when the game was designed to survive a dropped connection. When it wasn’t, you’re asking the feature to do something it was never built for.
Some developers opted their games out of Quick Resume at the engine level. Rocket League is the most cited example. The game just doesn’t enter the suspended state. Overwatch 2 handles it differently, letting the game resume but prompting a server reconnection from the menu rather than trying to drop you back into a live match. When a studio accounts for this, the experience stays clean. When they don’t, you get the mess.
Why Some Apps Reconnect More Cleanly
Most people don’t realise how many titles they’ve got sitting in the suspended queue until they go looking. It piles up faster than expected.
There’s a widely reported issue where too many games in Quick Resume can throttle active download speeds. A lot of Xbox players have found that clearing the queue before a big download makes a noticeable difference. It’s not fully confirmed as a consistent effect, but it’s worth doing anyway just as maintenance.
Go into “My games and apps,” open the Quick Resume group, and clear anything you’ve finished or aren’t actively rotating. Takes two minutes. Keeps the queue lean and stops old suspended states from hanging around, creating potential conflicts with game updates.
Use Quick Resume Selectively
A system-wide toggle to disable Quick Resume entirely doesn’t exist yet. It’s one of the most-requested features from Xbox users, and Microsoft has signalled awareness of the gap without committing to a timeline for it.
The workaround isn’t complicated once you’re used to it. Quit online games before stepping away. Let Quick Resume run for everything else. Trim the suspended list periodically. That combination covers the main failure cases and lets the feature do what it actually does well.
Quick Resume at its best is a genuinely good idea. The discipline around when not to use it is what most guides skip over.
