Occurs on any .net framework 4.6.1 and higher. It is due to the CLR.DLL.
Upgrading the .Net framework will not fix it.
CLR.DLL version 4.7.2102.0 to 4.7.2558.0 is the issue
What will fix it is
March 2018 Quality Rollup
If you can’t wait then the 2018-02 Preview of Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4075212)
will also fix it.
Verified on Windows Server 2012 R2