Window Media Center won't work with .Net v3.5 SP1. Help RRS feed

  • Question

  • I installed .Net Framework v3.5 and sp1 because my XSitePro2 website software said I had to have it.  Now I can not access Media Center on either my desktop or laptop, both running XP sp2 or 3(?).  I get the message:  ...install >net Framework version v1.1.4322.

    Will installing this version wipe out 3.5 version?  XSitepro requires .net 2.0 as a minimum to run.  When I initially installed .net v2.0 only v 1.1 installed and the XSitepro software program said it was not sufficient to run on that version.  So I installed 3.5 with the sp1.

    Please help.  I am not a techie or a programmer so I need kindergarten level assistance.  Thank you,

    Monday, January 25, 2010 7:04 PM


  • Hi Sharon,

    Thank you for your post.

    Some clarification with you:
    Do you mean that you cannot access Windows Media Center?
    What's the exact error message you noticed when you accessed Windows Media Center?

    I have both Windows Media Center and .NET Framework 3.5 SP1 installed on my laptop. They can work side by side.

    Installing .NET Framework 1.1 will not affect .NET Framework 3.5. .NET Frameworks can co-exist with each other.

    It seems that the error is related to .NET Framework 1.1. Could you please help me to try Verification Tool to verify .NET Framework 1.1 on your machine? Please check the verification result from "Current Status".

    If .NET Framework 1.1 cannot be verified successfully, your issue could be related to corrupted .NET Framework installation. You might try:
    - Use Cleanup tool to clear .NET Framework 1.1
    - Download .NET Framework 1.1 and install it

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Wednesday, February 3, 2010 2:09 AM
    Wednesday, January 27, 2010 7:03 AM