Download correctly, verify first, act safely
You do not need PowerShell expertise to use VietLicenSure. Stop if the checksum, signature, or download source does not match.
1. Download from the official source
Use only the official GitHub Release. Do not run an EXE redistributed through forums, unknown archives, or repackaged downloads.
2. Verify before launch
In the full package, run VERIFY-RELEASE.cmd and require 0 errors. Current EXE SHA-256:
D4FEC3E7806BA18B263BC3AB00394BBB21C75ED82379A61FD4FFD9A57A6B88E7
When you only have the EXE, use PowerShell:
Get-FileHash .\VietLicenSure-v5.0.exe -Algorithm SHA256 Get-AuthenticodeSignature .\VietLicenSure-v5.0.exe
3. Run as a standard user
You do not need to launch the entire application with “Run as administrator.” Accept UAC only after selecting a task that genuinely requires elevation.
Stay Offline for local assessment. The general Online switch refreshes the signed catalog first and then checks application-version availability without automatically downloading/installing it. When Online is enabled from a pending remediation task, VietLicenSure returns to that scope, rescans, and shows a preview; a separate confirmation is required before any system change, and no report starts automatically. LAN uses a separate switch.
4. Interpret results correctly
| Status | Meaning |
|---|---|
| Activated / Licensed | Technical status within the observed scope; it does not prove legal entitlement. |
| Needs verification | Evidence is incomplete or requires an invoice, agreement, account, or portal check. |
| Repair needed | An edition, service, or system file needs attention; prefer official repair tools. |
| IntegrityCompromised | A file/signature mismatch was found; stop changes and obtain a clean official copy. |
5. Use backup and post-action verification
- Confirm the product and target.
- Use Preview/Dry Run first.
- Review planned changes and backup location.
- Approve each scoped item; accept UAC only when expected.
- Wait for the rescan; completion requires a passing post-check.
6. Open the Central Dashboard
- Enable the authorized internal LAN and start the enterprise server.
- From the server tab, choose to open the Central Dashboard.
- Use the short-lived URL/session generated by the application; do not share its token outside the LAN.
- The dashboard is read-only: Online/Stale/Offline, last seen, technical status, License Compliance, and alerts; it does not control endpoints.
Getting support
Include the version, reproduction steps, screenshots, and a redacted support bundle. Never publish a full product key, secrets, or exploit code.