Symptoms
After you install security update 2966827 or 2966828 (described in Microsoft Security Bulletin MS14-046) for the Microsoft .NET Framework 3.5, and then you try to enable the optional Microsoft .NET Framework 3.5 feature in Windows Features for the first time, the feature does not install. You may notice this failure if you 'stage' the installation before you add the Microsoft .NET Framework 3.5 feature.
When this problem occurs, you may receive an error message that resembles one of the following.
Try Windows Server 2012 R2 on Microsoft Evaluation Center We recently announced Windows Server 2022 in preview, bringing you advanced multi-layer security, unique hybrid capabilities with Azure, and a flexible application platform. Click to learn more. These highlights of the full Windows 8.1 and Windows Server 2012 R2 privacy statement (“Windows privacy statement”) explain at a high level some of the data collection and use practices of Windows 8.1 and Windows Server 2012 R2 (“Windows”). They focus on online features and aren't intended to be an exhaustive description.
Error code | Error messages |
|---|---|
0x800F0906 | The source files could not be downloaded. |
0x800F081F | The source files could not be found. |
Microsoft Edge native support as of Stable version 88 for Apple Silicon Macs. Microsoft Edge does not support Chromebooks. Microsoft Edge support on Windows 7 and Windows Server 2008 R2 extended to January 15, 2022. Microsoft Edge support for Apple Silicon Macs. Microsoft RDS is the new expanded and renamed Microsoft Terminal Services. In this post I will document the implementation of RDS in my home lab using an ‘all-in-one’ configuration. VBoring Blog Series: Setup Remote Desktop Services in Windows Server 2012 R2; Setup RD Licensing Role on Windows Server 2012 R2.
Cause
This problem occurs because security updates 2966827 and 2966828 for Microsoft Security Bulletin MS14-046 for the .NET Framework 3.5 require metadata that is added to the system only if the Microsoft .NET Framework 3.5 feature is enabled on the system.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section. The issue is now resolved by update 3005628. The workaround that is provided in the next section still unblocks customers, depending on their situation.
Workaround
Windows Server Versions
To resolve the issue, install update 3005628. To work around this issue, use one of the following workarounds, as appropriate for your situation:
Turn on the Microsoft .NET Framework 3.5 feature before you install security update 2966827 or 2966828. For more information about how to turn Windows features on or off, go to the following Microsoft webpage:
Turn Windows features on or offYou can also use Deployment Image Servicing and Management (DISM) or any supported managed update system to add the Microsoft .NET Framework 3.5 feature. For more information about how to deploy the .NET Framework 3.5 by using DISM, go to the following Microsoft webpage:
If security update 2966827 or 2966828 has already been installed on the system, temporarily uninstall the update, enable .NET Framework 3.5, and then reinstall the security update.
If you see this behavior from Windows Server Update Services (WSUS), Microsoft Intune, or System Center Configuration Manager environments, refer to the following documentation:
To build a supported repair feature configuration environment: http://technet.microsoft.com/en-us/library/jj127275.aspx
To configure a Windows repair source: http://technet.microsoft.com/en-us/library/hh825020.aspx
More Information
Windows Server
The information in this article applies to:
Microsoft Edge Windows Server 2012 R2 Install
The Microsoft .NET Framework 3.5