Chris,

The core Windows Winsock component only supports HTTP communication. HTTPS communication is not supported. Many sites offer both a secure and a non-secure version. If you only have a secure version, then HTTP calls in SetupBuilder will always fail (e.g. with Error 5060 or 505010054 = WinSock Error Code 10054).

We are working on "WUPDATE2.EXE" and "WUCHECK2.EXE" SSL web update clients which are powered by our new (soon coming) HTTPs support in SetupBuilder. This is not a trivial change and requires changes to be made to many of the internal compiler functions. Our SSL support will be backward compatible down to Windows 2000. It supports Windows 2000 - Server 2016.

http://www.lindersoft.com/forums/sho...SL-Server-Help!

Friedrich