Officially, Microsoft only supports Windows Server 2016 and higher for .NET7, which this program builds and depends on. If you’re stuck on an older version of Windows (sorry), consider running the latest version of win-acme on a different machine and transfering the certificates over to the older machine using an installation script.
If you absolutely must run win-acme on the older machine, you can use an older release of the software and accept all known bugs and limitations, because they are not supported anymore.
api-ms-win-crt-runtime-l1-1-0.dll you may need KB2999226.
hostfxr.dll you may need KB2533623.
Failure processing application bundle., perhaps this thread might provide a solution.
Microsoft.Windows.Apprep.ChxApp_cw5n1h2txyewy:App.AppXc99k5qnnsvxj5szemm7fp3g7y08we5vm.mca appears in the Event Viewer this thread might provide a solution.
Server Name Indication (SNI) is supported from IIS 8.0 (Windows Server 2012) and above. This feature allows you to have multiple HTTPS certificates on the same IP address. Without it, you can only configure a single certificate per IP address.
If you want to have SSL for multiple sites with multiple domains with IIS 7.5 or lower all bound to the same IP address your choices are:
When win-acme creates the binding for a new certificate, it will bind the wildcard (*)
IP address by default. In other words, incoming connections on all network interfaces
will handeled using the certificate. You can customize this with the
switch from the command line, or manually after win-acme created the binding. On renewal,
the program will preserve whatever setting is configured in IIS.
Wildcard bindings are only supported on IIS 10 (Windows Server 2016+). Wildcard certificates can be created with older versions of IIS but their bindings will have to be configured manually.
Updating FTPS binding is only supported for IIS 7.5 (Windows 2008 R2) and above.