What this section changes
Enlarges the driver queue for input devices so clicks and keystrokes are never held up waiting to be processed.
| Setting | What it does | Registry path |
|---|---|---|
| Mouse data queue size | Raises the buffer the driver holds mouse reports in from 100 to 150, at the class layer and at the HID layer below it. It does not shorten latency, and any wording that says it does is wrong. What it does is stop a high-rate mouse losing reports when the reading thread stalls for a moment. | HKLM\...\Services\mouclass + mouhid\Parameters\MouseDataQueueSize |
| Keyboard data queue size | Raises the buffer the driver holds key reports in from 100 to 150, at the class layer and at the HID layer below it. It does not shorten latency; it leaves headroom against dropped input. | HKLM\...\Services\kbdclass + kbdhid\Parameters\KeyboardDataQueueSize |
| Cap how long a stalled input hook blocks the mouse | Overlays and macro tools install input hooks that every keystroke passes through. If one stops responding Windows waits five seconds before ignoring it, and input freezes for that whole time. This cuts the wait to one second. A hook that merely slows down under heavy load can hit the same limit and be dropped — restarting that tool brings it back. | HKCU\Control Panel\Desktop\LowLevelHooksTimeout |
| Cut the key-repeat delay to the shortest step | Windows waits half a second before a held key starts repeating. This takes that wait down to the shortest step the API allows, 250 ms, and sets the repeat rate to the fastest. Be clear about what it is: pressing and releasing a key in a game never passes through any of this — the gain is in the console, in chat and in menus. If characters repeat too eagerly while typing, undo the card from the Fix page. | HKCU\Control Panel\Keyboard\KeyboardDelay + KeyboardSpeed |
Applying it
- Open w0a
- Go to the Regedit Tweaks page in the left menu
- Find this section, tick the settings you want, apply
Every setting is individually selectable — you are not required to apply a whole section.
Undoing it
Two ways, both of which work:
- Backups & Restore — puts back the checkpoint written before the change was applied. It
reverts what that group changed and touches nothing else.
- The Fix page — searched by symptom, writes the Windows default unconditionally. It does not
read a backup, so it works even if w0a's own backup file is gone.
The undo log lives at %ProgramData%\w0a\backup.json, outside your user profile.
The risk
Everything here is a documented value Windows supports; none of it is kernel-level and none of it is irreversible. The honest sentence is still this: a setting may have no measurable benefit for you. If you apply a change and feel no difference, you are probably right — these pages are not selling you a feeling, they are telling you what was changed.
If you want to measure it, the rule from reading the benchmark applies: change one thing at a time, and read the lows rather than the average.
Did this page help?
What was missing, or what did not work? We read every one of these.
If this page did not solve it, write to us — say which article you read, and we will fix the article.