Keyboard not responding in Valorant game | Razer Insider
Skip to main content
Question

Keyboard not responding in Valorant game

  • June 22, 2025
  • 3 replies
  • 380 views
C

Hello,

I am using Huntsman v3pro TKL. 

 

 I am facing the problem starting today, when playing game Valorant, after 1or 2 mins, the whole keyboard just not responding at all. And before yesterday , everything was fine.  and when i quit the game, keyborad s back online. 

 

I didn’t do any software update, or game update, or synapse update or anything. it just suddently not working in the game. and back on desktop. technically it shouldn’t be.  Really really comfused.  And when in the game, couldn’t even alt+tab to shift to desktop, i have to force restart the pc. 

 

When I using my backup keyboard(not razer)to test,  20mins, everything seems fine. so it might be the conflict between the razer software or something idk.  or the key conflict or hotkey locked in game maybe

 

Please share any ideas. 

 

3 Replies

sharpSlimyGreenvision591

Happened to me as well, currently I’m not playing Valorant atm because of this annoying bug that just happened to me last night I was in range suddenly my keyboard stopped working. I’ve already tried everything but the issue only persist on Valorant not on any other games. If I run Valorant keyboards completely stops I wouldn’t be able to tab out all of the keys are not working, I had to manually use the mouse just to exit Valorant and be able to use my keyboard again. I’m using the Huntsman V3 pro mini.

dailybookSaddleBrown307

Hey guys, I also have a huntsman v3 mini and I found going into task manager and completely closing razer engine (13) or could be (14) fixes the issue, just do it before opening valorant. Once you open valorant try typing in party chat to test if it’s working. There was a couple times it stopped inputting but I hard shut down my pc and just turned it on and loaded valorant without touching anything and it works. 

dailybookSaddleBrown307

I was going through twitter and apparently this issue just popped up so I’m assuming there’s an issue with razer drivers and vanguard right now, hopefully they will fix it but that’s the only fix I have right now 

CookiesCookie settingsAccessibility statement