0
1
I'm trying to enable the NetFx3 feature on Windows 10, this fails through 'Turn Windows features on or off'. And also fails through DISM. I tried the following commands:
dism /online /enable-feature /featurename:NetFx3 /All dism /online /enable-feature /featurename:NetFx3 /All /LimitAccess dism /online /enable-feature /featurename:NetFx3 /All /source:F:\sources\sxs dism /online /enable-feature /featurename:NetFx3 /All /source:F:\sources\sxs /LimitAccess
All with the same output at the command line:
Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 Enabling feature(s) [==========================100.0%==========================] Error: 0x800f0922 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
The DISM log can be found here.
I also already changed the Group policy to get optional component installation and repair from Windows Update directly instead of WSUS, because we use a WSUS server in our domain.
"I also already changed the Group policy to get optional component installation and repair from Windows Update directly instead of WSUS, because we use a WSUS server in our domain." I've dealt with this one as well last week. My experience has shown that this policy doesn't (properly) apply to Windows 10. Using gpedit.msc on the local machine and setting it in the Local Policies worked as expected, .Net now installs. I'm thinking it's because I haven't upgraded the AD GP to support Win 10 yet, but I've done no testing/investigating on that (yet). – Ƭᴇcʜιᴇ007 – 2015-08-19T15:35:43.773
I actually changed it on my local machine as you describe. Unfortunately it still did not work. Just to be sure, I now tried it using the built-in local Administrator account (instead of using my domain user, that is also locally an administrator), but that also gives the same error code. – Jorre Meijrink – 2015-08-20T06:46:10.057