Ramblings from another nerd on the grid
Yesterday I got around to adding a few Lenovo ThinkVantage technologies to my ThinkPad W510. One I always like to add is the power management driver, and Power Manager. Unfortunately Power Manager wouldn’t completely install because one of it’s prerequisites wasn’t on my machine and could not be found.
I am referring to the .Net Frameworks v3.5. Normally the update client would grab the bits from your WSUS or our WU servers but they aren’t present there. Or if they are, they were not found and the install failed.
I first saw the following screenshot. Like most anyone, I clicked the first option fully expecting the sources to be found.
Nope. I received Error code: 0x800F0906 on that attempt (and a couple of retries). How rude!
Here’s the thing, I am connected to the Internet. At the time of the error I was in my home office using my fiber connection. So connectivity and bandwidth weren’t the issues. I wondered if the Hyper-V switch might be causing a problem. So I removed it and retried. Nope, still no dice.
I discovered a workaround. You can use DISM to install the frameworks from the Windows 8 install DVD, stick or location you used. In my case, I popped the DVD into the external Sony DVD burner and issued the following command:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:x:\sources\sxs /LimitAccess
Replace x: with the location of your sources (mine was e:). This should install what you need and get you rolling. I am still checking to see if this was introduced because I was not VPN’d or using DirectAcccess. The machine is domain joined and was likely looking for the internal WSUS server.
Thought this might be helpful if you hit this speed bump.
Hi Keith. You don't need to install it in this complicated way. Get into /Control Panel/, /Programs/, /Turn Windows features on and off/, select Netframework 3.5, click OK. Windows will require Internet connection to download certain packages during the process. It'll be done in two minutes.
Thanks Fink. I of course tried that first. Nada. No dice.
Many thanx Dear. I wasted saveral hours trying to update/enable .NET3.5 but kept on getting same error. But this command did the magic.
How do we know if the Windows team knows to make this work as it did in Windows Server 2008 R2?
Thanks I was facing same problem and its resolved with the solution you suggested.
Thanks a lot for this post. It worked for me as well and kept from getting frustrated following Microsoft's suggestions which was basically making me go around in circles.