I am using visual studio 2019, I created the sample function app and try to run it then it showing the error. Please find the attached error screen shot. 
I am using visual studio 2019, I created the sample function app and try to run it then it showing the error. Please find the attached error screen shot. 
@AnilKumarKasaINFOSYSLIMITED-5153 Looks like the func.exe does not exist on the path which you see in your screenshot. Can you confirm the same?
Can you delete the AzureFunctionsTools and azure-functions-core-tools from C:\Users\ {YourUser}\AppData\Local, restarted VS and ran the solution again so it downloaded the tools in AppData and then executed without errors. If it does not help I will suggest you to reinstall the function core tool from here
Hi MayankBargali,
Thanks for your response, Yes .Func.exe does not exist in the path.
I can't find the azure-functions-core-tools in the path C:\Users\ {YourUser}\AppData\Local, but I found this
folder in the path AzureFunctionsTools. I deleted it and then restarted my VS but still facing the same issue.
While running the my function app.
can you please suggest me on this.
Thanks
@AnilKumarKasaINFOSYSLIMITED-5153 We installed the azure core tools again and verify whether the path is same where it was finding the func.exe and the issue was fixed.
I'm having this same issue, but when I reinstall the core tools and restart Visual Studio, it's still looking at the incorrect path (path of a user folder that no longer exists).
Is there anywhere in Visual Studio where the path to this debug executable can be defined?
@TadhgConghaile-7697 You need to make sure that you are installing the same bit (32 bit/64 bit) visual studio and azure core tools. In case if you are still facing the issue feel free to create a new Q&A post and provide the details of your azure core tool and visual studio version along with the bit you have installed.
Actually, I followed your other response on this question and deleted the AzureFunctionsTools folder from "C:\Users{YourUser}\AppData\Local" and Visual Studio then looked at the correct path.
Thank you!
8 people are following this question.