i tried the command to enable .net 3.5.
it states again error 87.
I haven't found a solution yet. However, I have some thoughts I figured were worth adding to this somewhat dated discussion (since the issue is still very much alive, and googling hasn't netted me anything useful, I consider it a live issue):
1) Since adding it from Add Windows Features uses Windows Update, which fails, I removed my WSUS configuration and tried again, to no avail.
2) I used my install media (a flash drive I set up with a full SXS directory) for DISM, which has failed on parameters with 87, the problems in the log as such:
C:\WINDOWS\system32>Dism /online /enable-feature /featurename:NetFx3 /All /Sourc
e:G:\sources\sxs /LimitAccess
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
Enabling feature(s)
[===========================66.5%====== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>Dism /enable-feature /featurename:NetFx3 /All /Source:G:\sou
rces\sxs /LimitAccess
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 87
The enable-feature option is unknown.
For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>DISM /Online /FeatureName:NetFx3 /All /LimitAccess /Source:g
:\sources\sxs
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
Error: 87
The featurename option is unknown.
For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
3) Checking the log file referenced shows the following errors:
[2308] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2308] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2308] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2308] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2308] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2308] [0xc142011c] WIMGetMountedImageHandle:(2568)
The log also ends in a page or two of mandarin characters and jibberish, which doesn't seem appropriate.
It seems totally inappropriate that something as commonly used as .NET Framework 3.5 is this much of a hassle to get functioning.
If someone wanted to provide some insight as to what's broke and why Microsoft hasn't fixed it to make such a mundane, almost categorically required step into something easy, I'd be curious to hear it.
My network is not locked down meaningfully. It's a corporate network running 2008 R2 servers, but our GPO is very 'light', being basically drive mappings, printer installs and a logon script I wrote myself for a variety of tasks unrelated to DISM or Windows
Update.