Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've searched Google and seen discussions on it, even on their own MS blogs but I'm at a loss.

I've gone into WSUS and chose all of the .NET Framework packages I can find (they were in the "Service Packs" area) and set them to "Install" for a test group.

However, when I look at the reports, all of those packages show as "N/A" for the computers in the test group. But the computers still only have the default .NET 1.1 installed.

So my real question is:

Can I deploy .NET Framework 3.5 through WSUS? If so, how? If not, can you recommend another SIMPLE way to deploy it (I say this because the steps to deploy it using GPO Software installs is a nightmare with tons of prereqs, etc.).



(first, other updates deploy just fine to these computers)

The .NET Framework I have set to install in WSUS is:

KB951847 when I go back in and run the report it shows as Installed. Last week it was showing as N/A. I guess I jumped the gun on the question.

share|improve this question
You don't see .NET 3.5 with SP1 in WSUS? I was sure it was in there... let me check my WSUS server. – Andy May Jun 16 '09 at 14:03
Which KB# did you approve that is saying N/A? 951847? – Andy May Jun 16 '09 at 14:15
See my edits above in my Original post for the answers to your questions. – TheCleaner Jun 16 '09 at 18:44
Oh, and I'd have accepted your comment as the answer but can' if you post the KB article again in the answer I'll accept your answer. – TheCleaner Jun 16 '09 at 18:51
up vote 1 down vote accepted

Check out this blog post (May 7, 2009):

.NET Framework 3.5 Service Pack 1 (SP1) and Family Update package revisions coming soon!

As alternative, you could deploy it using the Active Directory (.NET Framework 3.5 Deployment Guide for Administrators):

This section describes how to use Active Directory to deploy the Windows Installer setup package for a specific component across a network. To deploy components that require file extraction, you must have administrator privileges on the target computers.

share|improve this answer
Would this work for Windows 8/2012 ? – Jeff Apr 25 '14 at 12:41

ok - I have an answer for this problem - not the one I hoped for... but it does work. If you grab the .cab file from the Windows install disc under sources\sxs then run the command:

dism.exe /online /enable-feature /featurename:NetFX3 /source:"sources\sxs"

Windows will install dotNet offline without affecting the WSUS configuration. This would be easy enough to script into the logon script. I've tried it out on Windows 10, so I guess it would work on previous OS versions too.

share|improve this answer

First of all you do not need all .NET framework packages, 3.5 SP1 will do. Try approving some other update and check if it installed. If not, something else is not working as expected. You can also check the file WindowsUpdate.log for errors, sometimes it really helps.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.