I'm having the same issue as Dave. I've been working with v16 since February and have used the Updater software since then. It just recently stopped working. I've tried everything mentioned here - Firewalls, going to the manual URL and seeing that I can connect to the server, installing TIA Administrator, punching in the URL as a "corporate" server. It still doesn't connect. 

The closest I've gotten is this manual method. It works but it is cumbersome. It would be great if the Siemens update software didn't constantly have issues:

"For myself I have written my own updater with notification via E-Mail.
All updates together: 130 GiB

You can request this file: https://update.industry.siemens.com/asu/files/tiaportal/UpdatesSummaryCatalog.xml

There you'll see all updates.

mainurl = https://update.industry.siemens.com/asu/files/tiaportal/

https://update.industry.siemens.com/asu/files/tiaportal/simatic/tiaportal/ASU/2.2.0.0/SIMATIC_Automation_Software_Updater_V2_2.exe

https://update.industry.siemens.com/asu/files/tiaportal/simatic/tiaportal/ASU/2.2.0.0/SIMATIC_Automation_Software_Updater_V2_2.txt

You can also check the file with md5sum or sha256sum.

Maybe it solves your problem. I'm not sure if it needs a previous installed version of asu."

I am using a Windows 7 VM and it is up-to-date as of today at 9:30am EDT.

I also tried the .NET "fix" that was mentioned in the forum, but it also did not work.

Based on comments from both 0_Einstein and D.House I have found a working solution that is easy to apply.

I instinctively knew that it was likely a secure protocol issue, as these happen from time to time, but since Win7 is no longer fully supported, it is trickier to keep it up to date. 0_Einstein indicated that without an EA Win7 wasn't up to date and D.House indicated it was TLS 1.1/1.2 that was at the root of the issue.

We have 2 M4 PGPCs running Win7 Ultimate and while we are currently getting ready to transition to Win10 M6s, we need to keep these up to date for now.

So here is what worked for me:

WindowsEasyFix51044.msi followed by KB3140245, which was an optional update for Win7. The EasyFix code simply adds a subkey required for TLS 1.1/1.2 so that KB3140245 can work correctly.

It took 5 minutes, a restart, and then they were connecting correctly again. I hope this can be of help to others encountering the same issue with Win7 devices.

--Dave Smith

LogicSolut

Based on comments from both 0_Einstein and D.House I have found a working solution that is easy to apply.

I instinctively knew that it was likely a secure protocol issue, as these happen from time to time, but since Win7 is no longer fully supported, it is trickier to keep it up to date. 0_Einstein indicated that without an EA Win7 wasn't up to date and D.House indicated it was TLS 1.1/1.2 that was at the root of the issue.

We have 2 M4 PGPCs running Win7 Ultimate and while we are currently getting ready to transition to Win10 M6s, we need to keep these up to date for now.

So here is what worked for me:

WindowsEasyFix51044.msi followed by KB3140245, which was an optional update for Win7. The EasyFix code simply adds a subkey required for TLS 1.1/1.2 so that KB3140245 can work correctly.

It took 5 minutes, a restart, and then they were connecting correctly again. I hope this can be of help to others encountering the same issue with Win7 devices.

--Dave Smith

 Dude, Thank You so much for the info.

It took a while to locate the EasyFix.msi but once located and installed, everything works just fine!

Cheers!

LogicSolut

Based on comments from both 0_Einstein and D.House I have found a working solution that is easy to apply.

I instinctively knew that it was likely a secure protocol issue, as these happen from time to time, but since Win7 is no longer fully supported, it is trickier to keep it up to date. 0_Einstein indicated that without an EA Win7 wasn't up to date and D.House indicated it was TLS 1.1/1.2 that was at the root of the issue.

We have 2 M4 PGPCs running Win7 Ultimate and while we are currently getting ready to transition to Win10 M6s, we need to keep these up to date for now.

So here is what worked for me:

WindowsEasyFix51044.msi followed by KB3140245, which was an optional update for Win7. The EasyFix code simply adds a subkey required for TLS 1.1/1.2 so that KB3140245 can work correctly.

It took 5 minutes, a restart, and then they were connecting correctly again. I hope this can be of help to others encountering the same issue with Win7 devices.

--Dave Smith

 Dave, thank you for sharing! Your proposal fixed the TIA Updater issue. Unfortunately I could only install WindowsEasyFix51044.msi . When trying to install KB3140245 I received the following message : "The update is not applicable to your computer". 

Installing WindowsEasyFix51044.msi fixed the issue, in my case.