To fix a locked Windows key on your AULA F99, press Fn + Win once and release both keys. Test Win alone, then press Fn + W if you need to restore Windows mode on the original F99 or F99Pro. Do not use that second shortcut on the F99 Max, where it selects a Bluetooth slot.
Start with those keyboard controls before changing Windows settings or drivers. The steps below use Windows 11 menus, and connection fixes apply mainly when several keys or the whole keyboard are unreliable.
The short version
- Check the lock: Press Fn + Win once, then test Win by itself.
- Restore Windows mode: Use Fn + W on the original F99 or F99Pro.
- Reset customizations: Hold Fn + Esc for five seconds on the F99 or F99Pro, or three seconds on the EPOMAKER x AULA F99 Max.
- Follow the symptoms: Check connections when several keys fail, and inspect the switch when one key stays faulty across computers.
| Fix or workaround | When to use it |
|---|---|
| Toggle the Windows key lock | Start here on F99, F99Pro and EPOMAKER x AULA F99 Max |
| Restore Windows mode | Original F99 or F99Pro has swapped modifier functions |
| Reset F99 or F99Pro | Lock and mode checks fail |
| Reset EPOMAKER x AULA F99 Max | Lock check fails on this model |
| Open Start with Ctrl + Esc | You need access while troubleshooting |
| Test another computer | You need to separate keyboard and PC problems |
| Reconnect USB and bypass hubs | Wired or receiver input is unreliable |
| Use a wired connection | Original F99 has wireless problems |
| Charge and reduce backlighting | Original F99 has a low battery |
| Power cycle F99Pro | Several keys or its connection stop responding |
| Reduce receiver interference | Original F99 has unreliable 2.4GHz input |
| Re-pair the original F99 receiver | Receiver connection remains faulty |
| Select or re-pair a Bluetooth slot | F99 or F99Pro connects to the wrong device or fails to connect |
| Select or re-pair Max wireless connections | EPOMAKER x AULA F99 Max needs its own shortcuts |
| Restart Windows Bluetooth | The Bluetooth connection fails |
| Remove and re-add the Bluetooth keyboard | Bluetooth still will not reconnect |
| Run Bluetooth diagnostics | A Bluetooth connection problem continues |
| Disable PowerToys remappings | Keyboard Manager redirects the key |
| Exit an AutoHotkey script | A script intercepts the key |
| Remove a SharpKeys mapping | A persistent mapping disables or redirects the key |
| Turn off Filter keys | Windows ignores brief presses |
| Turn off unintended Sticky keys | Modifier shortcuts behave unexpectedly |
| Use the On-screen keyboard | You need a temporary substitute |
| Install Windows and driver updates | The problem occurs only on one PC |
| Reinstall the keyboard device | A PC-specific driver problem remains |
| Clean around the key | An original F99 key is obstructed or intermittent |
| Reseat or replace the switch | One key fails on a hot-swappable mechanical model |
| Request AULA repair or recovery | Keyboard-side checks do not resolve the failure |
Turn off the Windows key lock
Hold Fn, press Win once, then release both keys. Press Win alone to test it. This combination toggles the Windows key lock on the F99 and F99Pro, and the EPOMAKER x AULA F99 Max uses the same shortcut.
Test after each toggle, since pressing the combination again can turn the lock back on. To open Start while troubleshooting, press Ctrl + Esc. That opens the menu but does not replace Win in other shortcuts.
Restore Windows mode on the F99 or F99Pro
On the original F99 or F99Pro connected to Windows, press Fn + W, then test Win again. This is especially useful when the left Alt and Win keys have exchanged functions.
On the EPOMAKER x AULA F99 Max, Fn + W selects Bluetooth device slot 2. Check your exact model before using operating-system or pairing shortcuts, since the Max has different controls.
Reset stored keyboard customizations
If unlocking and restoring Windows mode do not help, hold Fn + Esc for five seconds on the F99 or F99Pro, then release. AULA’s current F99 and F99/F99Pro FAQs specify five seconds, although the original F99 manual lists three seconds. Expect customized keyboard settings to reset.
Afterward, restore Windows mode with Fn + W on the original F99 or F99Pro and test Win. If necessary, toggle the lock once with Fn + Win and test again. On the EPOMAKER x AULA F99 Max, hold Fn + Esc for three seconds instead, release both keys and test Win.
AULA identifies stored key customizations as a possible cause of Windows key failure. Use the keyboard reset to restore those defaults rather than relying on removal of the companion application. If the reset changes nothing, check whether the failure follows the keyboard to another computer.
Compare computers and check power or connections
Connect the keyboard to another PC and test Win after checking its lock and, on the original F99 or F99Pro, Windows mode. A failure that follows the keyboard suggests a keyboard-side problem. If it works elsewhere, focus on the original PC’s software and drivers.
If several keys or the connection are unreliable, unplug the USB cable or receiver, wait briefly and reconnect it directly to another PC USB port. Bypass any USB hub and inspect the cable for damage. Microsoft specifies waiting about ten seconds before reinserting a wireless receiver.
On the original F99, move the connection switch to its middle wired position and connect the keyboard’s USB-C port directly to the computer with its USB cable. Test Win over that connection to bypass wireless problems. If the battery is low, charge the F99 from the computer with the original cable; AULA instructs you to avoid fast-charging devices.
Lower or disable the backlight while checking low-battery behavior. You can follow the steps to turn off your keyboard backlight while troubleshooting wireless reliability.
For an unresponsive F99Pro, disconnect USB power and move the connection switch to the wired position to stop battery power. Reconnect the cable for wired operation, or return the switch to the required wireless mode, then test again.
For an original F99 with unreliable 2.4GHz input, put its receiver in a USB 2.0 port away from other receivers and metal hubs, keeping the keyboard nearby. To re-pair it, select 2.4G, hold Fn + ~ for about three seconds until the cyan indicator flashes rapidly, then insert the receiver into the computer. Do not transfer that pairing shortcut to the Max.
Reconnect Bluetooth when the connection fails
For an original F99 or F99Pro connected to the wrong Bluetooth device, set the switch to BT. Press Fn + 1, Fn + 2 or Fn + 3 to select the computer’s existing slot. To pair that slot again, hold its combination for about three seconds until the blue indicator flashes rapidly.
The EPOMAKER x AULA F99 Max uses Fn + Q, Fn + W and Fn + E for Bluetooth slots 1, 2 and 3. Hold the corresponding combination to initiate pairing. For receiver pairing on this Max model, hold Fn + R.
On Windows 11, open Start > Settings > Bluetooth & devices. Turn Bluetooth off, wait a few seconds, then turn it on and test the connection again.
If reconnecting fails, on Windows 11 open Start > Settings > Bluetooth & devices > Devices. Find the keyboard and select More options > Remove device, then select Yes. Put the keyboard into pairing mode using its model-specific shortcut. Then select the Network, Sound or Battery icon on the taskbar, select the Manage Bluetooth devices chevron on the Bluetooth quick setting and select the keyboard under New devices.
For a continuing Bluetooth problem, on Windows 11 open Start > Settings > System > Troubleshoot > Other troubleshooters. Beside Bluetooth, select Run and follow the Get Help diagnostics. This checks Bluetooth connectivity; it does not turn off the keyboard’s Windows key lock.
Check remapping software and input settings
If a PowerToys remap affects the key, open PowerToys Settings > Keyboard Manager and disable Keyboard Manager, or exit PowerToys completely. Test Win again, since mappings stop when Keyboard Manager is disabled or PowerToys is no longer running.
For an AutoHotkey v2 script that intercepts the key, right-click its notification-area icon and select Exit. Test Win again. If that fixes the problem, edit or remove the responsible script before running it again.
For a persistent SharpKeys mapping, open SharpKeys and select the mapping that disables or redirects Win. Select Delete, then select Write to Registry. Sign out and back in or restart; uninstalling SharpKeys alone does not reverse its registry mapping.
When brief presses are ignored, on Windows 11 open Start > Settings > Accessibility > Keyboard and turn off Filter keys, then test a normal short press of Win. If modifier shortcuts behave unexpectedly and Sticky keys was enabled unintentionally, turn it off there and retest the affected shortcut. These settings address input timing and modifier behavior.
For temporary access, on Windows 11 open Start > Settings > Accessibility > Keyboard and turn on On-screen keyboard. Click its Win key to access Start; you can also learn how to use the on screen keyboard for other input. This provides a substitute without repairing the physical key.
Update or reinstall drivers for a PC specific failure
If the keyboard works on another computer, on Windows 11 open Start > Settings > Windows Update and select Check for updates. For optional drivers, on Windows 11 open Settings > Windows Update > Advanced options > Optional updates. Select relevant keyboard, USB or Bluetooth driver updates, choose Download and install, then restart and retest.
If the PC-specific failure remains, save your work, right-click Start and select Device Manager. Expand Keyboards and identify the affected keyboard entry before removing anything, particularly if several keyboards are listed. Right-click that entry and select Uninstall device, then select Uninstall.
Right-click Start, select Shut down or sign out > Restart, then retest after Windows restarts. Windows attempts to reinstall the device driver. Reinstalling this Windows device is separate from reinstalling AULA’s configuration application, and the steps to update or reinstall keyboard drivers provide more detail.
Inspect the key and arrange repair
If only Win remains intermittent or unresponsive on your original F99, disconnect power and inspect around the key for debris or obstruction. Clean the affected area, reconnect the keyboard and retest. AULA recommends cleaning when individual F99 keys fail.
On a hot-swappable F99-family mechanical model, you can reseat or replace a faulty switch. Disconnect power, remove the Win keycap with a keycap puller, then grip the switch’s retaining tabs with a switch puller and lift gently. Inspect the pins of the switch you will install, align them with the actual socket and seat it without forcing it.
Replace the keycap, reconnect the keyboard and test again. If a known-good switch does not fix the key, the socket or circuit board may need service. Contact AULA at [email protected] with the exact model, connection mode, failed key and results of the lock, reset and cross-computer checks, and request repair or recovery instructions.
Frequently Asked Questions
Should you use Fn plus U to unlock the Windows key?
Use Fn + Win instead. AULA assigns Fn + U to Print Screen on the original F99.
Does changing the F99Pro knob mode unlock the Windows key?
The F99Pro knob’s game and office modes change lighting and multimedia controls. AULA does not document changing that mode as a way to unlock Win.
Can another key temporarily replace the Windows key?
If you have PowerToys installed, open PowerToys Settings > Keyboard Manager and select Remap a key > Add key remapping. Under Select, choose an unused working key; under To send, choose Win, then select OK. Keep PowerToys running, since the replacement depends on it. This workaround does not work at password screens and may conflict with games.
Which AULA configuration software should you download?
Match your complete model and physical layout before downloading. Original F99 ANSI and ISO-ES editions have separate packages, while F99Pro, F99 Max and EPOMAKER collaboration editions have model-specific downloads. A firmware listing alone is not a reason to flash the keyboard to fix this symptom.