One of our MDs recently reported issues launching CPS (12.0.11). This MD reported that a different software program was also throwing errors about .NET 4.7. By removing .NET 4.7 and reinstalling .NET 4.5, we noticed that the issues with CPS were also resolved. GE Support later confirmed that .NET 4.7 is not compatible with CPS 12.
We noticed that Windows Update on Windows 7 is listing .NET 4.7 as an Important update. This could mean that Windows Update will automatically install .NET 4.7 on the next Patch Tuesday (July 11th). To combat this, we are blocking Windows Update from installing .NET 4.7 using a registry change that we are pushing out via Group Policy.
I am sending this out as a friendly head's up to fellow CPS users to avoid potential issues. It is very possible that in your environment, either of the following may happen: (1) .NET 4.7 does not get installed via Windows Update; (2) .NET 4.7 has no negative impact on CPS.
At this point we have not tested .NET 4.7 with CPS 12.0.x yet, but given that 4.7 has issues with Exchange 2013/2016, and other applications this wouldn't surprise me.
To my knowledge Microsoft hasn't released .NET 4.7 via WSUS yet, but as always my recommendation is to use the enterprise tools that Microsoft provides and validate updates in a test environment prior to releasing them to production.
I am going to test on 12.2.x and see if the newest .NET works with 12.2.
Thanks for the heads up. We use thin clients for our CPS. Does this mean the servers cannot have dot net 4.7 installed or the clients or both?
I'm not sure. Looking at Configuring CPS, I don't see any requirements for .NET on any of the servers. Configuring CPS does tell us that .NET 4.5 is required on client workstations.
We ran into issues where .NET 4.7 was installed on a client, so that is all I'm able to speak to.