{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/10/2026 3:25:20 AM
1
PC (Mouse & Keyboard): Movement stops after pressing Shift (Sprint) — can still aim/shoot/chat
[b]Platform[/b]: PC / Steam
[b]Description:[/b]
When I launch into Destiny 2, everything works normally on mouse and keyboard and I can move around without any issues. However, the moment I press **SHIFT** (sprint), I immediately lose the ability to move using WASD.
After pressing SHIFT:
- My character “budges” like it wants to move, but does not actually move.
- I can still:
- Turn/aim with mouse
- Shoot
- Throw grenades / use abilities
- Use menus
- Use text chat normally
- I just cannot move.
This happens every time and makes the game unplayable.
[b]Steps to Reproduce:[/b]
1. Launch Destiny 2 on PC using mouse and keyboard
2. Load into any activity (Tower, patrol, etc.)
3. Move normally with WASD (works fine)
4. Press SHIFT
5. Movement stops immediately (WASD no longer moves the character)
[b]Expected Result:[/b]
Pressing SHIFT should enable sprint (or whatever SHIFT is bound to) and movement should continue normally.
[b]Actual Result:[/b]
Pressing SHIFT causes movement to stop. Character may “budge,” but does not move.
[b]Troubleshooting Already Tried:[/b]
- Confirmed SHIFT is not double-bound to another action
- Reset keybinds to default
- Verified Sticky Keys is off
- Confirmed Logitech G Hub is up to date
- Uninstalled Logitech G Hub and tested without it (issue still occurs)
- Uninstalled and reinstalled Destiny 2 (issue still occurs)
- Rebound Toggle Sprint to another key: sprint works on the new key, but pressing SHIFT still causes movement to stop
- Tested with a controller: controller movement works normally
- Switched back to a keyboard/mouse: issue returns (movement stops after pressing SHIFT)
- SHIFT key is not physically stuck (typing in chat works normally)
[b]Additional Notes:[/b]
- Input is mouse and keyboard, not a controller.
- If there’s a known conflict with any Windows accessibility setting, overlay, or third-party input software, I’m happy to test.
- Appears specific to keyboard input; controller unaffected; SHIFT keypress triggers the movement lock regardless of sprint binding.
-
1 ReplyHello there, Thank you for reaching out. Below is a set of steps that might help resolve this 1. Make sure Shift is truly unbound in Destiny 2 You’ve moved Sprint to another key, but Shift may still exist as a secondary bind or in another category. Go to Settings → Keyboard & Mouse → Key Mapping. For every section (Gameplay, Vehicle, Menu, etc.): Click every action that shows Left Shift / Shift as Primary or Secondary and press Delete/Backspace to clear it entirely. Apply changes, return to the game, do not press Shift at all, and test: Move with WASD for 30+ seconds. Then tap Caps Lock (since the internal repro mentions it too) and see if that also kills movement. If WASD dies even when Shift has no binding, that’s a strong sign of an engine/input bug. 2. Completely reset Destiny 2’s local config Resetting in-game doesn’t always purge a bad config. Exit Destiny 2 and Steam. Go to (by default): C:\Users\<YourUser>\AppData\Roaming\Bungie\DestinyPC\prefs\ Rename cvars.xml to something like cvars_backup.xml. Relaunch Destiny 2: It will regenerate a fresh cvars.xml. Leave controls at default and immediately test: move with WASD, then press Shift once. If the problem disappears with a fresh config, your old cvars.xml was corrupted; keep the new one and re-set your settings manually. 3. Turn off Steam Input and overlays for Destiny 2 If Steam has an old custom layout where Shift switches to another action set, it can “turn off” WASD without you realizing. In Steam, right-click Destiny 2 → Properties → Controller: Set Override for Destiny 2 to “Disable Steam Input”. In General tab: Turn off Steam Overlay for this game. If you ever used a Steam Keyboard Layout: Go to Steam → Settings → Controller → Desktop Layout and Reset to default. Relaunch Destiny 2 and test again. 4. Kill all third-party input layers and try a plain keyboard Even if you uninstalled G Hub, other layers can still hook Shift: Temporarily exit/disable: Razer Synapse / Corsair iCUE / SteelSeries GG, AutoHotkey, Overwolf, MSI Afterburner overlays, Discord overlay, Nvidia overlay, etc. Plug in a different basic USB keyboard (no macros, no software) into a different USB port. Reboot, launch Destiny 2, test with the clean keyboard. If it only happens with one specific keyboard or when a certain app is running, that’s your conflict. 5. Double-check Windows accessibility & keyboard behavior You already checked Sticky Keys, but two more things can silently eat inputs when Shift is pressed: Windows Settings → Accessibility → Keyboard: Make sure Sticky Keys, Filter Keys, and Toggle Keys are all Off. Click each and turn off “Allow the shortcut key to start …”. In a blank Notepad window: Hold Shift and press WASD repeatedly for a few seconds. Confirm all letters appear normally and don’t “lock up” after pressing Shift. If Windows itself stops seeing WASD correctly after Shift, you’ve got a system-level keyboard issue. 6. Hard isolation test: new Windows user profile This clears per-user hooks and configs without touching your main setup. Create a new local Windows account. Log into that account, install/launch Steam, log in, and install Destiny 2 (or copy library and re-discover). Without installing any peripheral software, launch Destiny 2 and test the Shift behavior. If it still happens in a clean profile with a plain keyboard and a fresh cvars.xml, it’s almost certainly a game bug, not your PC. If it goes away, something in your main Windows user profile (input remapper, registry tweak, old driver) is the issue.
