Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

How to repair the .NET Framework 1.0 that ships as part of the OS on Media Center and Tablet PC

How to repair the .NET Framework 1.0 that ships as part of the OS on Media Center and Tablet PC

  • Comments 27

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:

  1. Delete the registry value netfx under HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents
  2. Rename the registry values ServicePackSourcePath and SourcePath located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup to ServicePackSourcePath2 and SourcePath2
  3. Rename the file netfxocm.dll located at %windir%\system32\dllcache
  4. Download the file netfxocm.dll (located in the zip file here) and copy it to %windir%\system32\setup.  A Windows File Protection error will likely appear shortly after doing this, and for now you can press cancel and ignore it.
  5. Create a file named netfx_repair.inf that contains the following text (or download it from here):
    [Version]
    Signature = "$Windows NT$"
    DriverVer=10/01/2002,5.2.3790.0
    [Components]
    netfx=netfxocm.dll,UrtOcmProc,netfxocm.inf,,7
  6. Open a cmd prompt and run the following command: sysocmgr /i:<full path to netfx_repair.inf>.  This will bring up the Windows optional component installer wizard.  Press next and installation/repair of the .NET Framework 1.0 component will begin.  You will be told that you need your original OS installation disc.  Press OK on that dialog.
  7. After pressing OK, you will be prompted to browse to the location of your OS installation disc.  In the browse dialog, you will need to browse to the folder \cmpnents\netfx\i386 on your OS installation disc or network share.  Windows XP Tablet PC Edition and Windows XP Media Center Edition include a file named netfx.cab on their installation discs in the \cmpnents\netfx\ sub-folder, and that cab file contains the files needed for the .NET Framework 1.0.
  8. After optional component setup finishes, rename the registry values ServicePackSourcePath2 and SourcePath2 located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup to ServicePackSourcePath and SourcePath

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>

 

  • Note that winisp.com is now offline (at least for me) and is being redirected to redweb.org?

    So can't download any of the tools or dll files.

    So far unable to repair my xp mce installation but will repost after trying a few more options.

    Cheers, and thanks for making this sort of information available.

    -Matt Ridings
  • Hi Matt - it looks like there was some kind of outage on the ISP that I'm using to host my tools downloads, but it appears to be up and working now. Can you please try the download again and see if it works for you? If it doesn't work, can you please contact me directly by using http://blogs.msdn.com/astebner/contact.aspx and I will email you a copy of the file directly instead?
  • Thank you! With your help I was able to fix my broken Tablet! I'm not sure what caused it, if it was the .NET SDK or .NET 2.0 Framework I installed but something broke my tablet input panel. I tried to fix it by reinstalling XP SP2 but that made the situation worse and I wasn't able to install or uninstall SP2 afterwards.

    I struggled with it for two days until I found this blog. Thank you so much for having such a useful site! :o)
  • Dear Aaron, I am having problems with my MCE to run some aspx pages. I am used to XP Pro to test my pages, and now I got this MCE 2005 which I cannot make it to run some codes in the aspx to test the files as I do in the Pro version. It only display some basic pages, and the same file works fine in the XP Pro.

    I have an HP which doesn't come with the intallating CDs anymore, and I made the recovery disk which contain the I386 folder. When I ran the sysocmgr, from your instructions, it asked for the I386 folder in the windows disk 2, and I could not point to a folder that contains the wished files.

    Any clue in how to solve me problem? I've been messing with this computer for over 3 days and I am tired of it and getting crazy now. Thanks for any tips. My email is dandancast@gmail.com , Daniel
  • Hi Daniel - I am not sure what to suggest in your scenario.  When I try the steps listed in this blog post, it gives me a Browse dialog that I can use to browse to the folder that contains the .NET Framework files.  Are you sure that this dialog that asks for the i386 folder does not let you change to a new path?
  • A while back, I posted this possible workaround for crashes that can happen when trying to launch Xbox...
  • PingBack from http://blogs.msdn.com/astebner/articles/454956.aspx
  • 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:

    sysocmgr /i:c:\netfx_repair.inf

    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:

    [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup]

    SourcePath

  • I tried the same set of steps, and got the disappearing wizard described by Nicolas Crawford. I went and changed

    [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath2]

    back to

    [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath]

    Ran in CMD window:

     sysocmgr /i:netfx_repair.inf

    The component shown has no name:

    [x]_________________56.6MB

    [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?

    Thanks.

  • 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 ?

    Thank you

  • 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.

Page 1 of 2 (27 items) 12
Leave a Comment
  • Please add 7 and 1 and type the answer here:
  • Post