Skip to main content

0x800F0906 and 0x800F081F Error Messages While Installing .NET Framework 3.5 in Windows 8 and 8.1

Ever since I experienced many of the problems of enabling (installing) .NET Framework 3.5 feature via Windows Update on Windows 8.x days or even weeks or month after my initial Windows installation I'v I've been quick to make that the first thing I install on a new clean Windows 8.x installation.

In my experience you will still "always" need .NET 2.0 or 3.5 (.NET Framework 3.5 feature set in Windows 8.x includes 3.0 and 2.0 also), so now I always install it righ away.

Most of the solutions on the internet tells you to grab the DVD/Mount ISO and point the 'dism.exe' to the SXS folder and enable it with the source files there. For a lot of us, those files aren't available when you need it, or not at all.

I just had this problem hit me again, as I just started a new consultancy assignment and got a new laptop from the work place I had to use. It came already installed with Windows 8.1 (over the network) and with all software and updates. Hence, enabling .NET Framework 3.5 (which wasn't enabled) I hit an error while installing from Windows Update: Error: 0x800F0906.

A long story short, here is what I did to actually make my computer enable .NET Framework 3.5 via Windows Update. The computer was also configured to use WSUS, but it was not locked down to deny me installing updates from Windows Updates (more/newer than those updates the IT department had approved). So if you are locked to only local WSUS this might not work. Or you can beg your IT department to enable this Group Policy (see below).

  1. Uninstall these three security updates (or those that was on my system):
    1. KB2966826
    2. KB2966827
    3. KB2966828
  2. In Local Group Policy, I enabled 'Specify settings for optional component installation and component repair' under Computer Configuration > Administrative Templates > System. See illustration below.

The screen shot for this step
The screen shot for this step

Just to be sure settings were in effect, I rebooted. I could probably just force a gpupdate as well..

My next attempt to install .NET Framework 3.5 was suddenly a success!!

Source:

  • http://www.askvg.com/fix-0x800f0906-and-0x800f081f-error-messages-while-installing-net-framework-3-5-in-windows-8/
  • http://support.microsoft.com/en-us/kb/2734782

Comments

Popular posts from this blog

Force Dell BIOS Upgrade

I just experienced a problem upgrading a Huawei N8300 OceanStor NAS Engine node (OEM'ed Dell PowerEdge R710 server). Running the linux binary update file looked good and it asked me to reboot. After reboot the same old v2.1.15 BIOS was there, not the latest v6.4.0 (as of writing this small post). Next up was creating a FreeDOS Bootable ISO with the bios update program included (see this page for how to do that in Windows). Running the BIOS upgrade program from FreeDOS (virtual media and DRAC) I got this error: Cannot use a "Dell System PowerEdge R710" BIOS in a " -  " Pres any key to exit. ROM update not performed. After some googleing I found the solution on Dell Community Forum - use the /FORCETYPE option. So to force the update, I just ran the update package with that option (I had renamed the file for 8.3 DOS filename): R710-640.exe /FORCETYPE And thats it. v6.4.0 BIOS up and running :)

How to configure multiple VLANs on QNAP TS-869U

It's unbelievable that QNAP still doesn't support multiple VLANs on a single bond0 interface via GUI when they now just released the QTS v4.1.0 NAS Operation System for QNAP. The underlying Linux OS (QTS) does support it, and there should at least not be any problems with Intel chipsets. Some are reporting problems with Marvell.. but I haven't tried. I wanted to use the QNAP as a iSCSI storage for my LAB using a second interface while having full redundancy and get max bandwith (2x1GbE) for my ESXi hosts, and I didn't want that interface routed. At the same time I of course need the possibility to manage the QNAP system via the main interface, which is routed. This CLI "hack" will at configure the QNAP for a second VLAN interface that will be persistent during reboots. It's not been verified that it works after an upgrade of the firmware, but I presumed it will. To get this to work I presume you already have the following working: Network onfigured