When I have the time I will try to install a VM with a Windows Server build in it. I know that you are using Windows DataCenter. Probably the problem would be the same on Windows Server.1.4.7 still crashes on my server. One thing I noticed in the even log as soon as it crashed was this SQL error.
Log Name: Application
Source: Microsoft-Windows-Perflib
Date: 1/7/2021 6:15:49 PM
Event ID: 2003
Task Category: None
Level: Warning
Keywords:
User: DOMAIN\Administrator
Computer: neptune
Description:
The configuration information of the performance library "sqlctr90.dll" for the "MSSQL$MICROSOFT##SSEE" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
I somewhat suspect that part of the problem is probably related to the fact that the application is not "signed" with a developer certificate. That's not an option since the project is open source and I don't want to spend the $300 to get a signing certificate anyway.
I think that the information about "not trusted" is the giveaway that there is some security setting that needs to be adjusted either with the application or with your setup. I am not a Windows Server expert so I'm not sure where to look without actually trying it. It does look like the location of the problem in the code has changed somewhat.
I don't know when I can get the VM installed. My WAG is that this would take a few hours once started, and possibly more disk space than I have available. I'll work on it when I have a chance, but even if I can get the VM installed I'm not 100% certain that it would help since my security settings would not necessarily be identical you yours. It is also possible that the problem may be related to a SQL installation somewhere on your machine that is interfering with the very restricted version of SQL (LocalDB) I'm using. So, even if the Windows Server install identical to yours I'm not sure whether I could get the SQL environment reasonably identical.
The other thing that could be going on related to Perflib (above is the Windows Performance Counter library) is interesting. The only way I'm using anything related to that is the CPU "busy" counter control on the main screen. It is possible that there is some security restriction around that too. It is also possible that Perflib is called indirectly by SQL stuff.
In essence what I'm saying is that it will take a lot of time and effort to track this down. Fixing a problem like this is not necessarily about just fixing my part of the equation. I will get to this, I'm not sure exactly when I can get back to you on it. It is probably that once I get a Server version installed the problem and solution will be pretty obvious.