could not install .NET frameworks 3.5 to PC

Question

23H2,22631.6649, Windows 機能エクスペリエンス パック 1000.22700.1108.0

in this windows version,could we install .NET Frameworks 3.5?
we use company PC, because of the windows version that we could not install Frameworks 3.5

Answer 1

Hi Sakuragi,

You can install .NET Framework 3.5 using the Windows Features dialog.

• Press Win + R, type optionalfeatures.exe, and click OK.
• Enable the .NET Framework 3.5 (includes .NET 2.0 and 3.0) checkbox.
• Click OK.

Note: If you receive any errors during the process, please post a screenshot of that error.

See also:

Install .NET Framework 3.5 | Microsoft Learn

Answer 2

Yes, .NET Framework 3.5 can still be installed and used on supported Windows versions, including current Windows 10/11 builds, but there are some important conditions and limitations.

Key points for .NET Framework 3.5 on recent Windows versions:

1. .NET Framework 3.5 is still supported
   • .NET Framework 3.5 SP1 remains a supported runtime until January 9, 2029.
   • It can be installed side-by-side with .NET Framework 4.x.
2. How it is provided on Windows 10/11
   • On Windows 10 and most Windows 11 builds, .NET Framework 3.5 is a Feature on Demand. The binaries are not preinstalled; Windows downloads them when the feature is enabled.
   • Starting with Windows 11 26H1 (build 28000), .NET Framework 3.5 is only available as a standalone installer and can no longer be added as a Windows component.
3. Why installation may fail on a company PC
   • Company devices often use WSUS or specific Group Policies that control Features on Demand and Windows Update access.
   • If Windows cannot download the .NET 3.5 feature from Windows Update or an alternate source, installation fails with errors such as 0x800F0906, 0x800F081F, 0x800F0907, or 0x800F0922.
   • In managed environments, the IT department must either:
     • Allow downloading Features on Demand directly from Windows Update, or
     • Provide a matching Windows installation source (ISO) and configure the Alternate source file path via Group Policy or DISM.
4. What to do on a managed (company) PC Because the device is company-managed, local users typically cannot change WSUS/Group Policy or provide OS media paths. The practical steps are:
   • Confirm with IT whether the current Windows build is before or after Windows 11 26H1:
     • If before 26H1: IT can enable .NET Framework 3.5 Features as a Windows feature (via Features on Demand, DISM, or Add Roles and Features on Server) using a proper source.
     • If on/after 26H1: IT must deploy the standalone .NET Framework 3.5 installer provided for that OS generation.
   • Ask IT to check for any of the known error codes (0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922) in installation logs and follow the documented resolution, including using a Windows ISO sources\sxs folder as the alternate source if required.

If the company’s policies or the specific Insider/enterprise build block .NET Framework 3.5 installation, only the administrator/IT department can change that configuration or deploy a supported installer.

---

References:

• Install .NET Framework on Windows and Windows Server
• Install .NET Framework 3.5 on Windows 10 and Windows Server
• .NET Framework 3.5 installation errors: 0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922
• Update for the .NET Framework 3.5 on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2