XTop

English

العربية

English

العربية

Appearance

Troubleshooting ​

Nothing happens when I launch it ​

Check Task Manager for an existing XTop.exe. A single-instance lock means a second launch hands off to the running copy and exits — which looks exactly like nothing happening. The running copy will have focused its panel.

If the app cannot start at all, it shows an error box rather than failing silently: a window that will not load or a data file that will not read produces a dialog with the stack and the path to the data folder.

The tray icon is missing ​

Windows decides whether a tray icon sits on the taskbar or in the hidden-icons overflow. Drag it out of the ^ area, or set it under Settings → Personalization → Taskbar → Other system tray icons.

The orb disappeared ​

If you unplugged the monitor it was on, it is clamped back onto a visible display automatically. If you turned it off, re-enable Show floating button in Settings — or just use the tray icon and Ctrl+Shift+Space.

The terminal takes no keyboard input ​

The interactive terminal backend could not load, so sessions run in output-only fallback mode. The terminal window says so in a banner. Commands still run and their output still streams — you just cannot type into them.

WSL options are greyed out ​

The app probes WSL and reports what it found: not installed, the Microsoft Store stub rather than the real thing, or installed with no distro registered. The disabled entries carry the reason, and offer Microsoft's install page.

If the probe could not answer confidently, nothing is disabled — the app would rather let you try than block you on a guess.

If a specific distro is missing, check the name in Settings → WSL distro against wsl -l -v.

Prayer times are wrong or missing ​

  • Times are fetched once a day and cached. Refresh times in the Islamic dialog forces a re-fetch — do that after travelling.
  • Check the calculation method; it changes Fajr and Isha by a lot.
  • No connection on the first run of the day means no times for that day. Once cached, a dropped connection does not stop the alerts.

No sound ​

Settings tells you when it played something and nothing came out. Check the Windows volume mixer — XTop can be muted there independently of the system volume. Also check that the sound for that alert kind is not set to Silent.

Meetings ​

Covered in detail at the end of the Meetings page. The short version:

  • "Choose or download a local Whisper model first" — open Manage model… and download one.
  • "The Whisper server stopped unexpectedly" — recording keeps going; press record again to restart transcription.
  • A non-ASCII model path — Whisper cannot open it. Keep models in C:\ProgramData\DevNexus\models.

"Start with Windows" is disabled ​

The toggle only works for an installed build. If you are running the portable exe, install the setup version instead and turn it on there.

I restored the wrong backup ​

Your previous data was archived before the restore, into a before-restore folder inside %APPDATA%\XTop\. Restore from there.

The data file is corrupt ​

XTop moves it aside as xtop-db.json.corrupt-<timestamp> and starts clean rather than discarding it. If you have a backup, restore it; if not, the corrupt file is still there to salvage by hand.