Windows 10 Enterprise 1909 Fails to install Optional Features

Are you using an uodate management system? WSUS, SCCM, or 3rd party.

Sounds like features on demand can't reach windows update, in which case the error is expected behavior.

Cliff

I am using WSUS

My other Windows 10 computer winver 1709 on same network and connected to same Windows Update Server WSUS works fine.

Is there a settings on Windows 10 I am missing?

It's not unique to 1809.  To reduce install size,  icrosoft has increasingly been leaving "optional features" out of an image Or it removes the binary installers from an installed OS if a month or so passes and no install was requested.

This is called "Features On Demand" and has been in windows in one form or another since windows 8.

It does mean that two installs of windows can behave differently depending on when they were installed, which specific features were installed, etc.  Once the binaries are gone, windows attempts to get them (and the list) from the update URL... In your case WSUS. Because WSUS doesn't fully support FOD, this can fail.

You'd usually want to install the feature via DISM and appropriate media.  Alternatively you'd embed it on a corporate image.  But there IS a group policy that can tell windows to get optional features and drivers from Windows Update in addition to WSUS.  

So several ways to solve your problem, but each requires planning and assisting risk and pros and cons.

I agree, nothing special in 1909 in this respect. What I used on 1909 lately, was a batch that removed the wsus connection temporarily (deleted the registry key with the wsus address), restarted the windows update service, then used dism to get the desired RSAT optional features, then set the wsus address straight again and restarted windows update once more.

McKnife

I just tried that still no luck.

1909 is a problem should not have to do anything like this.

I stopped the BITS and wuauserv services

Exported  then Deleted the reg key for Windows Update
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Started BITS and wuauserv services


C:\WINDOWS\system32>DISM.exe /Online /add-capability /CapabilityName:Rsat.WSUS.Tools~~~~0.0.1.0

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================]

Error: 12175

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

Got one warning in the DISM log

2019-11-23 09:00:37, Warning               DISM   DISM Provider Store: PID=11580 TID=13944 Failed to load the provider: C:\Users\Thomas R Grassi Jr\AppData\Local\Temp\107F4948-E034-4A58-8729-BB0435249475\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Any ideas

My remembrance fooled me, I didn't delete the WSUS address but instead set the registry value for usewsusserver to zero. Try that.

McKnife

No change.

Same warning/error in DISM log

very strange

This time
I stopped the BITS and wuauserv services

Change  UseWUServer   from 1 to 0 (zero)

Started BITS and wuauserv services

ran this

C:\WINDOWS\system32>DISM.exe /Online /add-capability /CapabilityName:Rsat.WSUS.Tools~~~~0.0.1.0

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================]

Error: 12175

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>
DISM Log same

SM Provider Store: PID=5872 TID=1664 Failed to load the provider: C:\Users\Thomas R Grassi Jr\AppData\Local\Temp\B68ABF43-FC76-430D-84AD-0632C333B052\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Try that on a test system again. No need to stop BITS, by the way.

I do not have a test computer at this time.

Should I restart computer after changing the registry?

No. You don't have any test machine? Set up a VM, then.

McKnife I would rather test on this computer

any other suggestions.

No idea, if you are not willing to install Hyper-V on your machine and just install a VM, to see for yourself that it ought to "just work" on a normal machine, I can only tell you, that it works here (although it took quite long as compared to other features).
Please try other features like these:

DISM.exe /Online /add-capability /CapabilityName:Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 /CapabilityName:Rsat.BitLocker.Recovery.Tools~~~~0.0.1.0 /CapabilityName:Rsat.CertificateServices.Tools~~~~0.0.1.0 /CapabilityName:Rsat.Dns.Tools~~~~0.0.1.0 /CapabilityName:Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0 /CapabilityName:Rsat.FileServices.Tools~~~~0.0.1.0

Select allOpen in new window

Do these install alright?

McKnife,

Changed the registry key to 0 again

restarted juast the wuauserv service

ran

C:\WINDOWS\system32>DISM.exe /Online /add-capability /CapabilityName:Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 /CapabilityName:Rsat.BitLocker.Recovery.Tools~~~~0.0.1.0 /CapabilityName:Rsat.CertificateServices.Tools~~~~0.0.1.0 /CapabilityName:Rsat.Dns.Tools~~~~0.0.1.0 /CapabilityName:Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0 /CapabilityName:Rsat.FileServices.Tools~~~~0.0.1.0

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================]

Error: 12175

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>


Same error

It starts the bar gets to 5.9 % then goes to 100% and fails.

Very puzzling that I am trying to install Microsoft add ons on a Microsoft OS and I have this problem

It's not puzzling and not strange. This is how features on demand works.  If they were embedded in the OS then they wouldn't be "on demand."

Truthfully I don't  know what deleti g those registry keys mightve permanently done to the OS.  As McKnife said, these things are best done in a test VM before doing so live. And as McKnife confirmed from what I said, this is NOT new to 1909.

Not is 1909 broken.  I just installed RSAT on my test VM without issue via features on demand.

The progress bar behavior is exactly what one would expect when FoD fails.  5 to 6% completion is normal when it starts cataloging installed features and available packages already on the local install.  Then it fails to go further because it can't find a valid source for the new requested package. Aka it cannot connect to WU.

You keep insisting this is an aberration or believing this is brokem on 1909. Neither is true.  I can seen, fixed, and could replicate this right now on a machine on 1709 using other optional features (since RSAT wasn't an optional feature in 17xx)... It is what it was is.

ok if not broken then why can’t I install any optional applications
I just applied some windows 10 1909 updates restarted my computer but still getting same error

any ideas

"ok if not broken then why can’t I install any optional applications"

I've explained this. Your machine so failing to reach WI because of WSUS. And deleting registry keys probably made things worse.
Not sure how many ways to explain that.

But if you have enterprise then you have access to 1909 enterprise media via VL.

As a troubleshooting step, I recommend downloading and creating a clean install source then attempt to install the tools via DISM and use the WIM as a source path. You'll probably find that it works. If you do so using the appropriate commands.

If you are able to install updates with usewsusserver set to 0, it shows that you are using online update successfully.

About dism: no idea. I would do a repair installation now, if I were you and retry afterwards.

it is a 1909 issue no question

I just installed fresh version of Windows 10 Professional.

Build 10240

Then ran the MediaCreationTool1909

After the restart the same exact failures on installing

When is Microsoft going to fix things

How do I go back to 1709


This is really a mess

I have others at work with same issue on 1909

WA the 10240 machine joined to the domain that uses WSUS?!, either before or after the upgrade to 1609? Or was this test done on an isolated non-dokain/non-wsus network eith the test machine left in a workgroup?

See if you have updated 1909 before you retry. Since it works for both me and Cliff, it's hard to believe 1909 has anything to do with your error.
Again the code that I use:

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU /v UseWUServer /t REG_DWORD /d 0 /f
net stop wuauserv & net start wuauserv
DISM.exe /Online /add-capability /CapabilityName:Rsat.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0 /CapabilityName:Rsat.BitLocker.Recovery.Tools~~~~0.0.1.0 /CapabilityName:Rsat.CertificateServices.Tools~~~~0.0.1.0 /CapabilityName:Rsat.Dns.Tools~~~~0.0.1.0 /CapabilityName:Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0 /CapabilityName:Rsat.FileServices.Tools~~~~0.0.1.0
reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU /v UseWUServer /t REG_DWORD /d 1 /f
net stop wuauserv & net start wuauserv

Select allOpen in new window

Thank you

Cliff, 100% correct.  Features were attempting to install via my wsus server and failing. Changing the local group policy and pointing the download to Microsoft solved this issue, thank you!