Help wanted: OpenMPT testing on Windows Server

[Amaroq Starwind]

While I am not an official contributor for OpenMPT, I do read the issue tracker from time to time, and I noticed an unusual bug report—what made this bug report so unusual was the fact that OpenMPT was being run on a system running Windows Server.

If you're not familiar with the nitty-gritty of operating systems, then you would think that Windows Server is just a rebranded version of regular Windows, more expensive, more complicated to configure out of the box, and with some components added or removed to make it more suitable for its intended userbase... but in reality there are a lot of smaller differences deeper in its codebase which can wreak havoc with different pieces of software. Web browsers, antimalware programs, process managers, even media players have all been known to behave differently or even stop working entirely on Windows Server's "default" configurations (or as close to "default" as you can get, see my earlier comment about a more complicated OoBE setup).

For anybody on this forum who happens to have access to a Windows Server system, and who is in a position to install programs without getting in trouble... would you be willing to test OpenMPT on those systems and report any abnormal behavior which appears specific to Windows Server on the issue tracker? Further discussion can take place here as well.

I understand that security can also be a stronger concern in environments which happen to use Windows Server, but any details you can share about the way you have your system configured could also be relevant to the bug reports and/or discussion.

Reminder: I am not affiliated with the OpenMPT developers, I'm just trying to help with what appears to be an overlooked issue.