It looks like your IIS is not processing the routing rules for your application and is trying to find default.aspx, index.htm, etc. Since it cannot, it wants to display directory listings (which is why you got 404.14).
I just checked the setup of my dev, and I think your AppPool should be installed on Integrated, and not Classic on the managed pipeline for AppPool. I came across this before, there may be ways to use Classic Pipeline, but this will / should be the fastest way to solve your problem. To check / change the pipeline mode, click "Application Pools" in the menu to the left of IIS, find your AppPool and look in the column of the managed pipeline. If it is set to Classic โ Right-click AppPool, select the basic settings, and then change the drop-down list from Classic to Integrated.
If I'm wrong, someone, please feel free to correct me on this in the comments.
Change Just add, you can run the MVC application in classic pipeline mode, but you need to do IIS 6 tricks to make it work correctly. Basically, you need to enable the wildcard script pattern for MVC to work in classic mode if it does not expect the existence of an .aspx file (or the like) for it to handle the execution pipeline with .NET from IIS.
Tommy source share