< class="prominent-subhead ">

K2 Server service failing to start up after recent Windows 2012 R2 Updates

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


After some recent Windows Updates, the K2 Server service is not starting up successfully and the following error appears:

"The process was terminated due to an internal error in the .NET Runtime at IP 00007FFC75C7AC4B (00007FFC75C70000) with exit code 80131506."


Existence of .NET Framework 4.7.1 was confirmed via registry key as per:


K2 blackpearl version 4.6.11 is not compatible/supported with .NET Framework 4.7/4.7.1 as per:


The following Windows KBs were recently installed on this Windows 2012 R2 server:





As K2 Blackpearl version 4.6.11 is only compatible/supported with .NET Framework 4.6 and earlier, the recent Windows updates were uninstalled and the server restarted to resolve the issue.

K2 Blackpearl version 4.7 and K2 Five is compatible with .NET Framework 4.7; however if on .NET Framework 4.7.1, then the applicable Fix Packs or later Fix Packs can be applied to resolve the issue:

K2 Blackpearl 4.7 - https://help.k2.com/kb002132

K2 Five - http://help.k2.com/kb002137