It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda RMM
formerly Managed Workplace

.NET Framework 4.6.0 Updates to be considered

  • Last updated on

As of MW 10SP2 MR1 we deploy the .NET Framework 4.6.0.

The .NET 4.6.0 Framework if un-patched could cause some unexpected behavior and/or crashing due to a couple known issues that have been identified and fixed in rollup updates.

One of the issues I found was described as an issue in the RyuJIT compiler which is shared by all .NET framework versions on the system when .NET 4.6 is installed, so not only will it affect .NET 4.6, but also 4.0, 4.5, etc which means it could affect any version of our software running on a machine with .NET 4.6.0. This issue caused the wrong parameters to be passed through code which could lead to unexpected behavior and/or crashing.

There’s a fairly detailed write-up http://www.theregister.co.uk/2015/07/27/critical_bug_in_net_46 that has a few additional references

The above seems to be addressed in the rollups linked below and the issue per Microsoft is described as the following.

Issue 6

After you install the .NET Framework 4.6, the .NET Framework 4.6 uses a new 64-bit compiler that's called RyuJIT. In some cases, the new compiler generates incorrect code that causes unpredictable behavior or crashes.

There is another set of .NET 4.6 rollups which address the following:

Issue 8

When you create native code for certain methods, the .NET Framework applications and NGEN processes may experience an unexpected crash.

You may also address these issues by simply upgrading the .NET framework to .NET 4.6.1 or 4.6.2 however if the system is an Exchange Server you may need to reference the Exchange Compatibility Matrix for .NET Framework 4.6 to ensure you can upgrade the .NET Framework version safely.