I needed to install .NET 4.7.1 to allow updating Exchange 2013 to CU 21.
This is the installer I downloaded and tried to install: https://www.microsoft.com/en-us/download/details.aspx?id=56116
But the installation never ends. It remains stuck without progressing in the “Installation progress” bar. Tested both with offline and online installation:
To install .NET Framework 4.7.1 download the msu package from the following link:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4033369
It seems that there is some kind of problem with the other format, but the msu worked correctly for me.
Update – For Windows Server 2016 (Thanks to Ryan comment):
If running into the same issue when installing CU10 for Exchange 2016 the msu of .NET 4.7.1 for Windows Server 2016 here it is: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4033393
Thanks so much for posting this. Ran into the same issue when installing CU10 for Exchange 2016. For anyone looking for the msu of .NET 4.7.1 for Windows Server 2016 here it is: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4033393
Thanks Ryan for your contribution
Thank you! worked for me for 4.7.2
Same here with CU10 for Exchange 2016 on Windows Server 2016. Link from Ryan worked for me.
This happened to me too. No progress showing. However, I looked at the process manager. The install was using cpu and memory and the number was going up and down. Also, the event viewer was showing events in the Application section, so I just let it sit. It took over an hour but it did finish.
That’s exactly I also noticed.
I also ran into this, but as others, I waited, as the process manager showed aorund 25% cpu load on the .net setup installer.
Waited 25-30mins, and after that, it was installed 😉
But I admit, it just stands there as stalled, but it does actually process, as you can see on process manager 😉
Ended up being a background silent “no restart” dism install that specifically required a restart. Run the offline installer and when it gets stuck, stop the install. There will eventually be a “failed / end” screen with a log link. In there, search for “error”. Towards the end, there will be a dism /silent /norestart /blahblah – remove the /silent /norestart options and run from a administrator command prompt.