Windows 11 26H1 Beta: .NET Framework 3.5 standalone installer refuses to install despite meeting its minimum OS requirement

Coolboy_PlayzYT 20 Reputation points
2026-11-13T06:00:16.4166667+00:00

Hello!

I'm having trouble installing .NET Framework 3.5 on my Windows 11 Insider Preview installation.

System information

  • OS: Windows 11 Home Insider Preview Single Language

Version: 26H1

Build: 28020.3445

Insider channel: Beta

Architecture: 64-bit

Problem

I have several older applications that require .NET Framework 3.5 to run. They all display the following error:

"This application could not be started. You must enable the .NET Framework from the Windows Features dialog box."

However, .NET Framework 3.5 does not appear in Windows Features on my Windows installation.

I understand that Windows 11 version 26H1 and newer require the standalone .NET Framework 3.5 installer rather than the traditional Windows Features or DISM installation method.

I downloaded the official standalone installer (KB5087077), version 1.0.03391.144, but it does not install the framework.

Installer log findings

The installer log contains the following information:

OSBuildVersion = 28020

Blocker_UnsupportedOS =
Microsoft .NET Framework 3.5 (5087077) requires
Windows version 10.0.28000.1 or newer.

Your current Windows version is 10.0.28020.3442.

The installer then evaluates:

Condition '(OSMajorVersion = 10 AND OSMinorVersion = 0
AND OSBuildVersion >= 28000) OR (OSMajorVersion > 10)'
evaluates to true.

Despite this, Blocker_UnsupportedOS is set to true, and the installer skips the installation.

The installer finishes with result code 0x0, but no components are installed.

Additional findings

I performed several checks:

The .NET Framework 3.5 registry key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5) does not exist.

The following runtime files are missing:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll

 `C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll`

 

    `C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorlib.dll`

    

    Windows Installer contains six registered .NET Framework 3.5 components:

    

       x64 Registry Components

       

          x64 Runtime Components

          

             x64 GAC Components

             

                x86 Registry Components

                

                   x86 Runtime Components

                   

                      x86 GAC Components

                      

                      All six components have version `1.0.03455.155`, which is newer than the downloaded standalone installer's version `1.0.03391.144`.

                      

                      All six components return `5` when queried through the Windows Installer API's `ProductState` property. Their cached MSI files also exist under `C:\Windows\Installer`.

                      

                      The standalone installer's log detects these components as related packages, with some marked as `Downgrade`, while others are marked `None`. Their package states are reported as `Obsolete`.

                      

                      DISM `/Online /Enable-Feature /FeatureName:NetFx3 /All` fails with error `0x800f080c`.

Troubleshooting already attempted

Downloaded the official KB5087077 standalone installer again.

Restarted Windows.

Ran the Microsoft .NET Framework Repair Tool.

Checked the .NET Framework registry entries.

Checked the actual runtime DLL files.

Inspected the Windows Installer registrations and cached MSI packages.

Checked Windows Update for optional updates.

None of these steps resolved the issue.

My questions

Why does the KB5087077 installer report that my OS does not meet its minimum requirement when build 28020 is newer than the stated minimum of 28000.1?

Could the existing Windows Installer registrations for version 1.0.03455.155 be preventing the older standalone installer from installing?

What is the recommended way to repair this inconsistent .NET Framework 3.5 installation state on Windows 11 26H1 Beta?

I would appreciate any guidance on how to get .NET Framework 3.5 installed correctly without manually deleting Windows Installer registrations or damaging the Windows installation.

Thank you!

Moved from: Windows for home | Windows 11 | Windows update

Windows Insider program | Windows Insider preview | Install, activate, and Windows update

1 answer

Sort by: Most helpful
  1. Clary-N 19,340 Reputation points Microsoft External Staff Moderator
    2026-11-17T00:13:06.8866667+00:00

    Hi Coolboy_PlayzYT,

    Thanks for taking the time to document everything so thoroughly. You've already done some really useful investigation here.

    Based on your logs, your Windows build does meet the minimum requirement for the standalone .NET Framework 3.5 installer, so the unsupported OS message doesn't seem consistent with the reported version check. However, the exact reason the installer is triggering this blocker isn't clear from the logs alone.

    I also noticed that your system has registered .NET Framework 3.5 components with a newer version than the installer you're trying to use. This could be contributing to the installation failure, particularly since the actual runtime files are missing. However, I can't confirm that this is the exact cause.

    Since you've already tried several troubleshooting steps, I wouldn't recommend manually deleting the Windows Installer registrations or cached MSI files. For now, I'd suggest checking whether a newer standalone installer is available from the official .NET Framework 3.5 download page. If the latest installer still fails, a Windows repair installation may be worth considering to address possible system inconsistencies, although it isn't guaranteed to resolve this particular issue.

    Since you're running an Insider Preview build, I'd also recommend submitting a report through Feedback Hub, including the installer logs and the version mismatch you've identified. This could help the engineering team investigate a possible installer compatibility issue.

    As this is a user-to-user support forum, I can help with general guidance, but some technical issues may need a closer look. Since you're using an Insider Preview build, sharing your findings through Feedback Hub would be a helpful next step.

    I hope this helps point you in the right direction.

    Was this answer helpful?

    2 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.