Since many people encounter the same problem with 4.2.3 & 2.0.43 on windows environment, I'm just wondering if this is a bug. This solution works well, but does it mean, we can't use 4.2.3, but only 4.3.0-dev?

----

 Another possible method 
Dear frustrated friends: 

After nearly two years, I finally felt compelled to upgrade Apache from 1.3 (I think) to 2.0.43, as well as upgrade my PHP build (last update in June). 

Anyway - like many others, I was having major problems with Apache loading the module. I tried all of the suggestions in this thread, as well as from other sites, but to no avail (but they certainly lead me in the right direction.) 

The following is what I ended up getting to work: 

- Uninstalled old Apache 
- Removed old PHP 
- Installed Apache 2.0.43 (c:/servers/Apache2) - performed basic static server configuration 
- Installed/Configured PHP 4.2.3 (c:/php) 
- Added the following to Apache's httpd.conf 

LoadModule php4_module c:/php/sapi/php4apache2.dll 
AddType application/x-httpd-php .php 

- Tried running apache (it failed) 
- Replaced c:/php/sapi/php4apache2.dll (from 4.2.3 build) with php4apache2.dll (4.3.0 pre build) 
- Tried running apache (it failed) 
- Replaced %SYSTEMROOT%/php4ts.dll (4.2.3 build) with php4ts.dll (4.3.0 pre build) 
- Tried running apache (it failed) 
- Removed %SYSTEMROOT%/php4ts.dll 
- Copied the 4.3.0 pre build of php4ts.dll to c:/php/sapi 
- Tried running apache (it worked!!) 

All I can figure is that Apache was not searching for the php4ts.dll dependency properly, but I don't really know. However, I am sure that neither php4apache2.dll nor php4ts.dll from the 2.4.3 build worked in any configuration. I only had luck after replacing those files with the ones from the 4.3.0 pre build. 

I'd be interested to hear if someone had the same situation as myself, and found my method to work... maybe I'm just odd ;-) 

Good luck! 

-Aaron