Skip to content
DarkBeaconHelp
← All guides

DARKBEACON GUIDE

Fix a device that the App cannot find

Check selection, power, cable, connection, and Windows access permissions before trying recovery or reset.

On this page

Applies to: Blade keyboards (61, 68, 84, 87, and 100), Flux keyboards (61, 68, 84, 87, and 100), Flux 68, Flux 84, and Flux 87 regional models, Devil Breaker and related keyboards, Steampunk, Other supported wireless keyboards shown in the App

Symptoms

The App shows no device, the wrong device, an unsupported state, repeated disconnect and reconnect messages, or a keyboard whose settings cannot be opened.

Applies to

Use this guide before reset, update, or recovery when a supported keyboard is missing or unstable in the App, or its settings cannot be accessed. The administrator comparison below applies only to Windows.

Low-risk checks

  1. Confirm that this device model is supported. If the App shows a PS5 mode card, follow Use PS5 keyboard mode to return to PC mode without clearing settings; configuration and firmware updates are unavailable in PS5 mode.
  2. Quit the App completely and reopen it. Check for a clear OS permission or application-update prompt; do not start a firmware update while the connection is unstable.
  3. Connect the keyboard directly to a PC port with the original or another known-good data cable, avoiding docks and hubs. Allow one full detection cycle.
  4. For wireless use, switch back to USB first. Once the USB connection is stable, switch to the matching Bluetooth or 2.4G connection.
  5. If disconnects repeat, leave the cable and device still for a while and note whether movement, sleep, mode switching, or a specific page triggers them.
  6. Once the keyboard is reliably identified in PC mode over USB, check the App for an applicable software or firmware update. Follow Update device firmware before starting; updating is not a prerequisite for these detection checks.

Recovery steps

Restart the App once; if the operating system itself also fails to see the device, restart the computer once. The App is working again when its home page shows the card for the correct device model and clicking that card opens the device's settings page.

Windows: try running as administrator

DarkBeacon App normally does not need administrator permissions to connect to a keyboard or change its settings. Ordinary typing or a device listed in Windows without warnings does not guarantee that the App can access its settings.

If the checks above do not help and the App cannot connect, open keyboard settings, or reports Access denied, compare ordinary startup with administrator startup:

  1. Confirm that no firmware update or recovery is in progress. If you are unsure, leave the App and keyboard connected and contact support before restarting anything.
  2. Save any accessible unfinished settings, then quit the App completely, including its icon in the Windows system tray. Check Task Manager to confirm that DarkBeacon App is no longer running.
  3. Right-click the installed DarkBeacon App shortcut or application and select Run as administrator. Approve the Windows permission prompt for DarkBeacon App; enter administrator credentials if Windows requests them.
  4. Keep the same keyboard, cable, and USB port. Wait for detection and open the correct device card. If Retry appears, click it once, then check whether its settings open.
  5. If settings open and the App prompts for calibration, follow Calibrate key travel and confirm that calibration is saved.

If this works while ordinary startup fails, administrator mode is a temporary workaround. You can continue using it while support investigates; it is not a normal requirement for the App. The difference points to a Windows device-access restriction, but does not establish whether the cause is device permissions, a driver, security software, or another system policy. It does not prove that another application exclusively holds the keyboard connection.

A repair tool that passes its checks while running as administrator confirms access at that permission level only; it does not establish that ordinary App startup can access the device. If firmware is already updated and settings now work, no further flashing or factory reset is needed for this access symptom.

If administrator startup also fails, export fresh App logs after the attempt and send them through Submit feedback and diagnostics. If support already asked you to run a repair tool, include the report it requested. If administrator access is unavailable, contact support with that result. See Recover from an interrupted or failed update for other application-access checks and possible driver interference; do not reset the keyboard or uninstall HID drivers blindly.

Stop conditions

Stop reconnecting if the device or cable becomes hot, smells unusual, has visible damage, disconnects during an update, or fails with more than one known-good data cable and port. Do not factory-reset a device that cannot maintain power.

Contact support

Provide the model, OS, App version, connection, visible message, last successful state, and shortest safe reproduction. On Windows, include whether ordinary startup and Run as administrator give different results, whether the same Windows account was used, and whether each can open keyboard settings. Follow Submit feedback and diagnostics and remove private identifiers.