Handler “ExtensionlessUrlHandler-Integrated-4.0” has a bad module “ManagedPipelineHandler” in its module list

Question

To be honest, I\'ve tried to turn a dirty trick on IIS and just when I thought that I was going to get away with it, I realized my workaround doesn\'t work. Here\'s what I\'

Answer 1

Making this its own post because this had me going for hours.

I saw maybe a dozen of similar posts here and elsewhere about this problema and the aspnet_regiis fix. They weren't working for me, and aspnet_regiis was acting odd, just listing options etc.

As user ryan-anderson above indicated, you cannot enter .exe

For those less comfy with things outside IIS on the server, here's what you do in simple steps.

1. Find aspnet_regiis in a folder similar to this path. c:\Windows\Microsoft.NET\Framework\v4.0.30319\

2. Right-click command prompt in the start menu or wherever and tell it to run as administrator. Using the windows "Run" feature just won't work, or didn't for me.

3. Go back to the aspnet_regiis executable. Click-drag it right into the command prompt or copy-paste the address into the command prompt.

4. Remove, if it's there, the .exe at the end. This is key. Add the -i (space minus eye) at the end. Enter.

If you did this correctly, you will see that it starts to install asp.net, and then tells you it succeeded.