Introduction

If your installer depends on .NET Framework 4.0, the safest place to check for it is before installation starts. In Inno Setup, that usually means reading the Windows registry inside InitializeSetup and aborting with a clear message if the framework is missing. The important detail is that .NET 4.0 used Client and Full profile keys, while newer 4.5-plus detection often relies on a different Release value.

The Registry Keys To Check

For .NET Framework 4.0, the usual registry locations are under:

• 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client'
• 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'

A DWORD value named Install equal to 1 indicates that the profile is installed.

For many applications, checking the Full profile is enough. If your application can run with the Client Profile, check either one.

Basic Inno Setup Check

Here is a practical Inno Setup script that accepts either the Client or Full profile.

1[Code]
2function IsDotNet4Installed: Boolean;
3var
4  installValue: Cardinal;
5begin
6  Result := False;
7
8  if RegQueryDWordValue(HKLM,
9    'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full',
10    'Install', installValue) and (installValue = 1) then
11  begin
12    Result := True;
13    exit;
14  end;
15
16  if RegQueryDWordValue(HKLM,
17    'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client',
18    'Install', installValue) and (installValue = 1) then
19  begin
20    Result := True;
21  end;
22end;
23
24function InitializeSetup(): Boolean;
25begin
26  if not IsDotNet4Installed then
27  begin
28    MsgBox('.NET Framework 4.0 is required before installing this application.',
29      mbError, MB_OK);
30    Result := False;
31  end
32  else
33    Result := True;
34end;

This is usually enough for a prerequisite gate in a legacy installer.

Why Not Use The Release Value

A lot of blog posts about .NET detection focus on the Release registry value. That approach applies to .NET Framework 4.5 and later, not to plain 4.0.

If your requirement is specifically 4.0, checking Install under the v4\Client or v4\Full keys is the correct style.

If your real requirement is "4.0 or later," then a later-version detection strategy may be more appropriate than a strict 4.0 check.

Handling 32-Bit And 64-Bit Systems

Inno Setup registry access normally handles the common case correctly, but if you are targeting both 32-bit and 64-bit Windows, be conscious of registry view differences and your installer architecture settings.

For a standard .NET Framework check under these NDP keys, the basic script above is usually enough. If your installer already uses explicit 64-bit mode, keep your registry strategy consistent with the rest of the script.

Improving The User Experience

Failing early is good, but a better installer also tells the user what to do next. You can link them to the framework installer or documentation.

1function InitializeSetup(): Boolean;
2begin
3  if not IsDotNet4Installed then
4  begin
5    MsgBox(
6      '.NET Framework 4.0 is required. Please install it and run setup again.',
7      mbError, MB_OK);
8    Result := False;
9  end
10  else
11    Result := True;
12end;

If your deployment pipeline allows it, bundling or chaining the prerequisite installer may be even better than making the user resolve it manually.

Common Pitfalls

A common mistake is using the 4.5-plus Release registry check when the requirement is specifically .NET 4.0. That can produce incorrect detection logic.

Another mistake is checking only one profile when your application could run with either Client or Full. Be clear about the actual runtime requirement.

Developers also sometimes perform the prerequisite check too late in the installation process. InitializeSetup is the right place for a hard precondition.

Finally, be careful with copied detection snippets from old forums. Many were written for a very specific deployment scenario and do not explain which .NET version family they actually detect.

Summary

• For .NET Framework 4.0, check the Install DWORD under the v4\Client or v4\Full registry keys.
• Put the prerequisite gate in InitializeSetup so the installer fails early.
• Do not use the Release value when the target is exactly .NET 4.0.
• Decide whether your app needs the Full profile specifically or can run with either profile.
• Show a clear message telling the user what prerequisite is missing.
• Keep version-detection logic aligned with the actual runtime requirement, not with copied generic snippets.