This guide walks you through fixing the Windows error 0x800f081f, which appears when you try to install .NET Framework 3.5 (which includes 2.0 and 3.0) on Windows 10 or 11. The error means Windows could not find the required feature files in its local source or Windows Update. You’ll learn several reliable methods to get .NET Framework 3.5 installed, from using the Windows Features dialog to manually installing from the installation media.
What You’ll Need
- Administrator access to the Windows PC
- An internet connection (for most methods)
- Windows installation media (ISO or USB) for the offline method – optional but useful
Step-by-Step
- Try the Windows Features dialog first. Press Windows + R, type
optionalfeatures, and press Enter. In the Windows Features window, check the box for “.NET Framework 3.5 (includes .NET 2.0 and 3.0)”. Click OK. Windows will search for the files and install them. If it succeeds, you’re done. If you get error 0x800f081f, continue. - Check Windows Update settings. Sometimes Windows Update is set to not deliver feature files. Open Settings > Update & Security > Windows Update (or Settings > Windows Update on Windows 11). Click “Advanced options” and ensure “Receive updates for other Microsoft products” is turned on. Then try Step 1 again.
- Use DISM with Windows Update. Open Command Prompt as administrator (press Windows + X and choose “Command Prompt (Admin)” or “Terminal (Admin)”). Type the following and press Enter:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:C:\Windows\WinSxS
This tells DISM to use the local component store. If it works, you’ll see “The operation completed successfully.” If you get error 0x800f081f again, proceed to the next step. - Use DISM with Windows installation media. You’ll need a Windows ISO or USB drive. Mount the ISO (double-click it) or insert the USB. Note the drive letter (e.g., E:). Then run:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:E:\sources\sxs
ReplaceE:with your actual drive letter. If you’re on a 64-bit system, the path isE:\sources\sxsas shown. If you’re on a 32-bit system, useE:\sources\sxsas well (the sxs folder is the same). This method bypasses Windows Update entirely. - Use the Windows Features dialog with installation media. If DISM works, you’re done. If not, you can also try going back to the Windows Features dialog and clicking “Have disk”? Actually, that’s not the right path. Instead, you can use the
dismcommand with the/LimitAccessflag to prevent Windows Update from being used:DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:E:\sources\sxs /LimitAccess
This forces DISM to only use the source you specify. - Verify installation. After any successful method, open Command Prompt and type
dism /online /get-features | find "NetFx3"to see the state. It should show “Enabled”. You can also check in the Windows Features dialog – the box should be checked.
Common Mistakes
- Using the wrong drive letter. If you mounted an ISO, the drive letter might be different than you think. Check File Explorer to confirm.
- Not running as administrator. The DISM and optionalfeatures commands require admin rights. If you see “Access denied” or “Error 740”, you’re not running as admin.
- Typing the feature name incorrectly. The feature name is
NetFx3– note the capital F and x. TypingNetFX3orNetFx3is fine, but avoid spaces. - Using a 32-bit source on a 64-bit system. The source path should be the same regardless of architecture, but ensure the ISO matches your Windows version (Home vs Pro, etc.) – though for .NET it usually doesn’t matter.
- Forgetting to mount the ISO. If you double-click an ISO, it mounts as a drive. If you extracted it to a folder, use that folder path instead (e.g.,
C:\WinISO\sources\sxs).
Tips
- Run Windows Update first. Ensure your system is fully updated before attempting the install. Some updates fix known issues with .NET installation.
- Use the /All switch. The
/Allswitch in DISM enables all parent features, which is recommended for .NET 3.5. - If you have a Windows installation USB, use it. It’s often more reliable than an ISO because the drive letter is consistent.
- Consider using the Windows 10/11 Media Creation Tool to download a fresh ISO if you don’t have one. It’s free from Microsoft.
- After installation, you can uninstall it later via the same Windows Features dialog if needed.
Troubleshooting
If none of the above works, try these additional steps:
- Check for pending Windows updates. Sometimes a pending update blocks the feature installation. Restart your PC and try again.
- Run the System File Checker. Open Command Prompt as admin and run
sfc /scannow. This repairs corrupted system files that might interfere. - Use the Windows Update Catalog. Go to the Microsoft Update Catalog website and search for “.NET Framework 3.5” for your Windows version. Download the .cab file, then run:
DISM /Online /Add-Package /PackagePath:C:\path\to\file.cab - Check if the .NET feature is already partially installed. Sometimes the feature shows as enabled but is corrupted. Disable it (uncheck the box), restart, then re-enable it.
- If you’re on a domain or enterprise PC, Group Policy might block feature installation. Contact your IT administrator.
- As a last resort, you can try the Windows Media Creation Tool to perform an in-place upgrade (keep files and apps) which often repairs the component store.
Frequently Asked Questions
Why does .NET Framework 3.5 need to be installed separately?
.NET Framework 3.5 is an older version that is not enabled by default on Windows 10/11. Microsoft removed it from the default installation to reduce attack surface and disk usage, but it’s available as a feature for compatibility with older applications.
Will this error affect my existing .NET Framework 4.x installations?
No. .NET Framework 3.5 and 4.x are independent. Error 0x800f081f only affects the 3.5 installation. Your existing 4.x versions will continue to work normally.
Can I install .NET Framework 3.5 offline without installation media?
Yes, you can use the Windows Update Catalog to download the .cab file and install it with DISM, as described in Troubleshooting. This requires internet access to download the file, but not to install it.
Is it safe to use DISM to enable features?
Yes, DISM is a built-in Windows tool designed for this purpose. As long as you run it as administrator and use the correct commands, it is safe. It won’t affect your personal files.
Why does the error say “source files could not be found”?
This means Windows couldn’t locate the necessary files in the component store or on Windows Update. This is exactly what 0x800f081f indicates. Using the installation media provides the files directly.
How long does the installation take?
Typically, it takes 2-5 minutes if using DISM with media. If using Windows Update, it may take longer depending on your internet speed and system performance.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Apps Not Downloading From Play Store
- Secure a Samsung Galaxy After a Zero-Day Disclosure
- What to Check Before Installing Linux Alongside Windows
- Fix OEM Activation Error 0xc004c060 in Windows 10
- Why Does My App Run One Query for the List and One per Item?
- Fix Google Chrome Has Stopped Working