Scrooge wrote:Maybe we need to submit a new ticket, because ticket #89 in relation to this problem was closed as a duplicate of ticket #6.

This issue where Uthgard.exe isn't recognized as a valid Win32 application by WinXP needs to be specificed when creating the ticket, so as not to confuse it with any TLS compatibility issues - cause that's now what this is about.

Nelg wrote:I don’t know anything about .NET development, but after reading some Stack Overflow posts, I guess the issue we have is still related to .NET 4.6: many people have the mentioned "is not a valid Win32 application" problem when developing with Visual Studio unless they target a WinXP-compatible framework or compile it with some WinXP-compatible setting.

· xxxxxx.exe is not a valid Win32 application (this answer describes a solution for Visual Studio 2015)

· .exe is not a valid Win32 application on Windows XP (this answer explains what might be going on)

· winform, c# application, Visual Studio 2015: *.exe is not a valid Win32 application

Yeah, will do this maybe later today (unless a staff member answers here in this thread or reopens issue #89). EDIT: nvm → https://uthgard.org/tracker/issue/598/