Windows 7 is outdated and does not support TLS 1.1/1.2 by default. You have to install and enable it manually.

Make sure that the update kb3140245 is installed on your system.

Afterwards use this easy fix tool which will add the required registry keys.

Since I am not sure if the easy fix tool covers all keys, you can also manually add these keys by copying the following to a text file, rename it to whatever.reg, open it and confirm to add the data to your registry.


Restart the PC and in theory it should work now.

Further general information about this topic can be found here.

The obvious question is "why are you still running W7?"


I mean I can understand why many people (inlcuding myself on my main machine) are not running W11 yet but W10 is mature enough by now surely ?

Are there any specific programs you use that will only run under W7 ?

Quoted from "Stark43"

Unfortunately it did not help.

We just tested that here with a fresh Windows 7 installation and it works. At first we also got no connection like you and after installing all Windows updates and applying the Fix and registry entry it was working.

It could be still possible that you have some other kind of network issue.

I assume you use Windows 7 SP2 with all available updates (also the optional ones)?

The server has the IP 46.4.72.36. The connection requires at least TLS version 1.2.

I am not sure about your name server question because that depends on your local network settings. You could maybe try a different public name server (Google, Cloudflare, OpenDNS, Quad9 etc.).

After starting the setup you could run the command "netstat -ano | findstr 46.4.72.36" in the console to check if any open connection exists.

You mentioned a VPN: is your entire traffic running through this? If so, are you sure that this connection supports TLS 1.2 too?

Please check the Windows event viewer if there are any error reports from the aquasuite setup or the old aquasuite when you try to update it.

Please navigate to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL and change the key EventLogging from 1 to 7. This should allow a complete logging of all schannel events. Your system seems not to be able to make a proper handshake with our server for whatever reason. Code 70 according to Microsoft means "The protocol version the client attempted to negotiate is recognized, but not supported. For example, old protocol versions might be avoided for security reasons. This message is always fatal." And that is also the reason why our server cuts the connection.

And since you are already there, could you please export the whole SCHANNEL key and share it.

Restart the system afterwards and play a bit around to check if the event viewer provides more information now.

- - - - -

One thing that just came into my mind. Make sure that you have the latest update of the .NET framework on your system since the aquasuite and its setup are .NET applications.

- - - - -

When you open the PowerShell and enter the command "[Net.ServicePointManager]::SecurityProtocol" - what is the result?

- - - - -

And my last idea for today. Copy the following lines to create a .reg file and apply it to your system (restart afterwards)


This will allow TLS 1.2 for .NET 4.5 and higher. This should also affect the result of the PowerShell command above.

Hello,

I am sorry to resurrect this, but I have the exact same problem.
Yes, I also have a modern system, but there is a Windows 7 system with "critical" software that still needs to be maintained for now...
I have tried ALL suggestions and nothing worked.

What I have found though is that the aquacomputer server (backend2.aquacomputer.de) only supports 3 cipher suites (see attached image).
And it looks like none of them are supported in Windows 7 and there is no way to add them.

I have tried going through a proxy, however it looks like the setup (.NET application) ignores any settings (system wide proxy by netsh, .NET wide proxy by machine/web.config).

QUESTION:
Would it be possible to add a few more cipher suites to the server so older clients can connect?
Specifically, these are the suites installed on my Windows 7 system:

TLS 1.2 SHA256 and SHA384 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_NULL_SHA256

TLS 1.2 ECC GCM cipher suites:

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521


Thank you for your consideration!

Woohoo! Looks like the server has been updated, the installer is showing some updates to download!

Thank you very much, amazing service!