Solution
This error occurs because DIAdem does not recognise that a compatible version of .NET Framework is installed.
Check if (and which version of) .NET Framework is installed, refer to the
Use Registry Editor section in
[External] How to: Determine which .NET Framework versions are installed.
Refer to the troubleshooting steps in the relevant sections below depending on which version of .NET Framework is installed.
.NET Framework is Not Installed
If .NET Framework is not already installed on the PC, download .NET Framework
Runtime version 4.6.2 (or whichever version is required by the installer) from
[External] Download .NET Framework 4.6.2.
.NET Framework 4.6.2 or Later is Already Installed
.NET Framework 4.5 and later is backwards-compatible with applications that were built with earlier versions, as explained in
[External] Version compatibility. Therefore, if this error occurs when .NET Framework 4.6.2 or later is installed, it is caused by underlying issues on the PC that prevent the DIAdem installer from recognising .NET Framework.
Follow the troubleshooting steps below to resolve this error:
- Verify that the Windows PC is has the latest updates. Instructions can be found in [External] Get the latest Windows update.
- Run the [External] .NET Framework Repair Tool in case there are any issues with the .NET installation.
- Install the [External] .NET Framework 4.6.2 Developer Pack (or whichever version is required by the installer).
- Verify that the Common Language Runtime (CLR) is compatible using the Step 2: Windows Powershell section in [External] How to determine the installed CLR version.
- The CLR version should be 4.0.30319.42000 or later.
- If using any 3rd party security or anti-virus software, temporarily uninstall it to check if the software is blocking the DIAdem installer.
- Configure Windows for a [External] Clean Boot. Upon restart, run the DIAdem installer again.
- It's possible that a 3rd party process is conflicting with NI's installer or .NET Framework. This test will boot Windows with minimal start-up processes to verify if this is the case.
- If the Windows PC came with .NET Framework pre-installed, the Windows image may be corrupt. Re-image the PC.