.NET Framework 4.7 is out

[cgthamm]

Microsoft has released .NET Framework 4.7.

 

Unforunately, it has caused stability problems for two of my clients on Windows 8.1 PCs. In one case, I had to re-format for normalcy to prevail.

 

At this point, I am able to recommend only .NET Framework versions up to 4.6.1 (along with its hotfixes, updates, and update rollups) for machines running Windows 8.1.

 

 

I suspect the same will turn out to be true for Windows 7 PCs.

Edited July 24, 2017 by cgthamm

[GrofLuigi]

No problems here on Win7 x64. In fact, some programs start noeticeably faster. I had COMPLUS_useLegacyJit set to 1, COMPLUS_JitMinOpts 1, useLegacyJit 1, all from before, and the installation added UseRyuJIT=1 and it left it like that.

 

As discussed here.

 

I'm not touching anything as long as it works.

 

Oh, and I'm using .Net 4.7 slim from repacks.net.

 

 

[cgthamm]

Microsoft has now documented a bug that occurs if you install .NET Framework 4.7 after installing the .NET Framework May 2017 Preview of Quality Rollup. The documentation also provides guidance on how to proceed, depending on your situation.

 

You can full the full article here:

 

.NET Framework May 2017 Preview of Quality Rollup

 

Bottom line:

 

If you have installed the .NET Framework May 2017 Preview of Quality Rollup but not .NET Framework 4.7, Microsoft recommends you uninstall the .NET Framework May 2017 Preview of Quality Rollup.

 

If you have installed the .NET Framework May 2017 Preview of Quality Rollup and .NET Framework 4.7, Microsoft recommends you uninstall and then re-install .NET Framework 4.7. Doing so will fix the underlying issue.

[cgthamm]

If you are using Windows 8.1 with .NET Framework 4.6 or 4.6.1, and you install the July, 2017 Preview of Quality Rollup for .NET Framework, you will end up with component store corruption.

 

This corruption cannot be repaired by uninstalling the July, 2017 Preview of Quality Update and running dism /online /cleanup-image /restorehealth from an elevated Command Prompt (which was -- up until now -- the reliable way to roll back a .NET Framework version on Windows 8.1).

 

I had to restore a recently-made System Image backup to return to sanity.

 

That's now "Strike Two," when it comes to Previews of Quality Updates for .NET Framework (i.e. May, 2017 and July, 2017).

 

 

 

[cgthamm]

I found a way to get .NET Framework 4.7 working. Here's the step-by-step method:

 

1. Download the following updates from Microsoft Update Catalog, appropriate for your CPU architecture:

 

For Windows 7 / Server 2008 R2:

 

KB4032113

KB4035510

 

For Windows 8 / Server 2012:

 

KB4032114

KB4035508

 

For Windows 8.1 / Server 2012 R2:

 

KB4032115

KB4035509

 

2. Install KB4019990, the Update for the d3dcompiler_47.dll component on Windows Server 2012, Windows 7, and Windows Server 2008 R2

 

For Windows 7 / Server 2008 R2, it's in the KB4032113 folder you downloaded in step 1.

For Windows 8 / Server 2012, it's in the KB4032114 folder you downloaded in step 1.

 

NOTE: KB4019990 is not needed for Windows 8.1 / Server 2012 R2.

 

3. Download and install .NET Framework 4.7 and any language packs you may need.

 

4. Depending on your version of Windows, install the following updates:

 

For Windows 7 / Server 2008 R2:

Install KB4014596 and KB4024848 from the KB4032113 folder you downloaded in step 1.

Then install KB4035510.

 

For Windows 8 / Server 2012:

Install KB4014594 and KB4024846 from the KB4032114 folder you downloaded in step 1.

Then install KB4035508.

 

For Windows 8.1 / Server 2012 R2:

Install KB4014598 and KB4024847 from the KB4032115 folder you downloaded in step 1.

Then install KB4035509.

 

That's it! You now have a working installation of .NET Framework 4.7 with no component store corruption.

[parkd1]

.NET Framework 4.7.1 is out