KB943485 or 941644 - kills MP (1 Viewer)

ianc

MP Donator
  • Premium Supporter
  • December 29, 2007
    132
    1
    wicklow
    Home Country
    Ireland Ireland
    TV-Server Version:
    MediaPortal Version: 02.3.0 SVN 16611
    MediaPortal Skin: Standard
    Windows Version: XP Professional SP2
    CPU Type: Intel P4 2G
    HDD: 300GB
    Memory: 1G
    Motherboard: Shuttle
    Motherboard Chipset: Shuttle
    Motherboard Bios: Shuttle
    Video Card: Sapphire ATI 2400
    Video Card Driver: ?
    Sound Card: onboard
    Sound Card AC3:
    Sound Card Driver:
    1. TV Card: FireDTV
    1. TV Card Type: DVB-S2
    1. TV Card Driver:
    2. TV Card:
    2. TV Card Type:
    2. TV Card Driver:
    3. TV Card:
    3. TV Card Type:
    3. TV Card Driver:
    4. TV Card:
    4. TV Card Type:
    4. TV Card Driver:
    MPEG2 Video Codec:
    MPEG2 Audio Codec:
    Satelite/CableTV Provider:
    HTPC Case:
    Cooling:
    Power Supply:
    Remote:
    TV:
    TV - HTPC Connection:

    3 of my 4 MP PCs stopped working today and I hadn't messed with the config of at least two of them - Honest. MP started up ok but when I picked a video to view the display stayed at the MP "menu" screen while the soundtrack could be heard. The only thing I could see in common across the 3 PCs was that they had an automatic download & Install of KB943485 & KB941644. I removed these and all started working again. Hmm.
     

    x4mer

    MP Donator
  • Premium Supporter
  • November 8, 2007
    306
    24
    Toronto
    Home Country
    Canada Canada
    My TVE3 server updated with the 941644 update, & then all clients (only with TV plugin enabled) started having numerous issues with TV not working, videos not playing, long start up times.

    I found that turning off the windows firewall on the server fixed all the problems. I don't know whether that update turned it on, as I don't recall turning it on (I usually turn it off), or whether it changed something in the way the firewall works causing MP to fail. The 941644 is listed as a TCPIP security patch, so this may be the case.
     

    Users who are viewing this thread

    Top Bottom