.NET: Microsoft Technologies based on the .NET software framework. Runtime: An environment required to run apps that aren't compiled to machine language.
For .NET Framework 3.5 getting stuck on Downloading required files, the supported fixes are to stop relying on the online download path and install from matching Windows installation media or ISO.
Since SFC, repair commands, driver checks, and even reinstalling Windows were already tried, the next steps are:
- Use a Windows ISO or installation media that matches the installed Windows version.
- On Windows 10, create or obtain an ISO for the installed version.
- Mount the ISO so it gets a drive letter.
- Point .NET 3.5 installation to the
sources\sxsfolder on that media.- The documented DISM command is:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:<drive>:\sources\sxs /LimitAccess- Example:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccessLimitAccessforces Windows to use the local source instead of trying Windows Update again. - If the error is 0x800F0906, check update connectivity.
- This error means Windows could not download the source files.
- Verify the PC can reach Windows Update.
- If the PC is managed by WSUS or policy, enable Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).
- If the error is 0x800F0907, check Group Policy.
- This error indicates policy is blocking the download path.
- The relevant policy is Specify settings for optional component installation and component repair.
- After changing policy, run:
gpupdate /force - If the error is 0x800F081F, validate the source path.
- Make sure the full path is correct:
X:\sources\sxs - Make sure the files are readable from the affected PC.
- If using a share, the account needs at least Read access.
- If the source is incomplete or from the wrong Windows version, use a different installation source.
- Make sure the full path is correct:
- If Windows Features itself hangs, run System File Checker again only if needed to confirm file integrity:
Run it from an elevated Command Prompt and do not close the window until verification reaches 100%.sfc /scannow
For a home gaming scenario, the most direct path is usually:
- mount the correct Windows ISO,
- run the DISM command with
Source:<drive>:\sources\sxs, - avoid the online installer path.
References:
- .NET Framework 3.5 deployment errors and resolution steps
- .NET Framework 3.5 installation errors: 0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922
- .NET Framework 3.5 installation errors: 0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922
- Use the System File Checker tool to repair missing or corrupted system files