Editorial review: 4 October 2026 UTC. This guide was checked against the linked publisher documentation. Software downloads, signature inspection, installation, game compatibility tests and performance benchmarks were not performed for this review.
If MSI Afterburner‘s overlay is missing, first check whether Afterburner has live sensor data, whether those sensors are selected for the on-screen display, and whether RivaTuner Statistics Server (RTSS) is running. A missing sensor and a missing overlay are different problems. If only one game fails, check that game’s overlay policy before changing detection settings.
Start with the symptom
| What you see | Check first | What it distinguishes |
|---|---|---|
| No readings in Afterburner’s hardware monitor | Selected sensor, GPU identity and driver recognition | Data collection, before RTSS rendering |
| Graphs work; nothing appears in any game | Show in On-Screen Display, RTSS running, OSD visibility and hotkey | Data exists but display setup may be incomplete |
| Only one game lacks the overlay | Publisher restrictions and the actual game’s RTSS profile | Game-specific compatibility or configuration |
| Temperature appears; average FPS or 1% low does not | Benchmark recording and selected statistics | A recording-dependent statistic, rather than total overlay failure |
| Overlay appears but is unreadable | RTSS position, zoom and background contrast | Presentation, rather than missing monitoring data |
1. Check your versions and official source
On this review date, MSI’s Afterburner page offers 4.6.6 Final and 4.6.7 Beta, both labelled September 2026. The Guru3D Afterburner page separately describes 4.6.7 Beta 3, build 17352, and retains a 4.6.5 Final button. Its button wording also mixes “Stable” with “Beta.” Treat the explicitly labelled beta as a beta; these pages do not show an identical final-version selection.
Use MSI’s current final channel as the normal starting point, unless the release notes identify a specific fix you need in a beta. Guru3D notes that beta builds can expire. The RTSS publisher page currently offers 7.3.7 Final. A standalone RTSS version and the version bundled with a particular Afterburner installer are not automatically identical; inspect your installed versions.
MSI says Afterburner is free and supports graphics cards from multiple brands; Guru3D lists RTSS as free freeware for Windows. Neither statement promises that every sensor or tuning function exists on every laptop or GPU. Freeware is not an open-source license. Obtain the software through MSI or Guru3D, using our Afterburner source guide and the official-download checklist to distinguish publisher links from advertisements.
2. Confirm that Afterburner can collect the statistic
Open the hardware-monitor window and look for a changing reading for the statistic you want. If the graph is absent, enable that entry in Settings > Monitoring. If GPU1 and GPU2 appear, open the Information window to identify the actual adapters; their numbering alone does not prove which is the discrete GPU.
If the expected adapter is not recognized after a hardware or driver change, check its driver and restart Windows as described in MSI’s monitoring walkthrough. Do not try to repair an unavailable temperature sensor by moving the overlay. Monitoring capabilities depend on hardware and driver support, and some readings require an appropriate monitoring source or plugin.
Leave voltage, clock and fan controls alone while diagnosing the display. They are separate from selecting monitoring statistics. Record the installed Afterburner, RTSS, GPU driver and Windows versions before changing anything so that an update-related problem has a reproducible starting point.
3. Select a small OSD and apply it
- Open Afterburner Settings > Monitoring.
- Select one available statistic, such as GPU temperature, and enable its monitoring checkmark.
- Enable Show in On-Screen Display for that statistic. Monitoring a graph alone does not put it into the game overlay.
- Click Apply. Add framerate or frametime after the first statistic works, rather than configuring a large layout at once.
- Open Settings > On-Screen Display and assign a toggle hotkey that does not conflict with the game. Close Settings with OK before trying the hotkey.
MSI’s walkthrough uses Scroll Lock as an example; it is not a mandatory key or a promise that every installation uses it by default. The documented global hotkeys do not operate while Afterburner’s Settings window remains open. Check whether a previous toggle simply hid the display.
4. Confirm that RTSS is running and showing the OSD
Afterburner supplies monitoring data; RTSS draws the in-game display. Both need to be running for this workflow. Open RTSS from its system-tray icon or the More button in Afterburner’s On-Screen Display settings. If RTSS was omitted from installation, configure the publisher’s RTSS component before expecting the overlay to work.
Check the OSD visibility control and the profile that applies to the actual game executable, rather than only its launcher. A per-game profile can differ from the global one. In the RTSS developer’s forum explanation, disabling application detection disables the relevant application functionality; a profile set to None is therefore a meaningful clue.
For a game that permits RTSS, restore its normal detection configuration and retest. Raising detection or enabling stealth options is not a universal fix. Do not use aggressive hooking to defeat a game’s restrictions or disable anti-cheat/security software to make an overlay appear.
Once it displays, adjust position and zoom so it stays inside the game area. A background fill can improve contrast over bright scenes. RTSS’s OverlayEditor can preview layout without a running game, but a preview is not proof that injection works in that game.
5. Understand average FPS and 1% low
MSI’s walkthrough documents benchmark recording as necessary for its average-framerate and 1% low statistics to update. Assign Begin and End recording hotkeys on the Benchmark tab, apply them and close Settings. It also describes checking Enable Benchmark Mode in RTSS Setup.
Start a new recording for each comparable run. A retained average from an earlier scene is not a measurement of the scene now on screen. Missing average FPS alone does not justify reinstalling the entire overlay. These are setup instructions from the publisher; this review supplies no measured FPS, frametime or 1% low result.
6. If only one game fails, check its rules
Bungie’s Destiny 2 compatibility policy is a concrete example: hardware monitors can run alongside the game, while overlay functionality is restricted. It distinguishes incompatible features from a blanket ban on common applications, and still reserves enforcement for violations of its rules. Do not translate this into permission to bypass the restriction.
Use a permitted in-game FPS counter or monitor readings outside the game, such as on a second screen. MSI also describes the Windows Game Bar Performance widget as an alternative in some games. An alternative overlay still needs the game’s permission and display-mode compatibility; it is not a guarantee for every title.
Guru3D lists both anti-cheat restrictions and conflicts with other overlay software among RTSS limitations. For a permitted game, temporarily close optional competing overlays one at a time and record the result. Do not assume that stacking another injector, including a modding tool, will repair RTSS.
7. Reinstall only after preserving the useful evidence
If a previously working setup stopped after an update, record the last working versions and screenshots of monitoring selections, hotkeys and game profiles. Guru3D recommends a clean removal of Afterburner and RTSS, including profiles, for some post-update failures. Removing profiles can also discard tuning settings; preserve anything you need before following that advice.
For installation blocked because Afterburner is already running, MSI describes disabling its Start with Windows setting, saving, restarting and installing again. Keep this separate from changing GPU tuning. After a clean installation, establish a minimal monitoring-only configuration before restoring old profiles that might reintroduce the issue.
If it still fails, prepare a useful support record: game and executable, allowed overlay policy, renderer if known, installed versions, whether the hardware monitor works, and whether a second permitted game behaves differently. That evidence narrows the problem more than the statement “the overlay does not work.”
