Glad to at least have found this thread, however VERY frustrated with this new install!

Installed on a new computer and ran into this problem:

FAILED TO LOAD PHP DEBUGGER CLIENT

FAILED TO START DEBUGGER LISTENER (PORT #10015)

PLEASE REINSTALL PRODUCT

Looked at the information mentioned here and actually CANNOT locate the HKEY_CLASSES_ROOT mentioned in the registry.

The product launches but cannot debug (the main reason I BOUGHT this product)

Appreciate any guidance...

Make sure you have administrator or equvivalent rights on your computer. Then reinstall the product.

Yep, I have admin rights and have reinstalled the product 2x now...

Appreciate further guidance...

It works fine on my Windows 2000 machine and did on my Windows XP (without SP2)

Bought a newer computer from Dell and changed the license to it and now can't debug!

Thanks!

If you have any firewall such as NIS, OUTPOST etc you have to allow DBGLISTENER.EXE to listen on its port.
Also make sure port is not in use by running the following command:

netstat -naop TCP

If you see any lines with local port 7869 like below:
Proto Local Address Foreign Address State PID
TCP x.x.x.x:7869 0.0.0.0:0 LISTENING 728

you have to locate the process ID (PID) in the list of processes in the Task Manager and stop it or select different port for DbgListener.

Firewall disabled and not running.

Ran the netstat -naop TCP and the 7869 port did NOT show up anywhere!

Next steps>>>

next step is to check the registry keys I posted in this thread.
then versions of the products.
DbgListener and debugger module (shown in phpinfo) should be 2.16.x
and phped should be 3.3.3

The registry all checks out!

What's with this... very, very frustrated!!

I see the following on the little satelite icon as well:

Failed to start DBG Listener, OSERR (0x2726) 'An invalid argument was supplied.

Running version 3.3.3 (Build 3395) debugger is 2.16.4

This needs to get resolved quickly as I am running further and further behind!

Thanks!

Sorry to be a PAIN, but I REALLY NEED TO GET THIS FIXED!!!

I have a project that is already 3 days late! Had I known this would caused me problems I would not have updated...

Reminds much, much to of Oracle. How can folks expect to go to production, take upgrades that break things and then expect to "remain in production"...