xDecoder 14.0 — Activation, Support and ECU Coverage 14.0

TNLB7 said:

ENISCO Try this. I've made this xDecoder-Launcher (with help from AI) that fixes the problem for me...

Click to expand...

Nice work putting this together and sharing the source — that kind of transparency makes it much easier to evaluate.

From what the source shows, the approach is sound for the problem it's solving. The launcher sets a Debugger value under SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\shutdown.exe pointing at cmd.exe /c exit, which redirects the 32-bit shutdown.exe launch path to a no-op. It cleans up that value once xDecoder.exe processes from its directory have exited, and the --restore flag as a recovery option if something goes wrong mid-session is a sensible addition.

A few things worth noting for anyone considering using it:

• System-wide scope while active — the README already flags this clearly, but it's worth repeating: the IFEO key covers the 32-bit shutdown.exe path system-wide for the duration xDecoder is open. Any other 32-bit process that tries to invoke that executable during that window would also be blocked. In practice that's unlikely to matter on a dedicated tuning machine, but it's not something to overlook on a general-use PC.
• Admin requirement — writing to HKLM IFEO keys requires elevation, so users will see a UAC prompt every launch. That's unavoidable given what it needs to do, but worth setting expectations.
• No code signing — SmartScreen and most AV products will flag an unsigned executable from an unknown publisher. Having the Go source available helps people who want to verify and build it themselves, but the pre-built binary will get warnings for most users until it builds a reputation hash.

The code itself looks clean — mutex for single-instance enforcement, proper cleanup flow, no logging artifacts left on disk. Nothing in the source raises a red flag beyond the caveats above.

As for including it in the official xDecoder download, that's a call for Bin rather than me — worth posting in the resource thread or dropping Bin a message directly so it gets proper consideration. The transparency of including the source folder definitely works in its favour.