As Enthousiast pointed out this key should be used with caution as it could break something. IMO: For private use it's ok and can be deleted/changed quickly in case of failure but in enterprise environments it's better to not use it at all.
It's just as simple to enable dotnet35 as modifying the registry and have the possibility to have problems with it. ??????? Dotnet35 is native on win 7 SP1.
only 2 things need .net2, dont need 3. some stuff i will use need 4 upwards. so im gonna use ricktendos .net 46 repack. so i can strip all .nets from 7 iso, then install his repack only when needed.
Using DISM in a script, to integrate NET 4.6.2 and the Windows 10 updates (KB3200970 and KB3202790). However, the integration hangs at 44.9% in the KB3200970 update. Follow the command I'm using. AT is the folder that contains the updates. Code: Dism /Image:%DIR%MOUNT /Add-Package /PackagePath:%DIR%AT_%PLA%
The servicing stack (KB3199986) has to be integrated before all other updates, why are you integrating it online after install?
Really? When i do, it both packages adds ~800 new folders in winsxs. So I always was thinking, there are only 4.6.1.