WPF front end for the Devuvo activation validator script
  • PowerShell 54.9%
  • C# 45.1%
Find a file
2026-09-15 07:55:50 +05:30
Assets sync bundled script 2026-09-12 03:04:10 +05:30
Localization validator source 2026-08-15 01:17:57 +05:30
.gitignore validator source 2026-08-15 01:17:57 +05:30
app.manifest validator source 2026-08-15 01:17:57 +05:30
App.xaml validator source 2026-08-15 01:17:57 +05:30
App.xaml.cs validator source 2026-08-15 01:17:57 +05:30
app_icon.ico validator source 2026-08-15 01:17:57 +05:30
LuaToolsValidator.csproj bump to 1.0.1 2026-09-11 23:16:44 +05:30
MainWindow.xaml remove disable updates checkbox 2026-09-11 23:13:59 +05:30
MainWindow.xaml.cs revert luavalidator uri scheme and auto-report submit 2026-09-15 07:55:50 +05:30
README.md bump to 1.0.1 2026-09-11 23:16:44 +05:30

LuaTools Validator

WPF front end for Devuvo.ps1, the script that checks and repairs a broken Denuvo activation on a Windows machine.

You give it a Steam AppID, it pulls the current script, runs it elevated, and streams the output into the window with a progress bar. At the end you get a D-Report code you can paste back into the bot.

Building

Needs the .NET 10 SDK and Windows.

dotnet build

For a single file to hand out:

dotnet publish -c Release -r win-x64

Layout

MainWindow.xaml.cs   all the logic, script download, process handling, log parsing
MainWindow.xaml      the UI
Localization/        string tables, multiple languages
Assets/Devuvo.ps1    bundled copy of the script, used if the mirrors are unreachable

The script is fetched at runtime from luatools.vercel.app first, falling back to the copy in lt_api_links, so the bundled one is only a last resort. That means fixes to the checks ship without rebuilding this.

Notes

Run it as admin. Most of the repair steps touch the Steam folder and the registry, and it will tell you it's in standard mode if you don't.

Reports get uploaded to paste.rtech.support so they can be linked in a ticket.