BLACKWIDOW V3 TKL can't be configured on SYNAPSE | Razer Insider
Solved

BLACKWIDOW V3 TKL can't be configured on SYNAPSE

  • 26 September 2023
  • 16 replies
  • 311 views

Userlevel 1

Hey comunity, I bought Keyboard BLACKWIDOW V3 TKL (yellow switch) (RZ03-03492300-R311), I can use normaly but can’t configure on Synapse. I test it on a personal computer and laptop, i got the same problem.

Anyone have same problem or can be a factory problem.

 

 

icon

Best answer by FiszPL 29 September 2023, 10:17

View original

16 Replies

i am having the same issue even with a different system

I’ve got the same problem: tested in three diferent machines (win 7, win 10 & win 11) and got similar results: the keyboard seems to work fine, but Synapse does not want to do anything with it. I got the same results as the original poster. I’ve uninstalled it, deleted devices in Device Manager, did several reboots with the keyboard connected to different USB ports and got no result.

If I don’t have a solution soon, I will have to return it and replace it by a Ducky or something similar.

Im having the same issue please let me know if you find a solution 

Userlevel 7

The download icon is stucked? Can you try via different internet connection? Or trying to disable Antivirus / firewall software for a while?

You can also try to clean reinstall Synapse - in some cases it helps:

  1. Uninstall Synapse
  2. Download & run this tool: https://rzr.to/Tf53xj to remove any razer drivers/leftovers
  3. Then restart your PC
  4. After reboot install Synapse again (as administrator).
Userlevel 1

I have the same issue. Followed the driver removal tool steps, performed a clean install of Win11, tried multiple USB ports, no joy.

Interestingly, I have a Razer Atheris mouse too. If I leave the Blackwidow v3 TLK disconnected and install Synapse with the Atheris only connected, it works fine. As soon as I connect the keyboard it downloads a small update which then breaks both, just showing greyed out with the loading circle frozen.

Userlevel 7

Seems to be some Synapse bug.

@Razer.Aero@Razer.Zionzedd 

 

Userlevel 1

Definitely a Synapse bug, happening on a completely different machine too. I've raised a support ticket

I bought a Blackwidow v3 TKL and Viper mini 1 year ago and all works fine. But I have a new pc, and now I have the same shitty error.  In the old one, both works fine until today…

The evento viewers said that id Synapse 3 Web Service s fault.

 

How can we do? :(

Userlevel 1

Hi all, looks like a fix has been pushed. synapse updated itself this morning and everything works fine now!

If you've got this issue just check manually for updates if it hasn't automatically updated.

Hi all, looks like a fix has been pushed. synapse updated itself this morning and everything works fine now!

If you've got this issue just check manually for updates if it hasn't automatically updated.

I didn't find any update regarding this. I mean I thought it was a windows problem so I reinstalled everything afresh and then tried one by one. I have a Viper Mini and Viper Ultimate. After installing the software these devices are recognised without any issue and I can change everything. But the moment I plug in BlackWidow V3 TKL (Yellow Switches)....*Bam...gone…

 

A weird update which I can't cancel cuz if I do the device doesn't show up on the main page. And the moment I do, all the devices go into a weird loop.

 

And if you say that there's an update being pushed out regarding this, if it's a regional time specific (IST for me), then I haven't received it yet.

Userlevel 1

Hi all, looks like a fix has been pushed. synapse updated itself this morning and everything works fine now!

If you've got this issue just check manually for updates if it hasn't automatically updated.

It’s thrue synapse got a updated and it was fixed 😃

 

So, am I the only one in the community who still has this issue. I followed every step mentioned here. As much as reinstalling windows all together but still I am facing this issue. Tried multiple ports. When I connect the mice individually it works all fine. But the moment I connect the keyboard everything goes into this loop.

 

So, I really don’t know what am I doing wrong here. I mean I’m not saying that the community is wrong in terms of update but I’ve downloaded the latest software from their own website and still the issue persists. And when I check for updates (which ideally I shouldn’t considering I’ve downloaded the software directly from their own website), it says no update indicated by a green check mark.

Razer Synapse Version: 2023092B.

BlackWidow V3 TKL (Yellow Switches) Device Version: 1.02.00

So, am I the only one in the community who still has this issue. I followed every step mentioned here. As much as reinstalling windows all together but still I am facing this issue. Tried multiple ports. When I connect the mice individually it works all fine. But the moment I connect the keyboard everything goes into this loop.

 

So, I really don’t know what am I doing wrong here. I mean I’m not saying that the community is wrong in terms of update but I’ve downloaded the latest software from their own website and still the issue persists. And when I check for updates (which ideally I shouldn’t considering I’ve downloaded the software directly from their own website), it says no update indicated by a green check mark.

Razer Synapse Version: 2023092B.

BlackWidow V3 TKL (Yellow Switches) Device Version: 1.02.00

Glad I’m not the only one… I’ve checked for updates and reinstalled etc etc… What a dissapointment after spending several hundred $ on a new setup...

 

Userlevel 1

If you go into settings cog > about, what does the version show? Mine is 3.8.930.92719

I'm not sure what the random update changed, because the driver in hardware manager is still the same too 10.0.15063.0

I’m glad that I’m not the only one with this issue. Just bought my first mechanical keyboard (Blackwidow v3, with yellow switches (if that matters)) along with a mouse (Basilisk v3). Both work if plugged in, including the standard hypershift keys. The keyboard is greyed out, and cannot be configured.

Strangely, if I restart with both M+KB plugged in, both end up greyed out after a system (or Synapse) restart. I can unplug/plug in the mouse to fix the mouse, but this doesn’t work for keyboard. If I ONLY have the mouse plugged in, the mouse is configurable after a system/program restart, and never gets greyed out. This doesn’t work for the keyboard.

Both of their RGB lights still work by default, cycling through colors (keyboard) or using what I chose (mouse). I can configure RGB using another program (SignalRGB, which needs razer software closed). The mouse keeps its configurations (on-board memory) even after I close the razer software (aside from the RGB, which is then handled by SignalRGB).


 

There has been a tiny handful of times the keyboard wasn’t greyed out after I did a full reinstall, or ran the repair utility. I can’t reliably have this happen, though. Upon PC restarting, or closing/re-opening the software, or re-plugging the keyboard -- the keyboard gets greyed out again. Even when it wasn’t greyed out, the configuration I made to hypershift keys didn’t seem to work (could just be user error).

I’ve tried uninstalling/reinstalling synapse, re-downloading synapse each time, running it as admin, clearing all drivers manually (and automatically with Driver Cleaner .bat), cleaning out program files/program data/etc folders, clearing the registry of anything razer related, tried installing all optional modules, tried installing no optional modules, tried the repair utility, tried every usb port, tried updating firmware (keyboard was up to date, mouse update didn’t change anything), and did all of the previous steps with: Windows defender on (with exceptions for all razer stuff), windows defender turned off, windows update disabled, automatic downloading of drivers disabled, and even a new install of windows. I’ve tried some of these things many, MANY times over the course of a full day (minus firmware/fresh install of windows) but nothing reliably works to have keyboard customizable.

 

During a ‘fresh install’ of Synapse, when I plug in my mouse it gets detected, and an update pops up in Synapse. I download it, and the mouse is configurable. When I do the same for my keyboard, both Synapse and windows tell me it has to restart to finish installation. Upon the update finishing, keyboard is greyed out (and the mouse too, even though it wasn’t before the keyboard update). Upon restarting, both are greyed out (and as usual, re-plugging the mouse fixes just the mouse).

 

I hope that it’s a software issue that can be fixed, as I otherwise like this keyboard (and having to use my old one while this one is shipped in the mail is gonna be miserable).


 

OS: Windows 11

Razer Synapse has two numbers:
In the “About” section of Synapse (and windows Control Panel): 3.8.930.92719
In the “updates” section of Razer Central: 20231003

Razer Central (in the about section) is version 7.13.0.628

Razer Firmware updater says that both M+KB are version 1.02.00

 

Device manager lists both M+KB as version 10.0.15063.0

If I then click Driver Details, here’s what it additionally says:

Razer Basilisk:
mouclass.sys & mouhid.sys: 10.0.22621.1 (WinBuild.160101.0800)
RzDev_0099.sys: (1.0.0.71)

 

Blackwidow V3 Tenkeyless
kbdclass.sys & kbdhid.sys: 10.0.22621.1 (WinBuild.160101.0800)
RzDev_0a24.sys): 1.0.0.68

The blackwidow is also in the mouse drivers section for some reason? It’s additional details are the same as the Basilisk V3 (shows the same 3 .sys files). Maybe Synapse is trying to read the “mouse” drivers for the keyboard, gets confused, and greys it out? (Is that even possible?)

 

 

I’m glad that I’m not the only one with this issue. Just bought my first mechanical keyboard (Blackwidow v3, with yellow switches (if that matters)) along with a mouse (Basilisk v3). Both work if plugged in, including the standard hypershift keys. The keyboard is greyed out, and cannot be configured.

Strangely, if I restart with both M+KB plugged in, both end up greyed out after a system (or Synapse) restart. I can unplug/plug in the mouse to fix the mouse, but this doesn’t work for keyboard. If I ONLY have the mouse plugged in, the mouse is configurable after a system/program restart, and never gets greyed out. This doesn’t work for the keyboard.

Both of their RGB lights still work by default, cycling through colors (keyboard) or using what I chose (mouse). I can configure RGB using another program (SignalRGB, which needs razer software closed). The mouse keeps its configurations (on-board memory) even after I close the razer software (aside from the RGB, which is then handled by SignalRGB).


 

There has been a tiny handful of times the keyboard wasn’t greyed out after I did a full reinstall, or ran the repair utility. I can’t reliably have this happen, though. Upon PC restarting, or closing/re-opening the software, or re-plugging the keyboard -- the keyboard gets greyed out again. Even when it wasn’t greyed out, the configuration I made to hypershift keys didn’t seem to work (could just be user error).

I’ve tried uninstalling/reinstalling synapse, re-downloading synapse each time, running it as admin, clearing all drivers manually (and automatically with Driver Cleaner .bat), cleaning out program files/program data/etc folders, clearing the registry of anything razer related, tried installing all optional modules, tried installing no optional modules, tried the repair utility, tried every usb port, tried updating firmware (keyboard was up to date, mouse update didn’t change anything), and did all of the previous steps with: Windows defender on (with exceptions for all razer stuff), windows defender turned off, windows update disabled, automatic downloading of drivers disabled, and even a new install of windows. I’ve tried some of these things many, MANY times over the course of a full day (minus firmware/fresh install of windows) but nothing reliably works to have keyboard customizable.

 

During a ‘fresh install’ of Synapse, when I plug in my mouse it gets detected, and an update pops up in Synapse. I download it, and the mouse is configurable. When I do the same for my keyboard, both Synapse and windows tell me it has to restart to finish installation. Upon the update finishing, keyboard is greyed out (and the mouse too, even though it wasn’t before the keyboard update). Upon restarting, both are greyed out (and as usual, re-plugging the mouse fixes just the mouse).

 

I hope that it’s a software issue that can be fixed, as I otherwise like this keyboard (and having to use my old one while this one is shipped in the mail is gonna be miserable).


 

OS: Windows 11

Razer Synapse has two numbers:
In the “About” section of Synapse (and windows Control Panel): 3.8.930.92719
In the “updates” section of Razer Central: 20231003

Razer Central (in the about section) is version 7.13.0.628

Razer Firmware updater says that both M+KB are version 1.02.00

 

Device manager lists both M+KB as version 10.0.15063.0

If I then click Driver Details, here’s what it additionally says:

Razer Basilisk:
mouclass.sys & mouhid.sys: 10.0.22621.1 (WinBuild.160101.0800)
RzDev_0099.sys: (1.0.0.71)

 

Blackwidow V3 Tenkeyless
kbdclass.sys & kbdhid.sys: 10.0.22621.1 (WinBuild.160101.0800)
RzDev_0a24.sys): 1.0.0.68

The blackwidow is also in the mouse drivers section for some reason? It’s additional details are the same as the Basilisk V3 (shows the same 3 .sys files). Maybe Synapse is trying to read the “mouse” drivers for the keyboard, gets confused, and greys it out? (Is that even possible?)

 

 

I actually returned my V3 tkl yesterday and picked up the Blackwidow Mech Full-sized green switch (I actually like the clickyness lol, who woulda thought?!) and as soon as I plugged it in, everything worked perfectly. Definitely an issue with the V3. Whether its on purpose to force people to exchange it for a more expensive keyboard, or just a random software glitch… who knows. But as soon as I got another razer keyboard, everything worked instantly without issue.

Reply