Need help with my Aula F75 Pro

General
1

My Aula F75 Pro suddenly started acting up after normal use, and now some keys are not responding the way they should. I’ve already tried basic troubleshooting, but the problem is still there, and I need help figuring out whether this is a common Aula F75 Pro issue or if there’s a fix I’m missing.

2

Start with the easy split. Figure out if it is hardware, firmware, or software.

  1. Test the board on another device.
    Use wired mode first. No hub. No extender. If the same keys fail on a second PC, the issue is inside the keyboard.

  2. Check switch behavior.
    If your F75 Pro is hot-swap, pull the bad switch and swap it with a key you know works, like from Pause or Scroll if you do not use those. If the problem follows the switch, the switch is bad. Replace it. If the same socket still fails with a known good switch, the socket or PCB is the problem.

  3. Clean the socket.
    Dust, bent pins, and half-seated switches cause missed input a lot. Pull the switch, inspect both pins, make sure they are straight, then reseat firmly. A tiny bit of debris in a hot-swap socket is enough to make keys act weird.

  4. Reset the keyboard.
    Try factory reset from the manual or Aula software. Some boards get stuck after macro or layer changes. If random keys output the wrong thing, this matters more than if they are dead.

  5. Reflash or update firmware.
    If Aula has a firmware tool for the F75 Pro, run it in wired mode. Close RGB and remap software first. Bad firmware shows up as wrong mappings, chatter, or dead zones.

  6. Rule out software conflict.
    Turn off AutoHotkey, SharpKeys, game overlays, and Aula software tempraorily. Test in a text editor and a keyboard tester site.

  7. Watch for pattern.
    One key dead, often switch.
    Whole column dead, often PCB trace or controller issue.
    Only wireless fails, battery or 2.4 GHz issue.
    Double typing, often switch wear or debounce issue.

If you list which keys fail, and whether they are dead, double press, or output the wrong key, people here can narrow it down fast. If it is a whole row or column, dont waste time on switch swaps first.

3

I’d add one thing @espritlibre didn’t really lean on enough: check for a stuck Fn/layer state before you assume the PCB is dying. On a lot of 75% boards, when a few keys start doing the “wrong” thing after normal use, it’s not always dead hardware. Sometimes the board thinks you’re on a secondary layer, or a macro profile got toggled by accident. That can look a lot like failure when it’s really just the keyboard being dumb.

A few extra checks:

  • Open an online key event tester and see the exact scancode being sent.
    • If pressing A sends nothing, that points one way.
    • If pressing A sends Left Arrow or some media key, that points another way.
  • Try BIOS or your login screen.
    • If the bad behavior happens there too, it’s probly not Windows doing something weird.
  • Check battery level if you mostly use it wireless.
    • Low battery can make some boards act wonky before they fully die. Not super common, but it happens.
  • Look for liquid or humidity damage.
    • Even one tiny spill from days ago can corrode a couple of keys first, then spread. People always say “normal use” and then remember the coffee incident later lol.
  • Press around the case gently while testing the dead keys.
    • If keys come back when the case flexes a little, that screams solder/socket issue, not software.

I’d actually disagree a bit with “just reflash firmware” early on. If the problem started suddenly and only affects a small cluster of keys, reflashing is lower on my list than checking for physical damage, layer weirdness, or partial PCB failure.

If you post the exact keys affected, like “entire left column” vs “just R and F” vs “wrong output,” people can narrow it down way faster. Whole pattern matters a ton here.

4

I mostly agree with @espritlibre, but before blaming firmware or the PCB, I’d test whether this is actually a switch or hotswap socket issue. On the Aula F75 Pro, a single bad switch can look like a dead key problem when the board itself is fine.

What I’d do:

  1. Pull the problem keycaps.
  2. Swap the affected switches with known-good ones from keys that work.
  3. Test again.

Results matter:

  • If the problem follows the switch, the switch is bad.
  • If the same key position still fails, it’s socket/PCB side.
  • If the key starts working after reseating, the switch may have had bent pins or poor contact.

Also inspect the switch pins closely. Bent pins are super common after even one swap and can cause partial input or total failure.

One thing I slightly disagree on: case flex testing can hint at a bad connection, sure, but I would not press on the case much unless you want to risk making it worse. Better to open it and visually inspect the PCB, daughterboard cable, and plate alignment directly.

For the Aula F75 Pro specifically, also try wired mode with the board fully powered off first, then reconnect. Some tri-mode boards get weird when switching between 2.4G, Bluetooth, and USB states.

Pros of the Aula F75 Pro:

  • Hotswap makes switch diagnosis easy
  • Tri-mode is convenient
  • Nice layout for daily use

Cons:

  • More points of failure because of wireless plus hotswap
  • Socket issues can happen after switch changes
  • Harder to diagnose than a plain wired board

If you list the exact dead keys, people can tell pretty fast whether it’s row, column, or just a couple sockets.