Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
A while back, I posted this possible workaround for crashes that can happen when trying to launch Xbox 360 PC setup to install the necessary software on a Windows Media Center 2005 system to enable it to act as a Media Center extender.
The setup executable for Xbox 360 PC setup (named dvcsetup.exe) is written in C#, and in cases where the .NET Framework is not functioning correctly, this setup will crash when it is launched. The previous workaround I posted described how to clean off and reinstall the .NET Framework 1.1.
In recent weeks, I have heard from a couple of customers who tried to use this workaround but still saw Xbox 360 PC setup crash on their system. When I looked at the Xbox 360 PC setup package in more detail, I realized that it will try to install the .NET Framework 1.1 and 1.1 SP1 if they are not already installed. That means that in some cases the Xbox 360 PC setup package may be using the .NET Framework 1.0 as the runtime version when it attempts to launch. Therefore, the previous workaround of repairing the .NET Framework 1.1 may not be helpful on systems that only have the .NET Framework 1.0 installed when trying to run Xbox 360 PC setup.
How to repair the .NET Framework 1.0
In cases where you see crashes when launching Xbox 360 PC setup on a Windows Media Center PC that does not have the .NET Framework 1.1 or higher installed, you can use the steps in this blog post to repair the version of the .NET Framework 1.0 that is included as part of the OS on Media Center systems.
How to repair the .NET Framework 1.1 or 2.0
If you see crashes when launching Xbox 360 PC setup on a Windows Media Center PC that does have the .NET Framework 1.1 and/or 2.0 installed, you can use the following steps to repair the .NET Framework 1.1 and/or 2.0 on your system:
I am flummoxed.
I am running XP Pro SP2 and attempted to update the installed Microsoft
.NET Framework 1.1 with the Service Pack 1 as suggested by Windows
Update. After the file is downloaded, the installation goes awry as a
couple of runtime error warning messages are presented and then after
clicking OK to those, a "Visual Studio Just-In-Time Debugger" error
box is presented with the following message:
"An unhandled win32 exception occurred in SL31.tmp .
Just-In-Time debugging this exception failed with the following error:
No installed debugger has Just-In-Time debugging enabled. In Visual
Studio, Just-In-Time debugging can be enabled from
Check the documentation index for 'Just-in-time debugging, errors' for
At that point I click the error message box and Windows Update
subsequently reports the installation was successful. However, the
installation is not successful, as this Service Pack shows up again in
the Windows Update and is not found in Add/Remove Programs. This
series of failed steps is repeatable.
I reinstalled (repaired) my build of XP Pro this morning in the hope
this problem could be overcome. Unfortunately, after a reinstall the
same sequence of events occur.
I don't have "Visual Studio" installed, nor ever have, so I can't
simply enable per the advice in the error message box. I believe
Visual Studio is not a free product?
Is there another way to enable JIT debugging without using Visual Studio so I
can move past this inability to install a "high priority" update from
MS? Is there something quite simple I am overlooking?
I have never experienced an issue such as this and I am a bit unnerved
at the moment, especially after performing a Repair Install. I was of
the belief that XP Pro SP2 would install the .NET framework 1.1 and I
would be in good shape.
In addition...I am receiving the following "MS Visual C++ Runtime Library" error
messages on a machine running XP Pro SP2:
Microsoft Visual C++ Runtime Library
This application has requested the Runtime to terminate it in an
unusual way. Please contact the application's support team for more
The error message seems to pop up when I am attempting to install or
uninstall things (e.g., IE7, Service packs indicated as "high
priority" by Windows Update, etc.).
Similar as the other one, but the file "msiexec.exe" seems to be the
culprit this time.
I tried using the .NET Framework cleanup tool, but the error messages above are presented during this activity as well.
I should note that all of this began recently when I discovered I had issues with the "gacutil.exe" process hanging while installing or uninstalling certain programs. I wound up having to go into Task Manager and end the process manually (each time it hangs during the install or uninstall routine) with limited success (sometimes the program installs correctly and other times it won't).
In an effort to correct the problem, I blindly uninstalled .NET Framework 2.0 to no avail (prior to stumbling upon your web blog). I reinstalled 2.0 (and yes, the "gacutil.exe" process hang plagued this installation at a particular point-- I recall "bootstrapi" or something to that effect) and even downloaded/installed the 2.0 SDK package thinking I could "steal" the newer "gacutil.exe" and associated config file from it and place it in the directory path where the .NET Framework directory resided. Again, no help...
So, I have uninstalled the two aforementioned .NET Framework 2.0 packages and have run into different issues as a result. Some of the programs I had installed under the 2.0 environment started to misbehave (e.g., Logitech SetPoint control panel) and I have reinstalled those that could be reinstalled (essentially those that do not call "gacutil.exe" in their installation routine. One such program (add-in, actually) which does use the "gacutil.exe" process during installation is the "Lookout" plugin for Outlook. When I started Outlook for the first time after uninstalling .NET framework 2.0, I was advised that some elements might not work properly. "Lookout" was one of these elements. I can not get it to install properly at this point-- it only causes Outlook to freeze. Another example is the Windows Live Local plugin for Outlook. It was installed before I began my trek toward "gacutil.exe" peace, but now is not functional within Outlook. When I attempt to reinstall, it appears to do so successfully (it doesn't use the "gacutil.exe" process), but the end result is missing.
At the end of all this, I attempted to perform a "detect and repair" within Outlook. This procedure resulted in a process hanging as well-- this time "msiexec.exe" is the culprit. I had unregistered/reregistered the Windows Installer, so I can't explain why this process would hang at this point.
Please offer your thoughts relative to how I can extract myself from this mess. I can't install/uninstall anything using Windows Installer at this point.
Quick followup to my above post...and please move both to another thread if more appropriate.
I just used the "SetupVerifier" tool and it reported the install of .NET 2.0 could not be verified. I reinstalled .NET 1.1 and surprisingly did not get any errors during installation. I found .NET 1.1 in my Add/Remove Programs so I was certain the tool would verify its existence. I was wrong. :-(
Not only did 1.1 not verify, but a couple of error messages popped up--
1) Runtime Error! -- \...\filelistgen.exe
2) Visual Studio JIT debugger
I'm not suicidal, but this has confounded me...
Hi Mhowie - I'm not sure how to explain the behavior you are seeing. The file gacutil.exe is not a part of the .NET Framework 1.1 or 2.0 setup, and it is not being run at all during either of those installation processes. You may need to uninstall and reinstall Windows Installer 3.1 to try to solve the msiexec.exe crashes that you are seeing when uninstalling or installing products on your system. Can you please try to uninstall Windows Installer 3.1 from Add/Remove Programs if it is listed there, and then install it again from http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c?
After doing that, can you please try again to run the .NET Framework cleanup tool and remove any existing versions and then reinstall them? You can find information about the cleanup tool at http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx.
If that fails, please send me the cleanup tool log file from your %temp% directory so I can try to take a look. You can send the log file to Aaron.Stebner (at) microsoft (dot) com.
In our SBS world the addition of .NET 2.0 sometimes mangles our Remote Web Workplaces, Companywebs and