Beruflich Dokumente
Kultur Dokumente
1, Windows 8, Windows
Server 2012 R2, and Windows Server 2012
Prerequisites for .NET Framework 3.5 in Windows 8 and Windows Server 2012
The following prerequisites are required to enable the .NET Framework 3.5 in Windows 8 and
Windows Server 2012:
Note If the computer that you want to update is behind a firewall or uses a proxy server,
see How the Windows Update client determines which proxy server to use to connect to
the Windows Update website.
The current user must be a member of the local Administrators group to add or remove
Windows features.
How to enable the .NET Framework 3.5 by using Control Panel in Windows 8.1 and
Windows 8
You can use Control Panel in Windows 8.1 or Windows 8 to enable the .NET Framework 3.5.
To enable the .NET Framework 3.5, follow these steps:
1. On the Start Screen type turn on windows features, click Settings, and then click Turn
Windows features on or off. (The screen shot for this step follows.)
2. Under Turn Windows features on or off, click .Net Framework 3.5 (includes .NET
2.0 and 3.0).
Note The wizard will search for required files and then prompt you to download the files
from Windows Update.
3. Click Download files from Windows Update.
4. Click Finish. (The screen shot for this step follows.)
How to enable the .NET Framework 3.5 by using the Add Roles and Features Wizard in
Windows Server 2012 R2 and Windows Server 2012
To enable the .NET Framework 3.5 in Windows Server 2012 or Windows Server 2012 R2,
follow these steps:
1. In Server Manager, click Manage, and then click Add Roles and Features. (The screen
shot for this step follows.)
Note In the screen shot, notice the statement that the .NET Framework 3.5 is not part of a
typical installation. However, the installation files are available in a side-by-side store
folder. Additionally, you do not have to mount or point to a specific WIM source.
Note If you are using Server Manager in Windows Server 2012 to add a role or feature to a
remote server, the computer account on the remote server requires access to the alternate source
file path because the deployment operation runs in the SYSTEM context on the target server.