Insert or mount the Windows Server 2012 R2 installation media. Assume the drive letter is D: . Open PowerShell/CMD: Open as Administrator. Run DISM Command: Execute the following command: powershell
This article provides a definitive, step-by-step walkthrough for obtaining a version of the Microsoft-Windows-NetFx3-OnDemand-Package.cab file specifically for Windows Server 2012 R2 , followed by guaranteed installation methods.
DISM tried to reach Windows Update and failed. Solution: Add the /limitaccess flag to prevent online checks, or configure your local group policy: Computer Configuration → Administrative Templates → System → Specify settings for optional component installation and component repair → Enable → Alternate source path.
In the Path field, enter the path to your mounted media: E:\sources\sxs (again, change E to your actual drive letter). Click and then Install . Where to Find microsoft-windows-netfx3-ondemand-package.cab Insert or mount the Windows Server 2012 R2
This is the most reliable and secure method. You will need an ISO or DVD of the same operating system version.
How to Acquire the microsoft-windows-netfx3-ondemand-package.cab
If the server is managed by WSUS, ensure the updates are synchronized and the "Features on Demand" category is enabled in the WSUS console options. Run DISM Command: Execute the following command: powershell
reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" /v Install # Should return: 0x1
If you are running a or a physical bare-metal server. Share public link
The NetFX3 feature includes both .NET Framework 2.0 and 3.5. In Server 2012 R2, Microsoft introduced a "Feature on Demand" model. Instead of storing feature files directly in the WinSxS folder (saving disk space), the server is designed to fetch required binaries from Windows Update. In the Path field, enter the path to
dism /online /enable-feature /featurename:NetFx3 /all /source:"C:\Temp" /limitaccess
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs Server Fault Method 2: Using Server Manager (GUI)