Oes Without Installer V 1.1

Hi CharlieBrownMSDN,Thank you for posting in MSDN forum.Windows Server 2012 R2 (all editions) includes the.NET Framework 4.5.1 as an OS component, and it is installed by default except in the Server Core configuration. It also includes the.NET Framework 3.5 SP1 as an OS componentthat is not installed by default.

The.NET Framework 3.5 SP1 can be added or removed via the Server Manager.Refer to:So you need to enable it, you have two ways to enable it:1. Go to Control Panel - Programs - Turn Windows features on or off, click the.NET 3.5, After this step, it will download the entire package from internet and install the.NET Framework 3.5 feature.2. Enable it offline:a. Insert Windows DVD or mount ISO image. The source of this feature can be found in folder E:sourcessxs.

(In this case E: the user’s drive letter on which the user has loaded Windows Media.)b. Open CMD.EXE with Administrative Privileges.c.Run the following command Dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:E:sourcessxs /LimitAccess, and hit Enter.For more detail information, please refer to:Best Regards,Jiayi LiWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey. Hi CharlieBrownMSDN,Thank you for posting in MSDN forum.Windows Server 2012 R2 (all editions) includes the.NET Framework 4.5.1 as an OS component, and it is installed by default except in the Server Core configuration. It also includes the.NET Framework 3.5 SP1 as an OS componentthat is not installed by default. The.NET Framework 3.5 SP1 can be added or removed via the Server Manager.Refer to:So you need to enable it, you have two ways to enable it:1. Go to Control Panel - Programs - Turn Windows features on or off, click the.NET 3.5, After this step, it will download the entire package from internet and install the.NET Framework 3.5 feature.2.

Enable it offline:a. Insert Windows DVD or mount ISO image.

Oes Without Installer V 1.1 Free

The source of this feature can be found in folder E:sourcessxs. (In this case E: the user’s drive letter on which the user has loaded Windows Media.)b. Open CMD.EXE with Administrative Privileges.c.Run the following command Dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:E:sourcessxs /LimitAccess, and hit Enter.For more detail information, please refer to:Best Regards,Jiayi LiWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey.

Oes Without Installer V 1.1 Windows 7

Hi Charlie, Install-WindowsFeature -Name Net-Framework-Core -source C:DownloadssourcesxsBetter you might be create a new folder in C drive as sourcessxs. In sxs folder paste the.net framework setup file. Dont forget to share the sources folder to everyone.and the location be like this, C:sourcessxs. When you try to access location via Run or explore mean, it has to been open the setup file location.either you can try to install using the powerShell command prompt'Install-WindowsFeature -Name Net-Framework-Core -source C:sourcessxsor please refer the below linkhope that will be helpful to you.Regards,Arun. It's more like a workaround than an answer, but I had exactly same issue with Windows 8.1. I was working on offline image, but that should work for you as well.Process: I have installed 'source' machine from the same.iso image (virtual should do). Added the required feature on the new machine (required internet access in my case).

Then copied contents modified on the day from SXS folder to a USB. Thatseemed to be good enough source.Additional notes:1. Some updates block installation of.NET.2.

Not sure if this workaround will work if your 'source' machine is installed from a different media. Brilliant, thank you for your enormous perseverance in finding the proper answer to your (and my) question, despite the only partially relevant answers here (maybe I should call them 'clues').I used the DISM command together with the SXS files which you found, which I was unable to track down locally today during a problem session. Like you, I found that the so-called 'complete install' EXE from Microsoft still attempted to log on to MicrosoftUpdate servers, which I don't happen to have available in my toolbox today.Best,CB.