UPDATE: This issue has been fixed in version 2.4.1
We are aware of this issue and are working to fix it. It came up in our testing but we decided to release with it in there anyway since it is easy to work around.
The path that is shown is the path that will be executed.
It will be fixed in the next minor release.