Timer Resolution Not Working? Why It Resets and How to Fix It

Published

On this page

If you set a low timer resolution and it snapped right back to 15.6ms — or a utility that used to work stopped doing anything on Windows 11 — nothing is broken. Windows changed how timer resolution is applied, and the old “set it once and close the app” approach no longer holds. This guide explains exactly why it resets and how to make a low timer actually stick during gameplay.

Timer Resolution Not Working? Why It Resets and How to Fix It

A raised timer only lasts as long as something keeps requesting it — close the app and Windows drops it back down.

Why timer resolution resets

The Windows timer resolution isn’t a permanent system setting you flip on. It’s a request. A program asks Windows for a finer timer (say 0.5ms), and Windows grants it — but only for as long as that program keeps the request alive. The moment the requesting process exits, Windows is free to raise the timer back toward the default 15.625ms to save power.

So if you opened a small utility, dragged the slider to 0.5ms, and closed it, the timer went back up the instant the window closed. It looked like it applied because the value was correct while the app was open — but nothing was holding it.

What changed on Windows 11

Older Windows versions treated a lowered timer as global: one app requesting 0.5ms lowered it for the whole system. Starting with Windows 10 2004 and continuing through Windows 11 and 24H2, Microsoft made the raised timer apply per-process, and only while that process is in the foreground.

That single change is why so many classic timer utilities look broken now:

  • The utility raises the timer, but only its own process gets 0.5ms.
  • Your game — a different process — still runs at the default timer unless it (or something covering it) requests the lower value.
  • Alt-tabbing or losing focus can drop the timer again.

The behavior isn’t a bug, and it isn’t reverting your setting out of spite. It’s the documented model. You just need something that requests the low timer continuously while your game is in focus. For the full background on how the timer affects input and frame pacing, see the ultimate guide to timer resolution for gaming.

Check your actual timer resolution

Before fixing anything, confirm what your timer is really doing right now:

  1. Download ClockRes from Microsoft Sysinternals.
  2. Open an elevated command prompt and run clockres.
  3. Read the three values it prints — Maximum, Minimum, and Current timer resolution.

The Current value is the one that matters. If it reads 15.625 ms while you expect 0.5ms, your requested timer isn’t being applied. If it reads 0.500 ms, something is actively holding it — check that it’s the right something. Tier1Timer shows this live current value in its window too, so you can watch it change in real time as you launch a game.

The fix: keep the request alive

Because the low timer only lasts while a process requests it, the fix is a program that stays resident and re-asserts 0.5ms continuously — not one you open and close. That’s exactly the gap Tier1Timer fills:

  • It requests your chosen timer resolution and holds it, so the value doesn’t drift back to 15.6ms.
  • Auto Mode applies the low timer when your game launches and reverts it when the game exits, so you’re not raising the timer during idle desktop use.
  • It displays the live current resolution, so you can verify with your own eyes that 0.5ms is actually active during a match — not just requested.

Set it once, leave it running (or let Auto Mode handle launches), and the timer stays where you put it.

If the timer still won’t drop

A few things can stop even a resident tool from reaching your target value:

  • Your hardware doesn’t expose 0.5ms. Run ClockRes and read the Maximum (finest) value it supports. If the minimum it lists is 1.0ms, that’s your floor — 0.5ms simply isn’t available on that platform.
  • Another app is fighting for the timer. Some browsers, media apps, and RGB software also request timer changes. Close background apps and re-check with ClockRes.
  • A power setting is interfering. Make sure Windows is on a high-performance power plan so the OS isn’t aggressively raising the timer to idle down cores.
  • You’re testing on the desktop, not in-game. With the per-process model, verify the current value while the game is running and focused, since that’s when it matters.

Does a lower timer actually help?

Once it’s applied and holding, a raised timer resolution samples input and schedules frames more often, which shows up as steadier frame pacing and more consistent input latency — smoother 1% lows, not a magic FPS jump. Test 0.5ms versus 1.0ms and keep whichever gives you the flatter frame times on your CPU. For the measurement side, see how to measure input lag.

Timer resolution “not working” almost always means the request stopped when an app closed, or the per-process Windows 11 model left your game on the default timer. Confirm the current value with ClockRes, use a resident tool that holds the request while you play, and check that your hardware actually supports the value you’re asking for. Do that and 0.5ms stays put where it counts.

Frequently asked questions

Why does my timer resolution keep resetting?

Because a raised timer resolution only lasts as long as the app that requested it is running. When that app closes — or on Windows 11 2004 and later, when its window loses focus — Windows drops the timer back toward the default 15.6ms. A tool you set once and closed will not hold the timer; you need a program that stays resident and re-requests the resolution continuously.

How do I check my current timer resolution?

Run Microsoft's Sysinternals ClockRes tool from an elevated command prompt — it prints the maximum, minimum, and current timer resolution. Tier1Timer also shows the live current value in its window. If the current resolution reads 15.625ms (or 1.0ms) when you expect 0.5ms, your requested timer is not being applied.

Does timer resolution work on Windows 11 24H2?

Yes, but Windows 11 (2004+) changed the behavior so a raised timer only applies to the process that requested it while it is in the foreground, rather than globally. This is why old set-and-forget utilities appear broken on 24H2. A resident tool that keeps the request alive restores a consistently low timer during gameplay.

What timer resolution should I set?

0.5ms is the common target on modern systems and is the lowest most hardware exposes. 1.0ms is the classic value and is still fine. Lower is not automatically better on every CPU — test both, watch your 1% lows and frame pacing, and keep whichever is more consistent. There is no benefit to values your hardware does not actually support.

Is it safe to leave timer resolution running all the time?

Yes. A raised timer resolution is a documented Windows setting, not a hack, and modern desktops handle a 0.5ms timer without meaningful power or heat cost while gaming. On laptops on battery it can slightly increase idle power draw, so a tool with Auto Mode that only raises the timer while a game is running is the tidiest setup.