You know, patch.exe has given me hell since I started using it on Vista and beyond. It requires admin and I just don't run admin much when prepping source or building even.
Clicking OK on the UAC warning also doesn't work so this has been a thorn in my side for some time.

Administrator Edit: Removed link to a website not on topic.

Sorry to bother you: The index.html file in download httpd-2.4.43-o111g-x64-vc15.zip has two minor errors that are flagged by the 4.01 syntax checker:
Line 60: <br/> should read <br>
Line 64:  </html  should read </html>
I appreciate your hard work in keeping Apache Haus distributions great quality.

That is really weird. I will try it out on a Windows 2016 server, and see if there should be some sort of difference to windows 10.

Well, it's not a problem in APR 1.7 like the problem with that apr & mod_ext_filter (which works with apr 1.6).
I built 2.4.43 with apr 1.6.5 and got the same error at startup that you do.

I decided to try Apache 2.2 (apr 1.5), while I do not get that error (unless I point to a rotatelogs.exe that doesn't exist).
However, I get no 404, 403 or 500 errors, it doesn't even create a log file at startup as it is documented with -f.

Adding a CustomLog line to check it, it keeps spawning a new process over and over and over but the processes do not stick around. So I think it just simply doesn't work on Windows, or maybe just Windoze 10 which I was testing with.

I might just stop building/including it. If someone actually uses it I'd expect some disturbance in the force which would eventually lead to someone asking why it's no longer included which then I ask questions of how the heck did they get it working.

Assuming the path used is correct and we are being shown a sanitized one:

I wonder if this problem is the same as with mod_ext_filter (both create an external process) in that it fails with APR 1.7.0 or if you should be using all double backslashes all the way through that ErrorLog string of yours since Windows doesn't understand forward slashes as a path separator. I have only used mod_log_rotate and never logrotate.exe but it seems to me I remember seeing an example that used \\ on windows decades ago. So try;

ErrorLog "|c:\\path\\to\\Apache\\Apache24\\bin\\rotatelogs.exe -l C:\\path\\to\\logs\\error.%Y-%m-%d-%H-%M-%S.log 86400"

Let me know if that works. If not I will compile httpd-2.4.43-o111f-x86-vc15 that instead uses APR 1.6.5 that you can test and if that works, I will go back to apr 1.6.5 till the problem with 1.7.0 gets fixed.

Correct - the path was sanatized :-)

I have now tried several things - all of them directly in the httpd.conf, no variables, just plain text hardcoded:
1. Double backslashes for both rotatelogs.exe and the log file path
2. Double backslashes for rotatelogs.exe and single backslashes for the log file path
3. Single backslashes for rotatelogs.exe and double backslashse for the log file path
4. Single backslashes for both rotatelogs.exe and the log file path
5. With and without .%Y-%m-%d-%H-%M-%S in the log filename

All of them write the same two errors in the event log.
1:
The Apache service named  reported the following error:
>>> (OS 2)The specified file was not found.  : AH00089: Couldn't start ErrorLog process 'c:\\path\\to\\the\\Apache24\\bin\\rotatelogs.exe -l c:\\path\\to\\logdir\\logs\\error.%Y-%m-%d-%H-%M-%S.log 86400'.     .
2:
The Apache service named  reported the following error:
>>> AH00015: Unable to open logs     .

Hi Gregg,

sorry about my lacking reply, I did not catch there had been replies to my post. I will try the double backslashes and give an update asap.

Forgot to mention.

mod_http2
This also come with the fix for the problem mentioned here: https://forum.apachehaus.com/index.php?topic=1614.0

The patch used has been included as well inside the zip file.

OpenSSL updated to 1.1.1g
This OpenSSL update covers 1 high severity vulnerability.

 Changes between 1.1.1f and 1.1.1g [21 Apr 2020]

  *) Fixed segmentation fault in SSL_check_chain()
     Server or client applications that call the SSL_check_chain() function
     during or after a TLS 1.3 handshake may crash due to a NULL pointer
     dereference as a result of incorrect handling of the
     "signature_algorithms_cert" TLS extension. The crash occurs if an invalid
     or unrecognised signature algorithm is received from the peer. This could
     be exploited by a malicious peer in a Denial of Service attack.
     (CVE-2020-1967)
     [Benjamin Kaduk]

The other change does not apply as we do not build with no-asm.

  *) Added AES consttime code for no-asm configurations
     an optional constant time support for AES was added
     when building openssl for no-asm.
     Enable with: ./config no-asm -DOPENSSL_AES_CONST_TIME
     Disable with: ./config no-asm -DOPENSSL_NO_AES_CONST_TIME
     At this time this feature is by default disabled.
     It will be enabled by default in 3.0.
     [Bernd Edlinger]


You can get your copy of the updated Apache HTTP Server from our download page.

I'm pulling the plug on VC14 builds since my VC14 keeps disintegrating. First it would crash building Curl x86, then x86 something else I cannot remember which but I'm done with building curl + the new something on another computer.

Apache 2.4.next is going to be built with VS16.

Those who want to get a head start can install the redistributable/s.

VC_redist x64

VC_redist  x86

I will also start getting VS16 versions of the modules on the download page next week.

Why VS and not VC. Every time the Visual Studio team in Redmond gets a new leader it seems their versioning changes. For instance;

Visual Studio 6 had VisualC++ 6 or VC6 for short.
Visual Studio 2003 had VisualC++ 7. VC7 for short.
Visual Studio 2016 has VisualC++ 14. VC14 for short.
Visual Studio 2017 has VisualC++ 14.1 but internally is Visual Studio 15 (VS15) .
Visual Studio 2019 has VisualC++ 14.2 but internally is VS16.

No problem, thanks for fixing the downloader!  Stay safe!!

Ethan