.NET Framework 3.5 Standalone Installer for Windows 10

Hello
abbodi1406;

I am new on this forum.
I have the .net Framework 3.5 SP1 downloaded from here: microsoft.com/net/download/all

Your version is over 4 times smaller in size though.
So, why would users prefer for this version instead of the one at the Microsoft's website?

What are the advantages of this version of .net Framework 3.5 SP1?

 

I thought no version of the .net framework such as 1.0, 1.1, 2.0 3.0 and up to 3.5 was in Win10.

So, you are saying it is there, and that this file from the Microsoft website is not suitable for Win10 users.

It doesn't make much sense to me as to why it was removed and disabled. Can you elaborate more please?

Thanks.

 

Keep in mind that having net3.5 added back has been linked with fringe occurrences of components (dcom?) getting mangled, that can lead to start menu / search / settings / uwp in general to misbehave.
Only do it if you absolutely need it - and even then, it's better to search for alternatives or urge the third-party developers to recompile their s**t.

 

Hi, please update it when possible

 

Hi. What exactly changed?
Please inform us?

Thanks.

 

Is this tool any different (in the terms of possible errors) from if i manually install .net 3.5 with dism using mounted iso?

 

Yeah. I'd like to know more about that too.
In what way is this one beneficial over the other installers.

 

1. Mount a Windows 10 ISO
2. Command Prompt (Admin): DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~ /Source:G:\sources\sxs
where G is the mount letter for the ISO in step 1.

 

or using DVD or ISO dism /online /add-package /packagepath:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab

 

Thanks a lot, I always had problem installing it, even on a clean install, this installer seems to work, even with my tweaks applies, that is saying something.

If you are a gamer, you need it, if you install 3rd party software, you most likely need it. Basically it is as essential as all those useless VisualC++, if you are missing a single one, you are done for.

 

Thanks a ton! Great work as always.

 

You need to login to view this posts content.

 

I'm thinking about changing my method from integrating .net 3.5 in the image to post-deployment.
In the past it proved to be problematic doing a resetbase after integrating .net 3.5 because of pending operations.

Seeing Abbodi's reply above, is it possible to enable .net 3.5 after deployment of an image with updates pre-integrated?

And if so, is the .net 3.5 package for build 17763 up to date or will WU offer patches already?
I'd prefer to leave it out all together, but as TairikuOkami noted, changes are that some third party software still uses it.

It's kind of a trade-off, integrate it and lose resetbase on the install wim, or do it post-deployment and have WU downloading patches.

Cheers.

 

When you use @abbodi1406 his W10UI script it gives you the option to /resetbase and pre-enable dotnetfx3, but better to do a /cleanup-image anyway, /resetbase breaks the "resetpc" option.
/cleanup image will compress the superseded files instead of removing them, almost the same gain.