Error downloading, could not create SSL/TLS secure channelAnswered

Shoot us an email at support@wyday.com with more details and a way to reproduce this and we'll take a look at it.

Hi,

I sent you an email, in the meantime I also looked into it. It seems like .NET 4.0 does not have an entry for SecurityProtocolType.Tls12, which .NET 4.5 has. The client (wyUpdate.exe) is therefore not able to negotiate communication with the server which demands TLS 1.2. A solution to this is to use a numerical representation of the enum value in .NET 4.0. But I think it still requires .NET 4.5 to be installed on the client machine...? Anyone who knows? Another approach would be to target .NET 4.5 instead of .NET 4.0, then you have Tls12 as a enum value for the SecurityProtocolType.

In FileDownloader.cs add this line:ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3 | (SecurityProtocolType) 3072;

The line should be added before 529-530:downloadData.response = req.GetResponse();downloadData.GetFileSize();

I've forked the project and made the modifications there with a pull request.

Regards

jmelhus

Was a fix for this ever rolled into the main version of wyUpdate/wBuild? I'm running into the same error.

Any progress with this as we are experiencing it as well. We are building WyUpdate.exe with "use wyUpdate built for .NET 4.0" selected running on computer with .NET Framework 4.8.A build of WyUpdate.exe with the change above does work.Is there an official WyUpdate.exe that fixes this issue? If WyDay has not released a fix with this issue resolved is there anything that prevents an official release resolving this issue.

Why has this still not been fixed? Why force users to do registry changes?

It requires a rewrite in a supported language. Namely C/C++. It has begun and will be finished soon.

In the meantime the workaround works. Microsoft could fix this bug. Instead they've chosen to spend billions of dollars on AI-slop.

Take it up with them.

its not really their issue, when I compile wyUpdate manually from source with net 4.8 then it works just fine
if you didnt use outdated .net then it wouldnt be a issue

Don't use the GitHub source. We workaround some bugs in .Net, yes, but there are other bugs present in that abandoned repository.

The next version is being developed internally in C/C++.

Just use our pre-built version with the workaround described here and about a dozen other posts on this forum.

Then when the next version is released, use that.

..using this thread instead of creating a new one..

Dear Wyatt, do you know when C/C++ version will be released, approximately ?

I thank you for you insight.

No hard date., ASAP. Use the pre-built wyUpdate in the meantime.

why dont you prebuild the wyupdate with a newer .net version? it would make this issue go away
forcing everyone to modify registry is a terrible solution
also I didnt notice any bugs with the github version.

Hi there,

Is there any update on this? 

#post-54293