Can't sprint with any gun equipped but can with gadgets and equipment.

Same issue. 

Yeah, me too, what is going on???

same issue. can only run with knife and gadgets

Have you found a fix for this?

I'm on PC and been experiencing the same thing for the last ~5 days. and I think found the source of the issue but idk how to fix it for PC / steam users.. heres what ive done

edit: issue is something is wrong with xbox series elite 2 controller configuration but I cant pinpoint the source (steam vs. bf6 vs. xbox accessory vs. windows vs. config files / firmware, etc). 

I've tried various solutions :

for all of the bullet points, In-game refers to the BF6 Firing Range (made testing easier). Note, you cannot test grenades in Firing Range.

• [failed] uninstall , reinstall game
• [failed] In-game, remapped my bf6 sprint to another button & tried to sprint 
• [failed] In-game,  remapped bf6 M&K key sprint. and tried to sprint
• [failed] deleted "PROFSAVE_profile" in C:\Users\%USERPROFILE%\Documents\Battlefield 6\settings\steam. This file sets all your special button config mapping and more in the game. It gets re-generated upon reboot. 
• [failed] attempted  https://steamcommunity.com/discussions/forum/1/1621726179577658947/
• [failed] attempted https://www.youtube.com/watch?v=1_-qom6bd0s&t=72s
• [partial success] While In-game, opened steam > manage bf6 > controller , and disabled steam input. Clicked back over to running game, & I could run with M&K but not controller. When restarting BF6, old behavior returned. success not very repeatable
• [partial success] disabled steam input, restarted the game. sprint worked, but shooting somehow became double mapped to R3 and right trigger. Thus, couldnt melee. All other actions seemed normal in game. In menus, the B button became RB and probably would have translated in a real game. 
•  [partial success] while in-game, changed current button layout from Official layout for BF6 - Gamepad  to Template Keyboard (WASD) and Mouse. This also was either completely working or completely not at random == not very repeatable.  Only enabled fully normal controls for M&K, did not work for controller. 
• [success] unplugging series elite 2 and using an xbox series controllers.

edit 2: the brutalist solution i found was to  change the following steps...

1.  change steam controller button layout from Official layout for BF6 - Gamepad  to Template Keyboard (WASD) and Mouse.
2. click edit layout then leave this open and start open bf6.
3. now, in Bf6, go into M&K infantry settings , and map all of those default M&K keybinds to the matching steam controller keybind. For example,  the steam controller Dpad left i mapped to '3' , Dpad up i mapped to '4', or steam controller Y button i mapped to 'scroll wheel up'. For something like crouch & prone, add an extra command and map the controller prone button to long press of z.
4. test

note, this will only work for infantry mapping. To map the rest (vehicles, menus, etc), you have to do a lot of cross matching / mapping to get close to the desired outcome. Super brutal. super janky but works for infantry only.

still exploring why the elite controller has this issue for me.

Anyone figure it out? Got the same issue  Even on my keyboard and mouse. 

I have the same issue. It occured mid game, and have been unable to sprint since. I have reinstalled the game twice now, reset every single option available in game and am no closer to being able to run with my gun in my hand. A knife and equipment let me sprint, but currently after 70h on the game I'm putting it away in the corner until this is resolved. This is a fundamental movement mechanic and I am extremely disadvantaged to the point where it is not an enjoyable experience. I hope this is resolved ASAP because if it isnt I probably wont return.

Nearly a month after this has been reported and still no fix, this for me is a game breaking bug that needs sorting >:(

I so far as backup my PC to a harddrive, reinstall windows on my SSD, booted with my SSD only connect, re-downloaded all the programs, and the error still occured..

I believe it's something with the cloud state of the game but there has been no solution as of yet.