Datasource verification problems after Windows updates

Question

Yesterday windows updates were installed on my laptop, and afterwards many features of ColdFusion were out of configuration.

I am using ColdFusion 2016 and SQL Server 2016 RC.

I fixed a number of issues (see below) but still get the message

Connection verification failed for data source: MT_EL java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: 8500:1433. Reason: Network is unreachable: connect The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: 8500:1433. Reason: Network is unreachable: connect.

The DSNs had been verifying for at least a year before the problems occurred.

So far I have done the following:

1. Both SQL Server and CF Server had to be started again. SQL Server was not a problem but the CF Server would not start. I went to the jvm.config file and reduced the -xms setting. This did not solve anything, so I looked at the logs. From the logs it was apparent that the neo-security.xml file was corrupted, and upon checking I saw that neo-security.xml was now empty. neo-datasource, neo-drivers and one or two other files were also empty. The back-ups of these files were also empty, but I found some old versions in another place, and copied them over. Now I was able to start the CF Server and get into the CF Administrator, but had to set up user names/passwords and also DSNs again.

2. SQL Server Configuration Manager had been moved to a different folder, but I found it and soon saw an error message saying that SQL Server Configuration Manager could not connect to the wmi provider. I fixed this by opening a command prompt in administrator mode and typingmofcomp "%programfiles(x86)%\Microsoft SQL Server\13\Shared\sqlmgmproviderxpsp2up.mof".

3. Now I could get into SQL Server Configuration Manager, but for some reason it is listed twice, The malfunctioning one still says I cannot connect to the wmi provider, but expanding the functioning one, I found that TCP/IP is enabled and the default port is 1433.

4. I checked the firewall and could not see any issues there.

5. SQL permissions + log in/password credentials are the same as before, when there were no DSN verification problems.

6. I have tried ports 8501 and 8502, but the above error persists.

7. I have checked the SQL Server logs. It is apparent that a number of errors occurred yesterday and certain features were disabled. However it is evident that these issues have now been resolved, and the most recent messages are of informational type and state that no user action is necessary.

Anyone any ideas? Thank you in advance for any comments/assistance.