logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in RSS X


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
Post new topic   Forum Index -> Apache View previous topic :: View next topic
Reply to topic   Topic: VS17 binaries 2.4.66 & later, because of imcompatibilty
Author
Emphramla



Joined: 21 Jun 2026
Posts: 1
Location: USA, Missouri

PostPosted: Sat 04 Jul '26 1:03    Post subject: VS17 binaries 2.4.66 & later, because of imcompatibilty Reply with quote

I've been going around in circles and stopped after the 2nd trip, and here I am hoping there's a simple answer. My Apache setup is via Laragon in Windows 10 for WordPress development along with discussion forum either MyBB or UBB.Threads

I have been using Apache 2.4.62 VS17 and PHP 8.3 VS16, both 64-bit, and there have been no compatibility problem by PHP's VS16 with Apache's VS17.

I upgraded to Apache 2.4.68 VS18 when I saw the version number progress since .62. I also figured upgrading to PHP 8.4 would be good because of the length of time, but not 8.5 yet because it's so recent and there's the issue of WordPress plugins compatibility.

However, Laragon tells me that Apache 2.4.68 VS18 doesn't like PHP 8.4.22 VS17 because VS17 isn't compatible with VS18. The Apache Lounge site says the higher VS numbers are backwards compatible with the lower, and this cuckoo incompatibility didn't happen prior with Apache 2.4.62 VS17 and PHP 8.3 VS16, and also doesn't happen with Apache 2.4.68 VS18 and PHP 8.3 VS16.

The Apache Haus has VS17 binaries but those downloads are disabled/unavailable, so Apache Lounge is the only source but has only VS18. Is there something that can be put in a "conf" file or "ini" file for the compatibility to work???
----------------------------------------------

Update a while later after I'd decided to do one last effort as a last resort or last-ditch-effort because of an SMTP error for replying to the verification e-mail to create my account here on Apache Lounge in order to post this message.

A search result came up when I typed in "download apache 2.4 vs17 binaries", and it's a page here on Apache Lounge. A search phrase like that sounds so much like wanting a babysitter, like it's just the lazy-wimpy way to get to the downloads instead of going to the company website and then finding the links. But I'd already done that, multiple times. The address in that search on this here site is https://www.apachelounge.com/download/VS17/ , but when using the normal links on the left side of the screen, the only category that shows is for VS18 and nothing for VS17. So then, when I go to the VS17 page there isn't a VS18 link on the left, but only "VS17" & "Additional". This VS17 page should be added to the links on the left side of the VS18 page in addition to "Home" and "VS18" that are already there.

Now that I have VS17 binary of Apache 2.4.68, there is no more compatibility error in Laragon. However, if the VS numbers are supposed to be backwards compatible, then that's still something to get figured out.
Back to top


Reply to topic   Topic: VS17 binaries 2.4.66 & later, because of imcompatibilty View previous topic :: View next topic
Post new topic   Forum Index -> Apache