ich habe das Problem gelöst...
Es lag an der installierten Firewall Filseclabs. Obwohl alle Prozesse und die Firewall beendet worden, ging der Apache nicht. In einem englischen Forum hatte jemand das gleiche Problem...
I don't know if this helps you, but I got the same problem with my
Apache just until today. It appeared day or two ago and I finally
isolated the problem to my newly installed firewall. It was Filseclabs
Personal Firewall Professional. Uninstalled it and the Apache worked
again. Od thing was that the firewall weren't blocking apache in
anyway, atleast in the configurations or did not show any deny
activities for the apache.exe. Still that solved my problem. Sad thing
is that the Filseclab firewall seemed quite good in other matter,
lighweight and really nice to configure with
ip/protocol/port/application based rules.
Ich bedanke mich für eure Hilfe...bis zum nächsten Problem