BlackWidow V3 Pro - Issues with Windows User Switching | Razer Insider

BlackWidow V3 Pro - Issues with Windows User Switching


I recently purchased a couple of BlackWidow V3 Wireless Keyboards and started having desktop issues when switching user profiles in Windows 10. Only happens when I switch users without signing out (meaning apps are open on multiple accounts). The system seems to get stuck in trying to load the windows task bar on the user I am switching to, it remains in a system busy state and I am unable to use the profile. I now have to go to task manager and signout from the account.

The current workaround is to sign out of each user profile and only sign in to one account at a time.

This is happening on both BW Keyboards I purchased and on two different PCs. Other brand keyboards does not cause this issue

Troubleshooting steps already performed:
- clean reinstall of Synapse and drivers
- windows sfc scan and update
- removed Synapse and used generic windows drivers
- tried different usb ports and switched connections between wireless and wired

Anyone else experiencing a similar issue?

A case is currently open with support and has been escalated.

This topic has been closed for comments

11 Replies

Userlevel 7
This is a general problem with fast-user switching. The configuration of the product is unique and set for the logged-in user. The driver is highly likely stuck trying to communicate with the previous user's Synapse 3 to load the profiles. I'd appreciate it if you can send me the ticket number so I can monitor it. Do send that over via PM.

I'll keep the thread open for now.
Hello and good evening.

My husband and I recently purchased a BlackWidow V3 as well. When we made a second user profile for me, the profile would not load if we were still signed in to my husband's profile. Signing out or removing the keyboard's USB cable seems to load either profile with no problem.

Has there been any movement with a solution?
Hello, not much movement from Support for my case. They are offering me a hardware replacement which obviously will not resolve the issue. I would suggest for you to submit a case to get more attention on the problem and hopefully they fix the firmware on the device. This is one of the most expensive keyboards out there and very frustrating that it cant handle basic Windows functionalities.
This issue has been discussed on a few threads, but I haven't heard of a fix yet.

On this thread, someone 'fixed' the issue with a work around to go into Device Manager and disable all the 'HID compliant' devices.
myklally


Anyone else experiencing a similar issue?

A case is currently open with support and has been escalated.

@myklally Has there been any movement in your ticket?
I am experiencing the same thing with a Ornata V2 keyboard.
I have this same problem with both my Naga Pro mouse and my Huntsman TE keyboard. Through much trial and error, I narrowed it down to those 2 specific pieces of hardware.

[Edit] I should point out that the problem occurs with either one of these connected. When BOTH are connected, the problem is worse. Logging out before logging into a different account (slow user switching) will sometimes, not always, cause the same issue.[/Edit]

It is really irritating to spend this much money on (supposedly) quality peripherals only to be limited in my computing experience by (obviously) inferior products. Fast user switching is one of the hallmarks of Windows, yet Razer cannot seem to bring themselves to support it.
Has there been any updates on this. Just bought a mouse an keyboard and I'm having this problem.
I though it was a computer issue and did two fresh windows installs then found these posts.
Progress3210
Has there been any updates on this. Just bought a mouse an keyboard and I'm having this problem.
I though it was a computer issue and did two fresh windows installs then found these posts.


I have just been working with Razer support for this issue on my Huntsman TE & Naga Pro. After many emails, I got these responses for each device.

Huntsman TE: "
We wanted to let you know that we have managed to identify the cause of the issue that you have reported.


Due to the complexity and the work that needs to be done, we are unable to provide an estimate of when you can expect a fix. However, once a fix has been identified, this will be released in a future software update."

Naga Pro: "We wanted to let you know that we have managed to identify the cause of the issue that you have reported.

The issue is present on chroma keyboards and mice since Razer mice and keyboard functionality via custom binds. Razer is aware of the issue and will likely roll out the via software update.

Due to the complexity and the work that needs to be done, we are unable to provide an estimate of when you can expect a fix. However, once a fix has been identified, this will be released in a future software update. "

So... looks like we just have to wait until they deem this an issue worth rewriting all their software for.
Encino_Stan
@myklally Has there been any movement in your ticket?
I am experiencing the same thing with a Ornata V2 keyboard.

I don't think this is priority in their part. Quite disappointing for a very expensive product where their software is riddled with issues.
Encino_Stan
@myklally Has there been any movement in your ticket?
I am experiencing the same thing with a Ornata V2 keyboard.

Nope. They closed the ticket and saying the fix will be part of a later update. I dont see them actually fixing this anytime soon. Quite disappointing for a very expensive product.
Just something to keep an eye on... If it bugs out when you first log in, turn off fast-startup. Razer software doesn't obey windows rules.
This is what got from Razer late July.

[indent]"We would like to inform you that your reported concern has been successfully replicated by our team. Please look forward to a future update to resolve the issue. We currently have no ETA on when the fix will be rolled out, however, we acknowledge that the issue is present and are working towards developing a fix.
"In the meantime, the only workaround is to ensure that only one Windows User is active when using the Razer device.
"The fix will likely be in the form of a firmware update, so we advise to check the product's support page for the firmware update once it becomes available.
"We will now be archiving your case."[/indent]