Troubleshooting AlomWare Lights: Common Issues and Fixes
AlomWare Lights (part of AlomWare Toolbox) is lightweight automation and window-management software for Windows. Below are the most common issues users encounter with AlomWare Lights and concise, actionable fixes.
1. App won’t start or crashes on launch
- Cause: Outdated version, corrupted install, or conflicting third‑party tweaks.
- Fix:
- Download and install the latest AlomWare Toolbox from the official site.
- Restart Windows, then run the installer as Administrator (right‑click → Run as administrator).
- If problem persists, uninstall, reboot, then reinstall.
- Temporarily disable or remove other tweak/automation utilities to rule out conflicts.
2. Features don’t work on certain windows or apps
- Cause: Lack of admin rights or target app running with higher privileges.
- Fix:
- Run AlomWare Toolbox with admin rights: right‑click → Run as administrator. For automatic admin on login: Settings → Run at startup/login → With Admin rights.
- If the target app runs as admin, ensure Toolbox is also elevated; otherwise it cannot interact with that app’s windows.
3. Auto‑typing or keyboard automation fails
- Cause: UAC, elevated target apps, or non‑English keyboard mappings.
- Fix:
- Run Toolbox as admin (see above).
- For non‑English keyboards, adjust the typing profile or use clipboard‑paste actions instead of simulated keystrokes.
- If UAC prompt blocks automation, consider using scripts that include simulated Enter after UAC is triggered or avoid automating UAC prompts (they require secure attention).
4. Saved window positions or states not applying
- Cause: Windows layout changes or app creates different window class/title on launch.
- Fix:
- Re-save the window profile while the app is in the exact state (restore/maximize/size) you want.
- Use more general window matching (class or partial title) if the app changes title between runs.
- Ensure no other utility (e.g., virtual desktop manager) is overriding positions.
5. Startup / Run‑at‑login not working
- Cause: Permission issue or Windows blocking startup entries.
- Fix:
- Enable “Run