0x800F081F when using WSUS on Domain

Hey guys,

I ran into a snag when trying to install .NET 3.5 (from Programs and Features) on our Windows 10 Enterprise domain machines.

We recently started using Windows Server Update Services (WSUS) for our domain machines to save bandwidth when installing updates on everybody's PCs. I created a GPO and configured automatic installs, as well as specified the Intranet WSUS server connection. I did NOT disable checking online, so in Windows 7+8 there is an option to "check online for updates", and in Windows 10 we have this:


However, it seems to ONLY check the WSUS server when trying to add optional features, and thus causes an error as the files are not there. I did some searches, and found what was said to be a solution: enabling this policy:

Code:

Administrative Templates, System, “Specify settings for optional component installation and component repair” to “Enabled” and checking the box “Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)”

What's interesting is that this DID fix the problem... on Windows 8 and 8.1 machines. But on Windows 10 I still get the error. I have seen threads where people said that GPO fixed it for them, so I'm not sure why it isn't working in my case. Yes, I've done gpupdate /force several times, and it's not just one machine that has this problem, all of our W10 domain machines do it.

To clarify, we're using the x64 version of Windows 10 Enterprise. Not LTSB, just the normal one.

Does anyone have any other ideas? Yes, I know I can mount the install ISO and use "dism" to do it, but that's a huge pain when we have numerous domain computers. I also don't want to specify the .wim location in Group Policy, because we have a combination of 7, 8.1 and 10 computers on our domain and that would be problematic if I only point to a Windows 10 image. Really, the solution here SHOULD be to force it to check against Windows Update online rather than our WSUS server, but somehow it doesn't want to do that.

Here is our Windows Update GPO:

I have the same exact issue in my environment.

The GPO setting to bypass WSUS for adding features works on 2012 and 8.x but not on Windows 10. This is not just one or two but all Windows 10 Enterprise systems that have this issue.

If you watch the network, when you try to add a feature it still connects to the WSUS server instead of Microsoft directly, as though it's ignoring the GPO option.

If they are removed from the domain, it works fine downloading from Microsoft directly.

Using source media via command line also works, but I don't want to do that long term for many systems on the network.

Anyone found a fix yet?

It actually seems to have fixed itself recently, I didn't do anything. Might have been build 1511 of Windows that did it, might have been some other update, but I'm able to install .NET now and it does download the files from Microsoft.

It's still not working for me, even with 1511 and brand new imaged systems. I'm stumped.

seems i may need this:


I'll give it a go and provide my results

Ah yeah, that might be it. I have it auto-approving and auto-installing WSUS updates too so it probably did that.

Ok so I didn't need that update.

All I needed was under "Products" - Windows 10 Feature on Demand and that's it. Then approve the features I want to deploy and voila.

I'm not sure why it doesn't allow the other GPO setting though, you would think that it wouldn't ignore talking directly to Microsoft.

The only updates that can be approved under this product are .net 3.5, directx, insider hub and language packs.

I hope this post helps someone else. Not much else out there that explains how to solve this without using media.