Installing .NET Framework 3.5 on Windows Server 2012 R2 Fails with Error Code 0x800F0906

I encountered this issue while working on a project for a client, involving server build automation.

The client provided me with a copy of their Windows Server 2012 R2 ISO, which I was using in my SCCM Build and Capture task sequence. As you can see from the screenshot, the Task Sequence includes copying the SXS folder onto the local system, in order to be able to install .NET Framework 3.5 (using the -Source parameter).

build-and-capture-ts-scrubed-265x300 Installing .NET Framework 3.5 on Windows Server 2012 R2 Fails with Error Code 0x800F0906

However, after the OS was installed, I noticed that the .NET Framework 3.5 and PowerShell options (which are also apart of the build) were not installed successfully. I checked, and confirmed that the SXS folder was still present (at the root of C:). So, I attempted to run the PowerShell install command manually to see if/why it failed. I encountered the following error.

build-and-capture-ts-scrubed-265x300 Installing .NET Framework 3.5 on Windows Server 2012 R2 Fails with Error Code 0x800F0906

This was odd, since it worked for my Build and Capture of Windows Server 2012. So, off to Google with the error code, and I came across this TechNet article which explained everything:

http://blogs.technet.com/b/askpfeplat/archive/2014/09/29/attempting-to-install-net-framework-3-5-on-windows-server-2012-r2-fails-with-error-code-0x800f0906-or-the-source-files-could-not-be-downloaded-even-when-supplying-source.aspx.

In a nutshell, there was a Security Update that was released that updated some of the .NET components (KB2966828). According to the TechNet article “If either of these updates are installed, you will run into the above issue if your server does not have access to the Internet to pull the updated components.”

The solution?

  1. Uninstalled the security update
  2. Install .Net Framework 3.5
  3. Reinstalled the update

Refer to the TechNet article for additional options/details. Hopefully this will help anyone that comes across this issue.

%d bloggers like this: