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 couple of months ago I posted some instructions about how to repair the OCM version of the .NET Framework 1.1 that ships as part of the OS on Windows Server 2003 (at this location). When I wrote that post, I knew that there would eventually be questions about how to perform a similar repair for the version of the .NET Framework 1.0 that ships as part of the OS on Windows XP Media Center Edition and Tablet PC Edition, but I skipped those instructions at the time because they are more complicated. Yesterday, I came to work and found a comment on one of my blog posts asking that very question, so now it is time to list these steps as well. I apologize in advance for the complicated nature of these steps - I promise that if we knew then what we know now we would have engineered our OCM setup to make this easier.
Here are the steps required to manually repair the .NET Framework 1.0 on Media Center and Tablet PC:
Note, you can verify that the .NET Framework 1.0 component was repaired by looking at the contents of the log file named %windir%\netfxocm.log. You should see entries towards the end indicating that several files were installed to the GAC, type libraries were re-registered, performance counters were re-registered, etc.
<update date="8/19/2007"> Added more specific details about where to browse for .NET Framework 1.0 source files </update>
<update date="6/24/2009"> Fixed broken download links. </update>
Hi, I've tried this a couple times, but on step 6, I am not getting asked for a path to install files from. I've saved the file in the root directory of c: and am typing this in exactly:
When it pulls up the wizard, though, it's a black checkbox that's selected, and after clicking next, the wizard disappears without asking for a path to install from. Any thoughts? Thanks!
Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework
Was there more to that reply?
Hi Nicholas - I looked at this a little more, and there is a registry value that controls where Windows will looks when you run sysocmgr to try to find the source files. You may want to try to temporarily changes the value of the following registry entry and re-run step 6 and see if that helps in this scenario:
I tried the same set of steps, and got the disappearing wizard described by Nicolas Crawford. I went and changed
Ran in CMD window:
The component shown has no name:
[Details] button is disabled.
I Click [Next].
Something flashes on the screen, and then the wizard disappears. Nothing new appears in the Event Viewer.
btw, The value in this key is "D:\", same as ServicePackSourcePath. There is no disk in D:, the DVDRW drive.
Has a fix been found? Should I skip this manual step and run the .Net Framework cleanup tool?
Hi Mpowered - I haven't heard of a scenario like you describe yet. If the steps in this post do not work, I'd suggest trying to do a full repair/re-install of your OS instead of just a targeted repair of the .NET Framework 1.0 and see if that helps resolve this issue.
The .NET Framework 1.0 is a part of the OS on Windows XP Media Center Edition, and because of that the cleanup tool will not allow you to remove it because it would affect OS functionality. So you will not be able to use the cleanup tool in this scenario.
Hi, Aaron - I tried your process to repair .NET FRAMEWORK 1.0 on a MCE. I got exactly the same résults as Mpowered. My original problem stems from a recent MS update KB930494 which refuses to install. I can't get rid of it. Have you given any more thoughts to this problem ?
Hi Drag-vid - I tried the instructions in this blog post on my home system that is running XP Media Center Edition 2005, and I found a couple of steps that were confusing so I've updated this blog post with updated steps that will hopefully be more specific. When I follow the steps as listed in the updated post, it works as expected. Can you please try using these updated steps and see if you have any better luck here?
If that doesn't help, it may be useful to try to install/repair the .NET Framework 1.1 or 2.0 (whichever version you have that is highest on your system) - in many cases in the past, I've seen that be helpful in resolving installation issues for .NET Framework 1.0 hotfixes.
Hopefully one of these helps.