Share via

Disabling services with MSConfig to work around setup failures

  • Article

I was talking recently with a colleague who works on the .NET Framework setup and Windows Installer technical support team here at Microsoft.  He told me about a set of steps that his team typically has customers try when they call in to report failed installations.  I wanted to post these steps here in case they are helpful to anyone else struggling to get an application installed.

This set of steps allows you to easily find all services that are installed on your system and temporarily disable them so they cannot interfere with installation processes.  It also allows you to identify and temporarily disable programs that are scheduled to start every time the system reboots.  The System Configuration tool (also known as MSConfig) allows you to manage these and other settings.

I recommend trying the following steps in cases where a product fails to install on your system and you've already tried other workarounds posted on my blog and elsewhere to attempt to resolve the issue:

  1. Click on the Start menu, choose Run, type msconfig and click OK
  2. In the System Configuration tool, click on the Services tab
  3. Check the box labeled Hide all Microsoft services
  4. Click the Disable All button to disable all non-Microsoft services
  5. In the System Configuration tool, click on the General tab
  6. Click the Selective startup radio button
  7. Uncheck the box labeled Load startup items
  8. Click OK to accept all changes in the System Configuration tool
  9. Reboot for the changes to take effect
  10. Attempt to install the application that previously failed
  11. Re-run the System Configuration tool and re-enable the services that you disabled in step 4 above

In many cases, the above steps will allow a previously failing setup package to install successfully.  Hopefully they will be useful to you as well if you find yourself in this situation.

Comments

  • Anonymous
    November 27, 2006
    The comment has been removed

  • Anonymous
    February 16, 2007
    The comment has been removed

  • Anonymous
    March 21, 2007
    A little while back, I wrote a blog post describing an interaction issue between Visual Studio setup

  • Anonymous
    January 14, 2008
    A client of ours was getting an installation error when attempting to install Microsoft .NET Framework 2.0 on his Windows XP SP2 platform. The error he would get was: "application failted to initialize properly (0xc0000142)" Just recently, his IT person was successful in installing .NET Framework 2.0 by setting the compatibility flag for "dotnetfx.exe" to "Windows 2000". How can this step work for him? Isn't the program compatibility for programs that are known to work on older systems but may not work on new platforms. Microsoft .NET Framework 2.0 was designed for Windows Vista and our client is on Windows XP. Setting its compatibility to Windows 2000 doesn't make sense. Any ideas?

  • Anonymous
    January 14, 2008
    The comment has been removed

  • Anonymous
    January 15, 2008
    Hi Aaron - I thought as much. Actually, I left a bit of information out which is that our client has created his Windows XP (sp2) platform based on an image of another computer. Maybe this causes the subtleties in the .NET 2 installation to which he was subjected. Unfortunately, due to the nature of the error, the log files do not get created. Thanks for your prompt reply.

  • Anonymous
    June 16, 2010
    Plzz Help I Install VB 2008 BUT Net Frame WOrk Is Not Installing So This Is Not Forward TO Another FIle

  • Anonymous
    June 16, 2010
    Hi Non English - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather your .NET Framework setup log files, upload the file %temp%vslogs.cab that this tool produces to a file server (such as http://skydrive.live.com) and then reply back here with a link I can use to download the log files and take a further look? In the meantime, it might also help to use the steps listed at blogs.msdn.com/.../8108332.aspx to manually remove and then try to re-install the .NET Framework 3.5 SP1 on your computer.

  • Anonymous
    September 07, 2010
    Thanks for your info. It really helped me out.

  • Anonymous
    October 13, 2010
    This post helped resolve a .NET framework install problem today.  I blogged about it here: recursivecode.blogspot.com/.../net-framework-wont-install-whos-locking.html Thanks!

  • Anonymous
    September 21, 2011
    I know this is an old post, but it still helped me. Thanks a lot!

  • Anonymous
    November 09, 2011
    excellent post,i did helped me as well. :) a .NET framework 3.5 is working now... yeah!!!