Windows 8.1 unable to install .NET Framework 3.5 0*800F0906

Question

After trying to install .net 3.5 via the program and features (see below). I was getting unable to install error 800F0906

I am using windows 8.1.

Answer 1

You probably have a GPO that blocks updates directly from Microsoft. Did not check the WSUS server to see if the required packages were present. Simply made these registry changes and the PC was able to pull down the updates. Note, no need to undo these as the GPO will do it for you.

----- Below this line is the actual content to create your own .REG file -----

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate]
"DisableWindowsUpdateAccess"=dword:00000000
"DisableWindowsUpdateAccessMode"=dword:00000000

Answer 2

I was facing same issue.

Cause: under gpeditor, MS update service location was set to some local WSUS.

Solution: copy that URL and set MS update service location disable or Not configured from gpeditor. now try steps from feature on/off Windows to install .Net Framework 3.5. after successfully completion revert WSUS update service URL.

[for MS update service location: under Run=> gpedit.msc navigate to Comp Conf->Admin Templates->Win Components->Win Update->"Specify internet MS update service location" ]

if MS update service location is not configured then check internet connection otherwise it's some other related issue.

Answer 3

check your windows firewall. That must be turned on.

Answer 4

Found link that identifies two Windows Updates as the problem if DISM and the offline installer do not work. Uninstall KB2966826 and KB2966828, then try installing 3.5 from programs and features. It worked for me.

By Chris Wardario

Answer 5

I had to log in as a local admin account, rather than runas to get it to download the missing binaries.

Answer 6

I ran into this issue today and it ended up being a problem with the WSUS server not having the necessary updates synced. To test this, I removed the PC from the policy that points the the WSUS server and adding the feature through the control panel is now working. I don't know if this will apply to everyone but I figured I would add my two cents.