Now available .NET 4.7.1

Topic

New Reply

Yesterday Microsoft released .NET 4.7.1, an in-place update for  .NET 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, and 4.7 Details on Martin Brinkmann’s G
[See the full post at: Now available .NET 4.7.1]

4 users thanked author for this post.

walker, JDeC, AJNorth, MrBrian

Reply | Quote

Replies

From https://blogs.msdn.microsoft.com/dotnet/2017/10/17/announcing-the-net-framework-4-7-1/: “.NET Framework 4.7.1 will be available on Windows Update in the near future.”

4 users thanked author for this post.

walker, JDeC, woody, AJNorth

Reply | Quote

Is this the reason this month’s .NET Framework Rollup was an optional update?

Reply | Quote

No. The reason is there were no new security-related .NET Framework fixes this month.

3 users thanked author for this post.

MrToad28, walker, JDeC

Reply | Quote

I see. Thanks for clarifying.

Reply | Quote

From the [ms-defcon-1-patches-failing-at-a-phenomenal-rate ] Thread /#post-138759

PKC, Always appreciate your guidance – BUT – with nothing but time and multi-Macrium Images I just Installed 4.7.1 with no issues yet via Browsing & Office use.

Being Win7-64 does limit the magnitude of this experience, but it’s a start for other W7 users.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

1 user thanked author for this post.

SueW

Reply | Quote

For the new .NET 4.7.1, are there any prerequisites for Win 7 SP1, Win Server 2012 & Win Server 2008 R2 SP1 users upgrading .NET from v3.5.x or installing over v4.0 – v4.6.x ?

Background: The aforementioned OS users need to install d3dcompiler_47.dll  (KB 4019990) first before installing .NET 4.7. I’m assuming such users installing .NET 4.7.1 over .NET 4.7 will have no problems of the installation being blocked, etc.

 

.NET 4.7.1: Known issues so far seem to affect mainly touchscreen users of .NET-dependent apps …

As of 18 Oct 2017 UTC:

• WPF Touch Stops Working After Rapid/Prolonged Use Of Popups
• WPF Touch generates a NullReferenceException in WispLogic.ProcessInputReport
• WPF Touch/Stylus Generates AccessViolations and Heap Corruption in GetPenEventMultiple
• WPF InvalidCastException when displaying a checked MenuItem

 

Reply | Quote

I am a little confused about what is going on with .NET 4.7 with comments that the monthly quality and security rollups were installing version 4.7 automatically. I have been looking at an optional update for >NET 4.7 for W8.1 x64 system since July which I have not installed as of yet. I have installed the cumulative security/quality updates through September. Does that mean I have already installed .NET 4.7 on a stealth install. The optional update is still on offer. I generally do not upgrade the .NET versions until I have an app that requires the newer version.

Reply | Quote

There are no stealth installations that I am aware of.

1 user thanked author for this post.

walker

Reply | Quote

I bit the bullet and installed 4.7 last month and [knock on head] haven’t had any issues with any of the apps I use that are .NET based. (Small anecdotal use here though, nothing major or critical.) If it ate itself, there’s always backups to restore from. 😀

Reply | Quote

In a recent blog post about paint.net 4.0.20 and .NET 4.7 developer Rick Brewster notes:

Just a quick heads up: the next update, version 4.0.20, will start using and requiring the .NET Framework 4.7 (previously, .NET 4.6 was required). If you’re using a supported version of Windows then the Paint.NET updater will automatically install .NET 4.7.1 if you don’t yet have .NET 4.7 or .NET 4.7.1 installed already.

Since I currently have .NET 4.6.1 installed, I’m just going sit tight for now and let paint.net take care of this. Rick says 4.0.20 will be available, “within the next few weeks.”

Reply | Quote