One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. For more information, see WINHTTP_STATUS_CALLBACK.[/code]
When I switched to URLConnection a few weeks ago, I found I was easier to add the two registry keys mentioned in the MS support KB to my Innosetup script instead of having Windows 7 users change their own system. That seems to have done the trick.
The two registry keys only works IF the kb3140245 is installed AND even then, some windows 7 may need more registry changes, the “Easy fix” tool makes all the changes . For a Innosetup, you can run those two in silent mode.
Me too, maybe they tested only in a full updated windows 7Sp1
Thanks! To be extra safe I’ll install the “Easy Fix” tool. You mention you can run “those two in silent mode”. Are there two “Easy Fix” tools? I only see one in that KB and just want to make sure I’m not missing something.
By them, I meant the KB update installer and the “Easy fix” tool.
Great example, but, you are also editing the registry manually. Today I deploy the new URLConnection version of my app on many Windows 7 Machine. In most of them worked As Is, on some, worked editing the registry, but on 2, didn’t work until runing the “easy fix”.