Support

Get Lurionyx SysDiag running and know what to check first.

This page is the support home for installation help, safe diagnostic use, security reports, feedback, privacy questions, and download verification.

01

Install and launch

Download the Version 2.0.1 Public Beta RAR, extract the whole Lurionyx SysDiag V2 folder, and start the app with the included shortcut. Keep the files together so images, diagnostic components, bundled runtime files, and legal notices stay beside the app.

Open downloads and verification

02

Run as administrator when needed

Basic diagnostic pages can run normally. Service actions, security actions, update repairs, device changes, and some hardware readings may need administrator permission.

03

Support response time

Lurionyx SysDiag is currently a one-person project. Support is handled by Rayen Leys, so replies may take time, especially if the app gets a lot of users.

04

Security reports

If you believe you found a security issue, report it privately instead of posting exploit details publicly. Include the affected page or app feature and the steps needed to reproduce the issue.

Read the security policy

05

Privacy and legal questions

For privacy, legal, licensing, or personal-data questions, use the official contact email and avoid including sensitive diagnostics unless they are needed for the request.

Read the privacy policy

06

Version 2 public beta

Version 2.0.1 is free forever and ready for public feedback. It includes the portable Version 2 app, bundled runtime files, first-run page tours, and local crash dump analysis.

If a sensor value is missing, include the page name, hardware model, Windows version, and whether the app was run as administrator when you report it.

See roadmap and known issues

Before repair actions

Repairs should match the symptom.

Lurionyx SysDiag is designed to explain what an action does before running it. If a repair does not match the symptom, do not run it just because it is available.

  • Create a restore point before moderate or high-risk repairs.
  • Read the action explanation and expected reboot behavior.
  • Refresh the affected diagnostics page after the repair completes.