Razer Lycosa Mirror Edition


Recommended Posts

Does anyone else have this keyboard, and major problems with it ?

i bought one a good few months back, and for the first month or so it was fine.

then keys stopped working, randomly.

id be playing a game or just typing and suddenly the D key would just go.

i then realised to fix this i needed to unplug it and plug it back in, then depending on the game restart it.

then i started having a problem where the keyboard wont turn on.

it happens at POST, which is really annoying if i need to load windows as i have grub and often find it boots into linux cause my keyboard cant do anything.

i have to hit the keyboard from the back a few times before itll start working.

and if i have the media keys set to a player i have installed, the keyboard has a habbit of randomly opening the player, and just skipping through my library.

so i went over to the razer site after realising the NORMAL lycosa's had all these problems and that you just had to send them your serial number, and if you fell in the range of serial's with the known problems, you got a replacement.

on the page i read about this, there were commnents from other mirror users with my exact problem, and someone from razer saying the mirror lycosa cant have the problem because it was produced after the problem was fixed.

evidently not the case.

i sent an email to razer, including my serial number, the fact it's a mirror, and the fact it's having all these problems.

this was about 3 or 4 months ago.

im yet to recieve anything back.

out of inpatience, i read up a fix for it (taking it apart and removing a screw that's in the way and causes the touchscreen to go mad), but it didnt change a thing.

infact ive done it twice, because i thought i mustve done something wrong the first time, but it still didnt work.

so now im stuck in a position where i cant send it back, and ive wasted ?70

as far as im concerned, no one should ever buy this keyboard.

it seems like a hit or miss as to whether yours is actually going to work properly!

:crazy::

/rant

Link to comment
https://www.neowin.net/forum/topic/815014-razer-lycosa-mirror-edition/
Share on other sites

I've had issues with Razers equipment not working at boot-up. I believe it has something to do with the very high power requirements that their stuff requests. They attempt to max the USB specification with almost everything they sell and at post when you have a few USB devices sharing the same host controller there are times where the amount of power being requested just isn't enough which causes their devices to not work at boot-up unless you unplug and plug them back in or deactivate and then reactivate them from device manager.

I've witnessed this the most with their 5.1 Surround Sound headsets and their Mice but I've heard of it happening with others on their Keyboards as-well and only at Post. I've personally had this happen on no less than 4 different Motherboards and 2 separate Laptops so I know this is an issue with Razers stuff.

Something to note. I get my Razer 5.1 Surround Sound headset to come on every single time at post if I leave its Blue LED lighting off.

I have the same keyboard they've had problems from the start, the first batch of lycosas they released had a lot of problems but they were supposed to have been fixed so I went and bought one and the touchpad doesn't even work, the problem is it's not worth the money sending it back just to get the touchpad fixed, luckily razers drivers are quite good so I bound all the media keys to the keypad.

When I reported the problems I got a response back the next day, Razers always been pretty fast to respond, still it's the last time I buy any thing from Razer, shame I liked their mice.

Definitely WOULDN'T recommend buying one

Theirs nothing special about the keyboard to make it worth the price it's nothing more than a cheap keyboard with a backlight and a media touchpad nothing that makes it worth the price it doesn't even have anti ghosting for all the keys, I'm not even sure how you clean the keyboard I don't think you can even remove the keys. :no:

hmm Vice, after you said about them trying to max out the power specifications for USB, i unplugged my 360 controller and webcam at boot.

it still didnt turn on, but it came on quicker than it usually does.

i had to hit the back of it, the past week or so its taken a good 5 minutes of me booting and hitting the back of it before it actually comes on.

it worked first hit this time though ;)

it just annoys me how it was perfectly fine for the 30 days i had to send it back, and then straight after starting going haywire.

i might take it apart and just unplug the touch screen, i never use it and it seems to be the source of most of the problems i think.

so jealous of my friend right now who came to my house on friday and spent a grand and a half on a pretty nice computer.

he got a G19 :(

Well, i bought one (Lycosa Mirror) a week ago or so, but had to return it because it was defect.

It had all the problems the early batch had (led flashing, random keys stop working, touch pad don't work).

My keyboard was a 'new batch' KB (serial started with MT09), and it's a shame that Razer still have some bad Lycosa keyboards in production.

I've send it back now, and will hopefully get a refund.

After a detailed explanation to the online-shop i bought it from, they refunded the money 2 days later.

I like Razer's mice, but i will never touch their keyboards again.

Now i have an apple wired instead (i wanted a keyboard without all the extra mediakeys and all that bs)

The G19 is crazy, a keyboard that uses a power adapter is going too far.

holy ****, i didnt know it needed it's own plug :| lmao

i thought itd just be normal USB.

come to think of it, it has a screen.

i feel quite silly now for not realising USB cant power a screen.

After a detailed explanation to the online-shop i bought it from, they refunded the money 2 days later.

I like Razer's mice, but i will never touch their keyboards again.

Now i have an apple wired instead (i wanted a keyboard without all the extra mediakeys and all that bs)

same, i do quite like their mice, but i also will never be going near a razer keyboard again.

and ill try to make sure my friends dont ethier.

saitek's keyboards are pretty reliable though.

i had one for YEARS, and gave it away when i got this razer and its still going on my friend's computer.

another freind bouht a saitek one aswell and it seems alot tougher and more sturdy.

my I and G keys just died, had to unplug it and plug it back in and beat it before theyd work again :crazy:

I have the same keyboard they've had problems from the start, the first batch of lycosas they released had a lot of problems but they were supposed to have been fixed so I went and bought one and the touchpad doesn't even work, the problem is it's not worth the money sending it back just to get the touchpad fixed, luckily razers drivers are quite good so I bound all the media keys to the keypad.

When I reported the problems I got a response back the next day, Razers always been pretty fast to respond, still it's the last time I buy any thing from Razer, shame I liked their mice.

Definitely WOULDN'T recommend buying one

Hmm....I bought my Mirror Edition when it first came out and I've never had any problems with it. Typing on it right now...

  • 4 months later...

While it's a somewhat old thread, I feel people should know that the problems STILL persist. A few days ago I bought the MT09 series of the non-mirror and within 12 hours had issues of keys not responding and requiring a reboot or replug to work. I've already contacted Razer about the issue and after pointing out how their canned responses are of no help, they finally agreed that RMA is the best option.

  • 1 year later...

While it's a somewhat old thread, I feel people should know that the problems STILL persist. A few days ago I bought the MT09 series of the non-mirror and within 12 hours had issues of keys not responding and requiring a reboot or replug to work. I've already contacted Razer about the issue and after pointing out how their canned responses are of no help, they finally agreed that RMA is the best option.

I had the same issues. However I made sure all new drivers were installed (v3 I think it is now). Just make sure you leave the task bar icon running (don't disable it), also there's an option that disables hotswitching.

No problems for 3 weeks now.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!