FIPS Compliance Issue

The following troubleshooting steps address an issue where a System.TypeInitializationException occurs because Windows is enforcing FIPS-compliant cryptographic algorithms. This typically happens when the system or domain has FIPS mode enabled, which blocks applications that use non-FIPS cryptographic providers (such as certain hashing or encryption implementations in .NET), causing the initialization failure.

TYPE: System.TypeInitializationException.

MESSAGE: The type initializer for ‘XXX’ threw an exception. -> The type initializer for ‘XXX.XXX’ threw an exception. -> This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Important Notice: Before applying any of the following solutions, make sure to create a backup copy of all files that will be modified. Incorrect changes to configuration files may cause the application to malfunction or fail to start. For this reason, it is strongly recommended that these modifications be performed by a system administrator or by personnel with sufficient technical expertise.

Solution 1: Disable FIPS mode in Windows

This can result if your System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting is enabled. Use the following steps to disable this setting:

1. Launch your Windows Control Panel, double-click Administrative Tools, and then double-click Local Security Policy. The Local Security Settings panel launches.
2. Click Security Settings in the left pane to expand, click Local Policies to expand, and then click Security Options.
3. Locate and right-click the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing entry in the right pane, and then click Properties from the shortcut menu.
4. The System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Properties dialog box appears.
5. Enable the Disable option, click Apply, and then OK.
6. Close the Local Security Settings panel, restart the computer and check

Solution 2: Disable FIPS mode via Windows Registry

It can also be done editing the Windows registry, contact your IT administrator to do these steps:

1. Press the key combination WINDOWS_KEY+R to launch the Run dialog.
2. Type “regedit” into the Run dialog box (without the quotes) and press Enter.
3. Navigate to “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy”.
4. Look at the “Enabled” value in the right pane. If it’s set to “0”, FIPS mode is disabled.
5. If it is enabled, double click on the file and select 0.
6. Restart the computer and check.

Solution 3: Disable FIPS Enforcement at the Application Level (via .NET Configuration)

In environments where Windows enforces FIPS-compliant cryptographic algorithms, applications built on .NET Framework may fail during initialization if they rely on non-FIPS cryptographic providers. When modifying system-wide security policies is not possible, the application can be configured to bypass the FIPS check at runtime.

This option applies only to applications built on .NET Framework (version 2.0–4.8). It does not apply to .NET Core or .NET 5+. The modification must be done carefully to avoid XML formatting issues or invalid configuration structure.

It is only valid for AutoCAD versions previous to 2025.

To do this, edit the application’s configuration file (acad.exe.config) in the AutoCAD installation directory and add the following entry under the section:

<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>

Learn more about in the next official Microsoft resources:

• System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
• Windows FIPS 140 validation
• Security options