Windows 2016 Netfx3 feature payload always removed when disabled

Question

_{Friday, October 14, 2016 11:56 AM}

Business case: We always add netfx3 components back to WIM to ease operations for admins. Enable feature (with CAB source), disable feature. In result, bits are in WIM, deployed and always available when required, no looking around for SXS files and guiding less experienced admins.

This worked great in 2012 and 2012R2. Now with 2016, when I disable Netfx3 feature, is always removes payload and moves to DisabledWithPayloadRemoved state.

My test WIM is 2016 Datacenter Sept23 refresh.

Below are minimal commands to show the issue, ran on Windows 10 1607.

PS C:\WINDOWS\system32> Mount-WindowsImage -ImagePath "C:\Temp\Windows2016-x64-enusDc.WIM" -Path C:\mnt\ -Index 1


Path          : C:\mnt\
Online        : False
RestartNeeded : False



PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Path C:\mnt\ |? featurename -eq 'netfx3'|fl *


FeatureName      : NetFx3
State            : DisabledWithPayloadRemoved
Path             : C:\mnt\
Online           : False
WinPath          :
SysDrivePath     :
RestartNeeded    : False
LogPath          : C:\WINDOWS\Logs\DISM\dism.log
ScratchDirectory :
LogLevel         : WarningsInfo



PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -FeatureName netfx3 -LimitAccess -Source C:\WIM\FeatureSXS\Windows2016\x64\ -Path C:\mnt\ -all


Path          : C:\mnt\
Online        : False
RestartNeeded : False



PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Path C:\mnt\ |? featurename -eq 'netfx3'|fl *


FeatureName      : NetFx3
State            : Enabled
Path             : C:\mnt\
Online           : False
WinPath          :
SysDrivePath     :
RestartNeeded    : False
LogPath          : C:\WINDOWS\Logs\DISM\dism.log
ScratchDirectory :
LogLevel         : WarningsInfo



PS C:\WINDOWS\system32> Disable-WindowsOptionalFeature -FeatureName netfx3 -Path C:\mnt\


Path          : C:\mnt\
Online        : False
RestartNeeded : False



PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Path C:\mnt\ |? featurename -eq 'netfx3'|fl *


FeatureName      : NetFx3
State            : DisabledWithPayloadRemoved
Path             : C:\mnt\
Online           : False
WinPath          :
SysDrivePath     :
RestartNeeded    : False
LogPath          : C:\WINDOWS\Logs\DISM\dism.log
ScratchDirectory :
LogLevel         : WarningsInfo

Is this some kind of bug in servicing stack or manifests? Disable-WindowsOptionalFeature has "-remove" parameter but not "-DoNotRemove"...

All replies (5)

_{Monday, October 17, 2016 9:47 AM}

Hi Don,

I have test this issue on my server 2016, encountered the similar issue with yours.

As server 2016 is released not too long, so I suggest you could keep your system up-to-date and wait if it has resolution for this issue.

My current OS info:

OS Name:                   Microsoft Windows Server 2016

OS Version:                10.0.14393 N/A Build 14393

Thanks again for posting here and understanding!

If this issue is urgent, our suggestion is you submit a service request to MS Professional tech support service so that a dedicated Support Professional can give more rapid support. You can find the phone number in the following link.

http://support.microsoft.com/gp/customer-service-phone-numbers/en-us

Best regards,

Andy

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, October 17, 2016 9:03 PM}

Good to know that you have a repro. It's not a critical issue (we'll just enable netfx3 permanently until fix) so take your time.

_{Tuesday, October 18, 2016 6:16 AM}

Good to know that you have a repro. It's not a critical issue (we'll just enable netfx3 permanently until fix) so take your time.

Good news, Don。

Have a nice day!

Best regards,

Andy

_{Tuesday, June 12, 2018 5:49 AM}

Hi,
I know this is very old thread, but apparently even after 2 years issue still exists even in  2016 OS Build 14393.2248.

Don't you think its right about time to fix it?

I want to allow my users to add .NET 3.5 feature when required, without adding any additional installation sources, HOWEVER I don't want to get this feature enabled (installed) on all my Windows 2016 servers....

* I can add CAB file into WIM, but this enabled .NET3 feature for default installation (big no)
* Once I disable feature -  its being disabled with Payload Removed... 

Thanks
Grobas

_{Tuesday, June 12, 2018 9:03 PM}

Yup, still as-is.

Have you created a support incident?