How to Fix "PageHandlerFactory-Integrated" bad module "ManagedPipelineHandler in IIS7

by Doug Updated June 18, 2014

HTTP Error 500.21 - Internal Server Error - IIS 7.5

After setting up a new Windows 7 computer with IIS 7.5 and Visual Studio 2010, I tried to start my ASP.NET 4.0 website using the Local IIS web server. However, right off the bat I was hit with the following IIS error message:

HTTP Error 500.21 - Internal Server Error Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.

I knew the website worked correctly, because it ran fine in the Visual Studio Development Server, just not in IIS 7. Apparently, the reason I was recieving the Internal Server error message was that I had installed SQL Server 2008, after installing Visual Studio 2010, and because of this it corrupted the IIS Machine level configuration files ("If you install VS2010 and then install VS2008 and VS2008 SP1, the configuration files for ASP.NET in IIS only include about 1/2 of the correct .Net 4.0 configuration sections." read more here).

To repair this problem I ran a full silent repair of the .NET Framework 4.0. Here's how on either a 32 bit or 64 bit computer:

Click Start -> All Programs -> Accessories -> Run
In the Open textbox paste in the following line (see list of all .NET Framework version install, repair and unistall command lines here):

For silent repair on 32 bit computer with .Net Framework version 4.0.30319 use:
```
%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
```
For silent repair on 64 bit computer with .Net Framework version 4.0.30319 use:
```
%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
```
Click OK to start the repair
After, the repair ran for a few minutes, I restarted IIS 7.5, and things began to work correctly!

Hopefully, that will work for you...

Some people also seem to be having success correcting this error by running aspnet_regiis.exe. I initially tried this and it did not work for me, but feel free to give it a shot. (Keep in mind for the example below I have .Net Framework version 4.0.3.0319 installed on my computer, but you may need to change directory version to what is installed on your computer): Here's how to run aspnet_regiis.exe:

Run "aspnet_regiis.exe" program from command line (within Command Prompt):

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i

If you want to open it using the Run program, just type in "Run" in the Windows 7 search box, then use the following line below in the Open box, then click OK:

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i

Note if your computer is 64 bit, then I would change the line to:

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i

Hopefully, these solutions help get you up and running and fix the IIS7 error... Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.

UPDATE (6-16-2014): The solutions above didn't work for my on a new Windows Server 2008 box that I was setting up, which had pre-installed SQL Server 2008, which I then installed SQL Server 2014. What finally worked for me, was removing SQL Server 2008, then doing a repair of the .NET Framework (latest version 4.5.1) from: Control Panel -> Programs -> Programs and Features -> then right-click on "Microsoft .NET Framwork 4.5.1" and click Uninstall/Change" -> then go through the Repair prompts -> and restart your computer or server. This seemed to do the trick. (Also, I did remove a previous version of "Microsoft .NET Framework 4.5 Multi-Targeting Pack", but I'm not sure if that had any impact on solving the issue. I think the real problem lies with SQL Server 2008 and it somehow screwing up the .NET Framework.

See Microsoft's solution here: http://msdn.microsoft.com/en-us/library/hh168535(v=nav.71).aspx

You may want to download the Microsoft .NET Framework Repair Tool here: http://www.microsoft.com/en-us/download/details.aspx?id=30135

176

176 Comments

by julio on 7/4/2010 thank Doug , without your help i shall be kill Gates and all their emploees. :-)
by Leo on 7/13/2010 YOU ARE AWESOME! Thank you so much. I would never think that installing SQL server 2008 then VS2010 would have any thing to do with corrupting ISS configuration. I repaired .net 4.0 and my .net 4 web app works fine now. Thanks a billion!!!
by Doug on 7/13/2010 Hey Leo, glad to hear the solution helped you get things working!
by Tony on 7/16/2010 Thanks a lot - saved me tearing my hair out!
by Wallies on 7/19/2010 Thanks for this post. It really saved me hours. Couldn't figure out wtf was going wrong :)
by Ago on 7/19/2010 This solution sure saved me a lot of time! Thank you!
by Brian on 7/21/2010 Great post - lots of detail, and fixed the problem perfectly! Thanks so much...
by Nanung on 8/2/2010 Thank you very much. Where do you learn this kind of things? I really anxious how people in the internet can solve such this kind of problem... :)
by Rukshan Chathura on 8/3/2010 Great work !
by SJ on 8/3/2010 Thank you soooooo much Doug :)
by William on 8/11/2010 Doug, thanks for the solution. The first step worked for me immediately.
by Mark Hebron on 8/11/2010 WOW! Thanks Doug, worked like a treat !!!!!!!!!!!!!!!!!!!!!
by Doug on 8/11/2010 Awesome... glad to hear it worked for you!
by Reggie on 8/15/2010 Thanks Doug!! the initial step worked for my 64bit Windows 7 setup. Saved me a lot of time and frustration!!
by Dave Schinkel on 8/27/2010 Also try just completely uninstalling and re-installing IIS in add/remove entirely. It's fixed weird IIS problems like this before for me.
by Iheacho Henry on 8/29/2010 Thank you so very much, I have been on this for 4 weeks without solution until now. I am excited.
by Ara Martitosyan on 9/1/2010 "aspnet_regiis.exe -i" did the job
by Mirela on 10/11/2010 Thank you. It saved me a lot of time.
by shaggy on 10/20/2010 Thanks - I hadn't done any SQL server installs but I got the same error on my production server. Ran the quiet repair for .Net4.0 and it all works. thanks again.
by PeterMunnings on 11/3/2010 Thanks so much - just installed a new win 7 machine and couldn't work out what the problem was
by Bob K on 11/16/2010 What a nuisance, these errors! Thanks for the recipe!
by Andy on 11/20/2010 Thank you!!! This sort of thing normally entails hours of frustrated wasted time poking around - simply doing this fixed it straight away. Thank goodness for people like you and (ironically) for the internet!
by FtpDaemon on 11/22/2010 sweet, that helped a lot. 10x!
by conejo on 11/23/2010 Thanks a lot!
by dvilner on 11/24/2010 Thanks for the post, saved me lots of time!
by bdotjones on 11/24/2010 thanks for the help
by DavidHun on 12/17/2010 Worked perfectly! Saved me tons of time!
by Legatou on 12/28/2010 You just solved what 4 hours of hunting couldn't. I applaud thee, Doug. Brilliant solution.
by saman on 12/28/2010 Thank u Doug, it really works like a charm, saved me a long time
by Elad on 1/5/2011 My goodness.. it worked like a charm.. thanks so much.
by Paul on 1/15/2011 Brilliant! I wasted 6 hours hacking around before I found this. Ever so grateful!
by Doug on 1/15/2011 Glad this article helped save you some time... I definitely know the feeling of searching for hours on end looking for a solution to a problem!
by Mark on 1/17/2011 Luckily I googled this error and your post was the first one I looked at. Thanks for the post!
by Bertrand on 1/21/2011 Thanks! It worked perfectly on Win 7 64bit. It takes few minutes, I just had to monitor started process with Process Explorer to see when it's finished.
by Nagarajan on 1/25/2011 thanks a lot its working perfectly
by Ralf on 1/26/2011 Thanks so much!! The repair command fixed it. Like you said, I had to wait a bit for the changes to take effect.
by Michael on 1/26/2011 Thanks man!! It worked perfectly! ;)
by Ankit Singhal on 1/29/2011 This worked for me. Thanks a lot for sharing this. God Bless you.
by Jonathan on 1/30/2011 Worked for me, too. Add me to the list of people who owe you.
by Curt on 1/31/2011 Sweet, High 5!
by soupreme on 2/10/2011 I was cursing M$, Windows 7 and IIS 7.5 for an hour. Thanks!!!
by jle8604 on 2/12/2011 Thanks for the advice!
by john on 2/16/2011 Thank you!!!
by adrianpadilla.net on 2/17/2011 Doug, yours was the most useful post EVER this saved me hours of frustration
by tom on 2/20/2011 aspnet_regiis -i worked for me. thanks!
by Azeem on 2/22/2011 Thank you doug
by Niall on 2/23/2011 Thanks! - aspnet_regiis.exe worked for me!
by Vighnesh Prabhudesai on 2/24/2011 Perfect !!!! the .NET repair just did it all ... Cheers! Vighnesh
by Chris on 2/24/2011 Thanks, aspnet_regiis worked for me :-)
by Mohammed on 2/27/2011 Dude, seriously I don't know how to thank you. you are a life savior.
by Marco Segundo on 3/1/2011 Thanks!
by Jebb Burditt on 3/1/2011 Worked perfect. Good thing too because I had no idea what the problem was.
by Saif on 3/5/2011 Thanks a Ton!
by Jordy van Eijk on 3/9/2011 Hi Doug, Thank you very much. The second solution worked for me.. Cheers from Holland!
by Edu on 3/10/2011 Thanks buddy, it was very helpful
by Andrei Ladunca on 3/11/2011 Tks a lot, second comand worked like a charm.
by Jan Birkmose on 3/11/2011 Thank you so much for saving my day and my hair
by Naif on 3/13/2011 Thank you very much
by Ratnakar Dutt on 3/13/2011 Thanks for this, very last one worked for me.
by Essam Shaker on 3/15/2011 Thank you very much, it solved my problem after hours of searching
by Faten Slaibi on 3/16/2011 Replying to Nanung on 2/08/2010 : The people who post such solutions are people mostly working for Microsoft. Who else would know the innards of the problem but them. Thanks for the solution though.
by Leoconco on 3/18/2011 Thanks a lot, very helpful. Simple and effective solution
by Hannah on 3/21/2011 Thanks, that program command fixes the problem
by luka on 3/23/2011 thanks, helped moa
by Louis on 3/23/2011 Thanks for this.
by fattyboombatty on 3/29/2011 Thank you -perfect fix
by JD on 3/29/2011 Killer fix! Thanks
by AD on 4/2/2011 thanks, it works now :)
by Jason Snelders on 4/3/2011 Awesome! I went for the "aspnet_regiis.exe –i" option and it worked. A word for the wary - my system was pre-installed with Windows 7 and tight application lock-down so I had to create a Windows shortcut and run that as Administrator for it to work, otherwise it just listed the aspnet_regiis.exe options.
by agieos on 4/6/2011 Thank you so much your tutorial, it's help me full for my problem. :)
by Thanuja on 4/7/2011 Great work man..! it was really useful...
by Kumar on 4/9/2011 thanks!
by M. Aamir on 4/12/2011 Worked for me as well. Thanks!
by kotsos on 4/13/2011 Worked like a charm! Thanks.
by asok on 4/13/2011 Thank you, you're a life saver. I booted a virgin amazon instance and it came with this problem.
by Doug on 4/14/2011 Awesome! So glad the solution worked out for you... I'm surprised you experienced the problem with an amazon instance, but I'm glad it worked to solve the problem!
by Sean on 4/15/2011 Windows Server 2008 R2 x64 The ".exe" was messing up the utility from working. It would just display the help. This worked: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis –i
by TomK on 4/18/2011 Thank You! It worked on Winsows 7 Pro 64bit.
by amin on 4/24/2011 ok, it's work
by TDL on 4/27/2011 Thanks for this, solved it for me!
by Steve on 4/27/2011 Thanks so much for this fix. Dont ever take this post down... even though you wrote this entry a long time ago, it is still vital info for the dev community. (One would think MS would fix this. Oh well.)
by Zak on 5/1/2011 Thanks Doug solved the issue in a jiffy!
by SOFF on 5/6/2011 Thanks, it was useful for me
by Anonymous on 5/8/2011 Super fix... thanks
by Keith on 5/11/2011 Thanks a million. Great fix.
by bkuhn on 5/17/2011 Thanks! The aspnet_regiis -i worked like a champ!
by Sondre on 5/19/2011 The first line totally fixed it right away. AWESOME!
by ucreateit on 5/27/2011 Thanks for the fix! It worked great.
by Yener on 5/29/2011 Great article. Thanks for the effort!
by .g on 5/30/2011 Thanks a lot
by Paul on 5/31/2011 I used: aspnet_regiis -ir And ensured my app pool was runing V4 of the framework. Using -ir rather than -i will have less impact on any other web applications on the server
by Alex on 6/2/2011 Seriously, you are my hero! Married me!
by Arman on 6/3/2011 Thank you SO much bro.
by Yusuf on 6/4/2011 Thank you so much "MasBro"
by punkuz on 6/17/2011 awesome.. life saver
by RamakrishnanRS on 6/17/2011 Thanks a ton, Doug !!! The first step did the trick :-)
by Palmtree on 6/19/2011 Thanks a lot
by Benjamin on 6/20/2011 Thanks a million. It worked.
by kimsok on 6/20/2011 Worked for me. Thanks so much.
by Dan on 6/27/2011 None of the run scripts were working for me, but I knew I had installed vs2008 after vs2010. So, I went and downloaded the most recent version of .Net 4 and boom. It worked. I just wanted to say thank you for your post. It led me to the right solution.
by aldosp on 7/4/2011 thanks %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i is work for me
by Willim Kahler on 7/6/2011 Oh... My..Thank you so much!! I can't believe that these errors are due to incomplete setup on the windows machine itself. I thought Microsoft was past these "early day" iis issues...
by sam patel on 7/8/2011 thank's
by renu on 7/14/2011 Thanks it worked.
by Sagi on 7/18/2011 Works like magic! 10x!
by M. Furqan Khan on 7/25/2011 Initially i was getting error even after applying the fix. But then i realized my mistake that my project was still open in Visual Studio while applying the suggested fix. As soon as i restarted the Visual Studio, the error was fixed. Thanks a lot!
by aedna on 8/1/2011 your solution works!! thank you
by Anitha on 8/11/2011 Thanks a lot. the first solution worked for me. I thought of reinstalling IIS 6.0 by replacing iis 7.5
by picce on 8/23/2011 I have the same problem, but I can't use remote server console to run aspnet_regiis.exe. Do you have any suggestion?
by Akshay Purabia on 8/29/2011 Thanks buddy, your effort are highly appreciated. Really man you have done gr8 job
by pelle susenbeth on 9/1/2011 people like you makes internet worhwhile :)
by felix on 9/7/2011 thanks very much
by Martins on 9/7/2011 +1
by Kevin Gaskin on 9/14/2011 Excellent article, Very clear and concise
by Nicolai on 9/22/2011 Brilliant article. I copied the commands to http://confighell.com/IIS for future reference, and linked back to this article. Thanks!
by Shahid Afzal on 10/3/2011 Millions of thanks .I just run %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart and then run %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i and now its working
by DieDaily on 10/11/2011 Solution worked. I installed SQL Server 2008 R2 BEFORE I installed VS2010 and still I had this error, so you may be wrong about why you had the error. Who cares, though, a great fix that saved me who knows how many hours! Thanks!
by vikram on 10/19/2011 Thanks for the TIP
by RoguePixel on 10/19/2011 You must type out the " -i" manually if you copy and paste the register with IIS command. Easter Egg left over from Windows 2000 and continues to remain even in 2008 R2. Tip of the day: switch to C++
by pwandz on 10/21/2011 RoguePixel, you're actually wrong. In the code snippet, the HEX value for the hyphen is 0x96, when the 'normal' hyphen on a keyboard is 0x2D. Blindly copying and pasting it puts in a non-standard hyphen, so the program doesn't understand. Might be a flaw in the forum's code that changes it, or Doug has a weird keyboard or something
by Doug on 10/21/2011 RoguePixel and pwandz, I'm not exactly sure why you guys are running into problems when copying and pasting the command in. I just tried (copy and pasting) on a Windows 7 computer (language: English-US) and it worked fine. The website's text editor (Tiny_MCE) that I use for the site will change " –i" to html code " –i". However, if I were to manually type " -i" using the minus key, the command does NOT run correctly using the "Run" box or "Command Prompt".
by germanSharper on 10/27/2011 aspnet_regiis.exe -i worked for me fine :) thanks
by Hassan Ali on 10/31/2011 Works like a charm! Thanks a lot for the post!
by Napster on 11/3/2011 thanks buddy that was helpful
by Daverino on 11/3/2011 Dude - you the man. %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i worked for me. First time.
by Pudd on 11/4/2011 Thanks very much!
by it's just me on 12/6/2011 Genius. What can I say?
by Sanaj on 12/15/2011 Thanks, it worked
by Wes on 12/16/2011 Awesome, the last option did it for me.
by Guru on 12/24/2011 My life was miserable for the last 20 days. Thanks a ton for this solution! Worked brilliant after restoring the .NET.
by Dan on 12/28/2011 It works on Win 2008 R2 64 bit. Thank you!
by Martin on 1/11/2012 Thanks a lot. Great solution!!!
by Jim Plant on 1/18/2012 Worked first time. Many thanks.
by Kevin on 1/23/2012 I already pulled out all my hair, but this kept me from pulling the trigger of the gun in my mouth. Awesomeness!
by CJD on 1/23/2012 Thanks. I moved a website over to a new VM with Windows 2008 R2 x64 / IIS 7.5 and had the problem. Your fix solved it. I was watching TaskMgr while the install was running so that I would know when it was done, and it looks like aspnet_regiis gets run during the silent install process.
by Axel Arnold Bangert on 1/29/2012 Thanks a lot, I run Apache on 80 and IIS7 on 8088. After installing VS6 the IIS 8088 deployment Server always threw the above mentioned error. The fix did it. I guess, that a new install of VS2010 would do it too, but this fix is a very finde and elegant solution. Where did you find that originally - I can't believe that someone deploys that by his own - or am I wrong? But thanks a lot! Axel Arnold Bangert - Herzogenrath 2012
by Parag Daraji on 2/10/2012 Thanks a ton it works for me. ;-)
by Michael Washington on 2/28/2012 Worked for me! However you have to be patient and wait for it to finish.
by Takeshi on 3/1/2012 Thanks a lot! that work like a magic :)
by Luis on 3/8/2012 Worked like a charm!
by Nei on 4/9/2012 Thanks man, this solve my problem :)
by Bernard on 4/16/2012 This did not work for me, I had a Win 7 setup with IIS. I installed the ".Net 4 Client Profile" setup, then did a repair but it still did not fix the problem. I finally fixed it by installing the "Full .Net Fx 4" setup, it also did only a "repair" but this time it worked.
by Marcos on 4/19/2012 Funciono perfecto !!!!! mil gracias.
by Shawkat on 5/18/2012 Excellent Work mate! "ASPNET_REGIIS.exe -i" worked for me.. i had another problem before it, though. Needed to disable the Authorisation to NONE in the web config file in the project. thanks again..
by George Birbilis on 5/30/2012 %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i worked for me on a x64 WinServer2008R2 - the reason of the error at the 1st place was that I had uninstalled VWD and various ASP.net tool installs for it, then installed VS ultimate I think
by Lariusz on 6/19/2012 Thanx Doug it works fine for me.
by Brent on 6/29/2012 It worked for me too, but i don't have vs2010 installed on my webserver. I didn't set up the box initially, so i don't know what the network admins might have done to cause it. Does anyone know the cause of this problem? Thanks for the remedy regardless!
by André Luiz on 6/29/2012 Òtimo, deu certo, muito obrigado!!!
by ying on 7/3/2012 you are super !!!!!!!!!!!!!!!!!!! it cost me weeks without results. so simple solution. thank you!!!!!!!!!!!!!
by nm on 7/11/2012 Glad I found this... was pulling hair out!! Thanks!!!
by Jeff on 7/20/2012 Still a great fix, solved my problem. Thanks!
by Anne on 8/2/2012 Perfect!!! I think Microsoft owes you big time.
by Elpi on 8/4/2012 You are very awesome,big kiss.just one precision after execute this command: %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart, restart your computer and it's will work. thanks a lot
by Rei-li on 8/11/2012 At first it didn't work for me. I tried to reinstall Microsoft .NET Framework 4 Extended but it also didn't work. After this reinstallation I tried %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart once again and this time it solved my problem. thanks
by Martin on 9/6/2012 Had three very similar sites on Windows Server 2008 R2, one of which threw this error. aspnet_regiis.exe –i fixed it for me.
by Dung Pham on 9/14/2012 Thanks you my friend.
by Pilu on 9/17/2012 Thanx!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
by Bill on 10/2/2012 Thanks. The .net repair said that I had a bad package but the aspnet_regiis.exe -i solved my problem.
by Asim Siddiqui on 10/11/2012 %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i Works for me. Thanks man
by Colo-Colo de Chile!!!! on 10/17/2012 Thanks. Works for me.
by Mike on 10/26/2012 Thanks! I got past the error with the aspnet_regiis command.
by Miarantsoa on 11/15/2012 Thank you so much for your help !!
by Adriano on 11/23/2012 Thank you so much !
by ahmad on 1/7/2013 tnx for your help.. it's so useful for me..
by Damien on 1/17/2013 Thank you, worked a perfectly
by abdessamd on 3/19/2013 tnx for your help
by Harsh anand on 4/4/2013 open command prompt on window and run C:\Windows\Microsoft.NET\Framework\v4.0.30319\ aspnet_regiis.exe -i this will resolve your issue
by PhanCongPhuoc on 6/29/2013 Another case may cause this problem is the framework we use, casting from 2.0 to 3.5 or 4.0. In these case we have to choose Framework 4.0 with Framework 3.5 is enable on IIS
by Himanshu on 8/5/2013 Thanks bro! You Rock
by Jai on 9/3/2013 thanks, it's working for me.
by Todd on 10/8/2013 That worked! Saved me a lot of time, you have my gratitude!
by daledondale on 12/5/2013 windows 7 settings: x86 Windows’ta: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe /i x64 Windows’ta: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /i
by Bogdan0x400 on 12/13/2013 I can't use setup.exe from way #1 to reinstall .NET FW 4.0 because I have .NET FW 4.5 installed. aspnet_regiis -i from way #2 doesn't help :( .
by Saeed on 3/31/2014 you are exclusive! no body think this solution
by MooseMan on 5/27/2014 Worked today for me as well. Spent two days working on this one.
by super_dragon on 7/15/2014 thanks, you have my gratitude!

by julio on 7/4/2010

thank Doug , without your help i shall be kill Gates and all their emploees. :-)

by Leo on 7/13/2010

YOU ARE AWESOME! Thank you so much. I would never think that installing SQL server 2008 then VS2010 would have any thing to do with corrupting ISS configuration. I repaired .net 4.0 and my .net 4 web app works fine now. Thanks a billion!!!

by Doug on 7/13/2010

Hey Leo, glad to hear the solution helped you get things working!

by Tony on 7/16/2010

Thanks a lot - saved me tearing my hair out!

by Wallies on 7/19/2010

Thanks for this post. It really saved me hours. Couldn't figure out wtf was going wrong :)

by Ago on 7/19/2010

This solution sure saved me a lot of time! Thank you!

by Brian on 7/21/2010

Great post - lots of detail, and fixed the problem perfectly! Thanks so much...

by Nanung on 8/2/2010

Thank you very much. Where do you learn this kind of things? I really anxious how people in the internet can solve such this kind of problem... :)

by Rukshan Chathura on 8/3/2010

Great work !

by SJ on 8/3/2010

Thank you soooooo much Doug :)

by William on 8/11/2010

Doug, thanks for the solution. The first step worked for me immediately.

by Mark Hebron on 8/11/2010

WOW! Thanks Doug, worked like a treat !!!!!!!!!!!!!!!!!!!!!

by Doug on 8/11/2010

Awesome... glad to hear it worked for you!

by Reggie on 8/15/2010

Thanks Doug!! the initial step worked for my 64bit Windows 7 setup. Saved me a lot of time and frustration!!

by Dave Schinkel on 8/27/2010

Also try just completely uninstalling and re-installing IIS in add/remove entirely. It's fixed weird IIS problems like this before for me.

by Iheacho Henry on 8/29/2010

Thank you so very much, I have been on this for 4 weeks without solution until now. I am excited.

by Ara Martitosyan on 9/1/2010

"aspnet_regiis.exe -i" did the job

by Mirela on 10/11/2010

Thank you. It saved me a lot of time.

by shaggy on 10/20/2010

Thanks - I hadn't done any SQL server installs but I got the same error on my production server. Ran the quiet repair for .Net4.0 and it all works.

thanks again.

by PeterMunnings on 11/3/2010

Thanks so much - just installed a new win 7 machine and couldn't work out what the problem was

by Bob K on 11/16/2010

What a nuisance, these errors! Thanks for the recipe!

by Andy on 11/20/2010

Thank you!!! This sort of thing normally entails hours of frustrated wasted time poking around - simply doing this fixed it straight away. Thank goodness for people like you and (ironically) for the internet!

by FtpDaemon on 11/22/2010

sweet, that helped a lot. 10x!

by conejo on 11/23/2010

Thanks a lot!

by dvilner on 11/24/2010

Thanks for the post, saved me lots of time!

by bdotjones on 11/24/2010

thanks for the help

by DavidHun on 12/17/2010

Worked perfectly! Saved me tons of time!

by Legatou on 12/28/2010

You just solved what 4 hours of hunting couldn't. I applaud thee, Doug. Brilliant solution.

by saman on 12/28/2010

Thank u Doug, it really works like a charm, saved me a long time

by Elad on 1/5/2011

My goodness.. it worked like a charm.. thanks so much.

by Paul on 1/15/2011

Brilliant! I wasted 6 hours hacking around before I found this. Ever so grateful!

by Doug on 1/15/2011

Glad this article helped save you some time... I definitely know the feeling of searching for hours on end looking for a solution to a problem!

by Mark on 1/17/2011

Luckily I googled this error and your post was the first one I looked at. Thanks for the post!

by Bertrand on 1/21/2011

Thanks! It worked perfectly on Win 7 64bit.
It takes few minutes, I just had to monitor started process with Process Explorer to see when it's finished.

by Nagarajan on 1/25/2011

thanks a lot its working perfectly

by Ralf on 1/26/2011

Thanks so much!!

The repair command fixed it. Like you said, I had to wait a bit for the changes to take effect.

by Michael on 1/26/2011

Thanks man!! It worked perfectly! ;)

by Ankit Singhal on 1/29/2011

This worked for me. Thanks a lot for sharing this. God Bless you.

by Jonathan on 1/30/2011

Worked for me, too. Add me to the list of people who owe you.

by Curt on 1/31/2011

Sweet, High 5!

by soupreme on 2/10/2011

I was cursing M$, Windows 7 and IIS 7.5 for an hour. Thanks!!!

by jle8604 on 2/12/2011

Thanks for the advice!

by john on 2/16/2011

Thank you!!!

by adrianpadilla.net on 2/17/2011

Doug, yours was the most useful post EVER this saved me hours of frustration

by tom on 2/20/2011

aspnet_regiis -i worked for me. thanks!

by Azeem on 2/22/2011

Thank you doug

by Niall on 2/23/2011

Thanks! - aspnet_regiis.exe worked for me!

by Vighnesh Prabhudesai on 2/24/2011

Perfect !!!! the .NET repair just did it all ...

Cheers!
Vighnesh

by Chris on 2/24/2011

Thanks, aspnet_regiis worked for me :-)

by Mohammed on 2/27/2011

Dude, seriously I don't know how to thank you. you are a life savior.

by Marco Segundo on 3/1/2011

Thanks!

by Jebb Burditt on 3/1/2011

Worked perfect. Good thing too because I had no idea what the problem was.

by Saif on 3/5/2011

Thanks a Ton!

by Jordy van Eijk on 3/9/2011

Hi Doug, Thank you very much. The second solution worked for me.. Cheers from Holland!

by Edu on 3/10/2011

Thanks buddy, it was very helpful

by Andrei Ladunca on 3/11/2011

Tks a lot, second comand worked like a charm.

by Jan Birkmose on 3/11/2011

Thank you so much for saving my day and my hair

by Naif on 3/13/2011

Thank you very much

by Ratnakar Dutt on 3/13/2011

Thanks for this, very last one worked for me.

by Essam Shaker on 3/15/2011

Thank you very much, it solved my problem after hours of searching

by Faten Slaibi on 3/16/2011

Replying to Nanung on 2/08/2010 : The people who post such solutions are people mostly working for Microsoft. Who else would know the innards of the problem but them. Thanks for the solution though.

by Leoconco on 3/18/2011

Thanks a lot, very helpful. Simple and effective solution

by Hannah on 3/21/2011

Thanks, that program command fixes the problem

by luka on 3/23/2011

thanks, helped moa

by Louis on 3/23/2011

Thanks for this.

by fattyboombatty on 3/29/2011

Thank you -perfect fix

by JD on 3/29/2011

Killer fix! Thanks

by AD on 4/2/2011

thanks, it works now :)

by Jason Snelders on 4/3/2011

Awesome! I went for the "aspnet_regiis.exe –i" option and it worked. A word for the wary - my system was pre-installed with Windows 7 and tight application lock-down so I had to create a Windows shortcut and run that as Administrator for it to work, otherwise it just listed the aspnet_regiis.exe options.

by agieos on 4/6/2011

Thank you so much your tutorial, it's help me full for my problem. :)

by Thanuja on 4/7/2011

Great work man..! it was really useful...

by Kumar on 4/9/2011

thanks!

by M. Aamir on 4/12/2011

Worked for me as well. Thanks!

by kotsos on 4/13/2011

Worked like a charm!

Thanks.

by asok on 4/13/2011

Thank you, you're a life saver. I booted a virgin amazon instance and it came with this problem.

by Doug on 4/14/2011

Awesome! So glad the solution worked out for you... I'm surprised you experienced the problem with an amazon instance, but I'm glad it worked to solve the problem!

by Sean on 4/15/2011

Windows Server 2008 R2 x64

The ".exe" was messing up the utility from working. It would just display the help. This worked:

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis –i

by TomK on 4/18/2011

Thank You! It worked on Winsows 7 Pro 64bit.

by amin on 4/24/2011

ok, it's work

by TDL on 4/27/2011

Thanks for this, solved it for me!

by Steve on 4/27/2011

Thanks so much for this fix. Dont ever take this post down... even though you wrote this entry a long time ago, it is still vital info for the dev community. (One would think MS would fix this. Oh well.)

by Zak on 5/1/2011

Thanks Doug solved the issue in a jiffy!

by SOFF on 5/6/2011

Thanks, it was useful for me

by Anonymous on 5/8/2011

Super fix... thanks

by Keith on 5/11/2011

Thanks a million. Great fix.

by bkuhn on 5/17/2011

Thanks! The aspnet_regiis -i worked like a champ!

by Sondre on 5/19/2011

The first line totally fixed it right away. AWESOME!

by ucreateit on 5/27/2011

Thanks for the fix! It worked great.

by Yener on 5/29/2011

Great article. Thanks for the effort!

by .g on 5/30/2011

Thanks a lot

by Paul on 5/31/2011

I used:

aspnet_regiis -ir

And ensured my app pool was runing V4 of the framework. Using -ir rather than -i will have less impact on any other web applications on the server

by Alex on 6/2/2011

Seriously, you are my hero! Married me!

by Arman on 6/3/2011

Thank you SO much bro.

by Yusuf on 6/4/2011

Thank you so much "MasBro"

by punkuz on 6/17/2011

awesome.. life saver

by RamakrishnanRS on 6/17/2011

Thanks a ton, Doug !!!

The first step did the trick :-)

by Palmtree on 6/19/2011

Thanks a lot

by Benjamin on 6/20/2011

Thanks a million. It worked.

by kimsok on 6/20/2011

Worked for me. Thanks so much.

by Dan on 6/27/2011

None of the run scripts were working for me, but I knew I had installed vs2008 after vs2010.

So, I went and downloaded the most recent version of .Net 4 and boom. It worked.

I just wanted to say thank you for your post. It led me to the right solution.

by aldosp on 7/4/2011

thanks
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i is work for me

by Willim Kahler on 7/6/2011

Oh... My..Thank you so much!! I can't believe that these errors are due to incomplete setup on the windows machine itself. I thought Microsoft was past these "early day" iis issues...

by sam patel on 7/8/2011

thank's

by renu on 7/14/2011

Thanks it worked.

by Sagi on 7/18/2011

Works like magic!
10x!

by M. Furqan Khan on 7/25/2011

Initially i was getting error even after applying the fix. But then i realized my mistake that my project was still open in Visual Studio while applying the suggested fix. As soon as i restarted the Visual Studio, the error was fixed.
Thanks a lot!

by aedna on 8/1/2011

your solution works!! thank you

by Anitha on 8/11/2011

Thanks a lot. the first solution worked for me. I thought of reinstalling IIS 6.0 by replacing iis 7.5

by picce on 8/23/2011

I have the same problem, but I can't use remote server console to run aspnet_regiis.exe. Do you have any suggestion?

by Akshay Purabia on 8/29/2011

Thanks buddy, your effort are highly appreciated. Really man you have done gr8 job

by pelle susenbeth on 9/1/2011

people like you makes internet worhwhile :)

by felix on 9/7/2011

thanks very much

by Martins on 9/7/2011

by Kevin Gaskin on 9/14/2011

Excellent article, Very clear and concise

by Nicolai on 9/22/2011

Brilliant article.

I copied the commands to http://confighell.com/IIS for future reference, and linked back to this article.

Thanks!

by Shahid Afzal on 10/3/2011

Millions of thanks .I just run
%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart
and
then
run %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i
and now its working

by DieDaily on 10/11/2011

Solution worked. I installed SQL Server 2008 R2 *BEFORE* I installed VS2010 and still I had this error, so you may be wrong about why you had the error. Who cares, though, a great fix that saved me who knows how many hours! Thanks!

by vikram on 10/19/2011

Thanks for the TIP

by RoguePixel on 10/19/2011

You must type out the " -i" manually if you copy and paste the register with IIS command. Easter Egg left over from Windows 2000 and continues to remain even in 2008 R2.

Tip of the day: switch to C++

by pwandz on 10/21/2011

RoguePixel, you're actually wrong.

In the code snippet, the HEX value for the hyphen is 0x96, when the 'normal' hyphen on a keyboard is 0x2D.

Blindly copying and pasting it puts in a non-standard hyphen, so the program doesn't understand.

Might be a flaw in the forum's code that changes it, or Doug has a weird keyboard or something

by Doug on 10/21/2011

RoguePixel and pwandz,

I'm not exactly sure why you guys are running into problems when copying and pasting the command in.

I just tried (copy and pasting) on a Windows 7 computer (language: English-US) and it worked fine. The website's text editor (Tiny_MCE) that I use for the site will change " –i" to html code " –i". However, if I were to manually type " -i" using the minus key, the command does NOT run correctly using the "Run" box or "Command Prompt".

by germanSharper on 10/27/2011

aspnet_regiis.exe -i worked for me fine :) thanks

by Hassan Ali on 10/31/2011

Works like a charm! Thanks a lot for the post!

by Napster on 11/3/2011

thanks buddy that was helpful

by Daverino on 11/3/2011

Dude - you the man.

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i

worked for me. First time.

by Pudd on 11/4/2011

Thanks very much!

by it's just me on 12/6/2011

Genius. What can I say?

by Sanaj on 12/15/2011

Thanks, it worked

by Wes on 12/16/2011

Awesome, the last option did it for me.

by Guru on 12/24/2011

My life was miserable for the last 20 days. Thanks a ton for this solution! Worked brilliant after restoring the .NET.

by Dan on 12/28/2011

It works on Win 2008 R2 64 bit. Thank you!

by Martin on 1/11/2012

Thanks a lot. Great solution!!!

by Jim Plant on 1/18/2012

Worked first time. Many thanks.

by Kevin on 1/23/2012

I already pulled out all my hair, but this kept me from pulling the trigger of the gun in my mouth. Awesomeness!

by CJD on 1/23/2012

Thanks. I moved a website over to a new VM with Windows 2008 R2 x64 / IIS 7.5 and had the problem. Your fix solved it. I was watching TaskMgr while the install was running so that I would know when it was done, and it looks like aspnet_regiis gets run during the silent install process.

by Axel Arnold Bangert on 1/29/2012

Thanks a lot,
I run Apache on 80 and IIS7 on 8088. After installing VS6 the IIS 8088 deployment Server always threw the above mentioned error.
The fix did it. I guess, that a new install of VS2010 would do it too, but this fix is a very finde and elegant solution.
Where did you find that originally - I can't believe that someone deploys that by his own - or am I wrong?
But thanks a lot!
Axel Arnold Bangert - Herzogenrath 2012

by Parag Daraji on 2/10/2012

Thanks a ton it works for me. ;-)

by Michael Washington on 2/28/2012

Worked for me! However you have to be patient and wait for it to finish.

by Takeshi on 3/1/2012

Thanks a lot! that work like a magic :)

by Luis on 3/8/2012

Worked like a charm!

by Nei on 4/9/2012

Thanks man, this solve my problem :)

by Bernard on 4/16/2012

This did not work for me, I had a Win 7 setup with IIS.

I installed the ".Net 4 Client Profile" setup, then did a repair but it still did not fix the problem. I finally fixed it by installing the "Full .Net Fx 4" setup, it also did only a "repair" but this time it worked.

by Marcos on 4/19/2012

Funciono perfecto !!!!! mil gracias.

by Shawkat on 5/18/2012

Excellent Work mate! "ASPNET_REGIIS.exe -i" worked for me.. i had another problem before it, though. Needed to disable the Authorisation to NONE in the web config file in the project.
thanks again..

by George Birbilis on 5/30/2012

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i
worked for me on a x64 WinServer2008R2 - the reason of the error at the 1st place was that I had uninstalled VWD and various ASP.net tool installs for it, then installed VS ultimate I think

by Lariusz on 6/19/2012

Thanx Doug it works fine for me.

by Brent on 6/29/2012

It worked for me too, but i don't have vs2010 installed on my webserver. I didn't set up the box initially, so i don't know what the network admins might have done to cause it.

Does anyone know *the cause* of this problem?

Thanks for the remedy regardless!

by André Luiz on 6/29/2012

Òtimo, deu certo, muito obrigado!!!

by ying on 7/3/2012

you are super !!!!!!!!!!!!!!!!!!!
it cost me weeks without results.
so simple solution.
thank you!!!!!!!!!!!!!

by nm on 7/11/2012

Glad I found this... was pulling hair out!! Thanks!!!

by Jeff on 7/20/2012

Still a great fix, solved my problem. Thanks!

by Anne on 8/2/2012

Perfect!!! I think Microsoft owes you big time.

by Elpi on 8/4/2012

You are very awesome,big kiss.just one precision after execute this command:
%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart,
restart your computer and it's will work.
thanks a lot

by Rei-li on 8/11/2012

At first it didn't work for me. I tried to reinstall Microsoft .NET Framework 4 Extended but it also didn't work. After this reinstallation I tried %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart once again and this time it solved my problem.
thanks

by Martin on 9/6/2012

Had three very similar sites on Windows Server 2008 R2, one of which threw this error.
aspnet_regiis.exe –i fixed it for me.

by Dung Pham on 9/14/2012

Thanks you my friend.

by Pilu on 9/17/2012

Thanx!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

by Bill on 10/2/2012

Thanks. The .net repair said that I had a bad package but the aspnet_regiis.exe -i solved my problem.

by Asim Siddiqui on 10/11/2012

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i

Works for me.
Thanks man

by Colo-Colo de Chile!!!! on 10/17/2012

Thanks. Works for me.

by Mike on 10/26/2012

Thanks! I got past the error with the aspnet_regiis command.

by Miarantsoa on 11/15/2012

Thank you so much for your help !!

by Adriano on 11/23/2012

Thank you so much !

by ahmad on 1/7/2013

tnx for your help.. it's so useful for me..

by Damien on 1/17/2013

Thank you, worked a perfectly

by abdessamd on 3/19/2013

tnx for your help

by Harsh anand on 4/4/2013

open command prompt on window and run C:\Windows\Microsoft.NET\Framework\v4.0.30319\ aspnet_regiis.exe -i
this will resolve your issue

by PhanCongPhuoc on 6/29/2013

Another case may cause this problem is the framework we use, casting from 2.0 to 3.5 or 4.0. In these case we have to choose Framework 4.0 with Framework 3.5 is enable on IIS

by Himanshu on 8/5/2013

Thanks bro! You Rock

by Jai on 9/3/2013

thanks, it's working for me.

by Todd on 10/8/2013

That worked! Saved me a lot of time, you have my gratitude!

by daledondale on 12/5/2013

windows 7 settings:
x86 Windows’ta:
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe /i

x64 Windows’ta:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /i

by Bogdan0x400 on 12/13/2013

I can't use setup.exe from way #1 to reinstall .NET FW 4.0 because I have .NET FW 4.5 installed. aspnet_regiis -i from way #2 doesn't help :( .

by Saeed on 3/31/2014

you are exclusive! no body think this solution

by MooseMan on 5/27/2014

Worked today for me as well. Spent two days working on this one.

by super_dragon on 7/15/2014

thanks, you have my gratitude!

Add your comment

by Anonymous - Already have an account? Login now!

Your Name: Your Name is required.

Comment: Comment is required.

Enter the text you see in the image below

What do you see?

Can't read the image? View a new one.

Your comment will appear after being approved.

How to Fix "PageHandlerFactory-Integrated" bad module "ManagedPipelineHandler in IIS7

176 Comments

Add your comment

Related Posts

Ask a Question

Article Categories

Follow Us