Results 1 to 9 of 9

Thread: Microsoft Windows Installer 3.1 will not install

  1. #1
    DustDevil_007 Guest

    Microsoft Windows Installer 3.1 will not install

    Keep trying to install updates and above installer 3.1 will not install. Auto
    update is turned on. Yesterday there were several updates not installed.
    Today, I just get the one message about the MS Win installer 3.1. The shield
    remains in the taskbar advising me that updates are ready to be installed,
    but I keep getting the same response. Any thoughts on this??
    --
    Roger A.

  2. #2
    TaurArian [MS-MVP] Guest

    Re: Microsoft Windows Installer 3.1 will not install

    We need some more information -

    On the WU Website, select your history of updates - now click on failed update (red mark)
    and see if there is an error code.
    If there is an error code, write it down and post back or in the alternative, do a search
    for the error code.

    Also - how to view the Update log in Windows:-

    Click Start, and then click Run.
    In the Open box, type: %windir%\windowsupdate.log
    and then click OK.

    Scroll down towards the bottom for the latest entries to locate the error code(s)
    associated with the latest failed attempt to download/install. If appropriate copy and
    paste the error codes into this thread so someone may be able to assist you. On the other
    hand, you may be able to find the error code and other suggestions by searching the
    Newsgroup.

    Also check Windows folder for file called KB******.log (****** = number of update ie
    KB896688) and post the contents of the failed update.
    This may provide further clues as to why the update failed.

    How to read the Windowsupdate.log file:
    http://support.microsoft.com/?kbid=902093

    You cannot install updates that you download from the Windows Update Web site on a Windows
    XP-based computer
    http://support.microsoft.com/?kbid=934648

    --
    ====================================
    TaurArian [MS-MVP] 2005-2007 - Australia
    ====================================
    How to make a good post: http://www.dts-l.org/goodpost.htm
    Defending your machine: http://defendingyourmachine2.blogspot.com/
    http://taurarian.mvps.org/index.htm


    "DustDevil_007" <[email protected]> wrote in message
    news:[email protected]...
    | Keep trying to install updates and above installer 3.1 will not install. Auto
    | update is turned on. Yesterday there were several updates not installed.
    | Today, I just get the one message about the MS Win installer 3.1. The shield
    | remains in the taskbar advising me that updates are ready to be installed,
    | but I keep getting the same response. Any thoughts on this??
    | --
    | Roger A.



  3. #3
    DustDevil_007 Guest

    Re: Microsoft Windows Installer 3.1 will not install

    some recent entries in the windowsupdate.log are reproduced below..

    2007-06-30 18:14:57:859 1068 710 EEHndlr FATAL: MSI DLL version is 3.0.
    Version 3.1 is required.
    2007-06-30 18:14:57:859 1068 710 Agent WARNING: Failed to evaluate Installed
    rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr = 80241001
    2007-06-30 18:15:00:312 1068 710 Handler Attempting to create remote handler
    process as ARMSTRON-8DFD60\Owner in session 0
    2007-06-30 18:15:00:671 1628 ecc Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-06-30 18:15:00:671 1628 ecc Misc = Process:
    C:\WINDOWS\system32\wuauclt.exe
    2007-06-30 18:15:00:671 1628 ecc AUClnt FATAL: Error: 0x80004002. wuauclt
    handler: failed to spawn COM server
    2007-06-30 18:15:02:078 1068 710 Handler FATAL: 0x80004002: ERROR: Remote
    update handler container process created (PID: 1628), but exited before
    signaling event
    2007-06-30 18:15:02:078 1068 710 Agent * WARNING: Exit code = 0x80004002
    2007-06-30 18:15:02:078 1068 710 Agent *********
    2007-06-30 18:15:02:078 1068 710 Agent ** END ** Agent: Installing
    updates [CallerId = MicrosoftUpdate]
    2007-06-30 18:15:02:078 1068 710 Agent *************
    2007-06-30 18:15:02:078 3560 728 COMAPI >>-- RESUMED -- COMAPI: Install
    [ClientId = MicrosoftUpdate]
    2007-06-30 18:15:02:078 3560 728 COMAPI - Install call failed
    2007-06-30 18:15:02:078 3560 728 COMAPI - Reboot required = No
    2007-06-30 18:15:02:078 3560 728 COMAPI - WARNING: Exit code = 0x80240FFF;
    Call error code = 0x80004002
    2007-06-30 18:15:02:078 3560 728 COMAPI ---------
    2007-06-30 18:15:02:078 3560 728 COMAPI -- END -- COMAPI: Install
    [ClientId = MicrosoftUpdate]
    2007-06-30 18:15:02:078 3560 728 COMAPI -------------
    2007-06-30 18:15:02:078 1068 710 Agent WARNING: WU client failed installing
    updates with error 0x80004002
    2007-06-30 18:15:02:843 3560 85c COMAPI WARNING: Operation failed due to
    earlier error, hr=80004002

    Error code looks to be 0x80004002
    --
    Roger A.


    "TaurArian [MS-MVP]" wrote:

    > We need some more information -
    >
    > On the WU Website, select your history of updates - now click on failed update (red mark)
    > and see if there is an error code.
    > If there is an error code, write it down and post back or in the alternative, do a search
    > for the error code.
    >
    > Also - how to view the Update log in Windows:-
    >
    > Click Start, and then click Run.
    > In the Open box, type: %windir%\windowsupdate.log
    > and then click OK.
    >
    > Scroll down towards the bottom for the latest entries to locate the error code(s)
    > associated with the latest failed attempt to download/install. If appropriate copy and
    > paste the error codes into this thread so someone may be able to assist you. On the other
    > hand, you may be able to find the error code and other suggestions by searching the
    > Newsgroup.
    >
    > Also check Windows folder for file called KB******.log (****** = number of update ie
    > KB896688) and post the contents of the failed update.
    > This may provide further clues as to why the update failed.
    >
    > How to read the Windowsupdate.log file:
    > http://support.microsoft.com/?kbid=902093
    >
    > You cannot install updates that you download from the Windows Update Web site on a Windows
    > XP-based computer
    > http://support.microsoft.com/?kbid=934648
    >
    > --
    > ====================================
    > TaurArian [MS-MVP] 2005-2007 - Australia
    > ====================================
    > How to make a good post: http://www.dts-l.org/goodpost.htm
    > Defending your machine: http://defendingyourmachine2.blogspot.com/
    > http://taurarian.mvps.org/index.htm
    >
    >
    > "DustDevil_007" <[email protected]> wrote in message
    > news:[email protected]...
    > | Keep trying to install updates and above installer 3.1 will not install. Auto
    > | update is turned on. Yesterday there were several updates not installed.
    > | Today, I just get the one message about the MS Win installer 3.1. The shield
    > | remains in the taskbar advising me that updates are ready to be installed,
    > | but I keep getting the same response. Any thoughts on this??
    > | --
    > | Roger A.
    >
    >
    >


  4. #4
    PA Bear Guest

    Re: Microsoft Windows Installer 3.1 will not install

    1. First install the newly released 'standalone' version of Windows Update
    Agent 3.0, v7.0.6000.374
    http://support.microsoft.com/kb/932494

    2. Now (re)install this (updated) fix:
    http://support.microsoft.com/kb/927891

    NB: Windows Update/Automatic Updates started offering 927891 on 22 May-07.
    If "Update for Windows XP (KB927891)" is listed in Add/Remove Programs (make
    sure Show Updates box is checked), it's already installed. cf.
    http://www.microsoft.com/technet/sec...ry/927891.mspx

    3. Reboot.
    --
    ~Robear Dyer (PA Bear)
    MS MVP-Windows (IE, OE, Security, Shell/User)
    AumHa VSOP & Admin; DTS-L.org


    DustDevil_007 wrote:
    > some recent entries in the windowsupdate.log are reproduced below..
    >
    > 2007-06-30 18:14:57:859 1068 710 EEHndlr FATAL: MSI DLL version is 3.0.
    > Version 3.1 is required.
    > 2007-06-30 18:14:57:859 1068 710 Agent WARNING: Failed to evaluate
    > Installed
    > rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr = 80241001
    > 2007-06-30 18:15:00:312 1068 710 Handler Attempting to create remote
    > handler
    > process as ARMSTRON-8DFD60\Owner in session 0
    > 2007-06-30 18:15:00:671 1628 ecc Misc =========== Logging initialized
    > (build: 7.0.6000.374, tz: -0500) ===========
    > 2007-06-30 18:15:00:671 1628 ecc Misc = Process:
    > C:\WINDOWS\system32\wuauclt.exe
    > 2007-06-30 18:15:00:671 1628 ecc AUClnt FATAL: Error: 0x80004002. wuauclt
    > handler: failed to spawn COM server
    > 2007-06-30 18:15:02:078 1068 710 Handler FATAL: 0x80004002: ERROR: Remote
    > update handler container process created (PID: 1628), but exited before
    > signaling event
    > 2007-06-30 18:15:02:078 1068 710 Agent * WARNING: Exit code = 0x80004002
    > 2007-06-30 18:15:02:078 1068 710 Agent *********
    > 2007-06-30 18:15:02:078 1068 710 Agent ** END ** Agent: Installing
    > updates [CallerId = MicrosoftUpdate]
    > 2007-06-30 18:15:02:078 1068 710 Agent *************
    > 2007-06-30 18:15:02:078 3560 728 COMAPI >>-- RESUMED -- COMAPI: Install
    > [ClientId = MicrosoftUpdate]
    > 2007-06-30 18:15:02:078 3560 728 COMAPI - Install call failed
    > 2007-06-30 18:15:02:078 3560 728 COMAPI - Reboot required = No
    > 2007-06-30 18:15:02:078 3560 728 COMAPI - WARNING: Exit code =
    > 0x80240FFF;
    > Call error code = 0x80004002
    > 2007-06-30 18:15:02:078 3560 728 COMAPI ---------
    > 2007-06-30 18:15:02:078 3560 728 COMAPI -- END -- COMAPI: Install
    > [ClientId = MicrosoftUpdate]
    > 2007-06-30 18:15:02:078 3560 728 COMAPI -------------
    > 2007-06-30 18:15:02:078 1068 710 Agent WARNING: WU client failed
    > installing
    > updates with error 0x80004002
    > 2007-06-30 18:15:02:843 3560 85c COMAPI WARNING: Operation failed due to
    > earlier error, hr=80004002
    >
    > Error code looks to be 0x80004002
    >
    >> We need some more information -
    >>
    >> On the WU Website, select your history of updates - now click on failed
    >> update (red mark) and see if there is an error code.
    >> If there is an error code, write it down and post back or in the
    >> alternative, do a search for the error code.
    >>
    >> Also - how to view the Update log in Windows:-
    >>
    >> Click Start, and then click Run.
    >> In the Open box, type: %windir%\windowsupdate.log
    >> and then click OK.
    >>
    >> Scroll down towards the bottom for the latest entries to locate the error
    >> code(s) associated with the latest failed attempt to download/install. If
    >> appropriate copy and paste the error codes into this thread so someone
    >> may
    >> be able to assist you. On the other hand, you may be able to find the
    >> error code and other suggestions by searching the Newsgroup.
    >>
    >> Also check Windows folder for file called KB******.log (****** = number
    >> of
    >> update ie KB896688) and post the contents of the failed update.
    >> This may provide further clues as to why the update failed.
    >>
    >> How to read the Windowsupdate.log file:
    >> http://support.microsoft.com/?kbid=902093
    >>
    >> You cannot install updates that you download from the Windows Update Web
    >> site on a Windows XP-based computer
    >> http://support.microsoft.com/?kbid=934648
    >>
    >> "DustDevil_007" <[email protected]> wrote in message
    >> news:[email protected]...
    >>> Keep trying to install updates and above installer 3.1 will not install.
    >>> Auto update is turned on. Yesterday there were several updates not
    >>> installed. Today, I just get the one message about the MS Win installer
    >>> 3.1. The shield remains in the taskbar advising me that updates are
    >>> ready
    >>> to be installed, but I keep getting the same response. Any thoughts on
    >>> this?? --
    >>> Roger A.



  5. #5
    TaurArian [MS-MVP] Guest

    Re: Microsoft Windows Installer 3.1 will not install

    Try the following:-

    Click Start, select run and type the following (pressing okay after each one):-

    net.exe stop wuauserv

    regsvr32 wuapi.dll
    regsvr32 wups.dll
    regsvr32 wuaueng.dll
    regsvr32 wucltui.dll
    regsvr32 MSXML3.dll

    net.exe start wuauserv

    Try WU again.

    If that fails - try manual download

    Windows Installer 3.1 Redistributable (v2)
    http://www.microsoft.com/downloads/d...DisplayLang=en

    If that doesn't help - reinstall the ActiveX controls (because they may have become
    corrupt):-

    Follow this article -
    The Windows Update Web site and the Microsoft Update Web site do not scan for updates when
    you repair a failed installation of Windows XP Service Pack 2 or of Windows XP Service
    Pack 1
    http://support.microsoft.com/kb/916259

    This articles still mentions the old WU client so see below for the new WU Client 3.0

    Note the new WU Client 3.0 - Windows Update Agent:
    http://download.windowsupdate.com/v7...gent30-x86.exe

    or for the 64 bit version
    http://download.windowsupdate.com/v7...gent30-x64.exe


    --
    ====================================
    TaurArian [MS-MVP] 2005-2007 - Australia
    ====================================
    How to make a good post: http://www.dts-l.org/goodpost.htm
    Defending your machine: http://defendingyourmachine2.blogspot.com/
    http://taurarian.mvps.org/index.htm

    Emails will not be acknowledged - please post to the newsgroup so all may benefit.


    "DustDevil_007" <[email protected]> wrote in message
    news:[email protected]...
    | some recent entries in the windowsupdate.log are reproduced below..
    |
    | 2007-06-30 18:14:57:859 1068 710 EEHndlr FATAL: MSI DLL version is 3.0.
    | Version 3.1 is required.
    | 2007-06-30 18:14:57:859 1068 710 Agent WARNING: Failed to evaluate Installed
    | rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr = 80241001
    | 2007-06-30 18:15:00:312 1068 710 Handler Attempting to create remote handler
    | process as ARMSTRON-8DFD60\Owner in session 0
    | 2007-06-30 18:15:00:671 1628 ecc Misc =========== Logging initialized
    | (build: 7.0.6000.374, tz: -0500) ===========
    | 2007-06-30 18:15:00:671 1628 ecc Misc = Process:
    | C:\WINDOWS\system32\wuauclt.exe
    | 2007-06-30 18:15:00:671 1628 ecc AUClnt FATAL: Error: 0x80004002. wuauclt
    | handler: failed to spawn COM server
    | 2007-06-30 18:15:02:078 1068 710 Handler FATAL: 0x80004002: ERROR: Remote
    | update handler container process created (PID: 1628), but exited before
    | signaling event
    | 2007-06-30 18:15:02:078 1068 710 Agent * WARNING: Exit code = 0x80004002
    | 2007-06-30 18:15:02:078 1068 710 Agent *********
    | 2007-06-30 18:15:02:078 1068 710 Agent ** END ** Agent: Installing
    | updates [CallerId = MicrosoftUpdate]
    | 2007-06-30 18:15:02:078 1068 710 Agent *************
    | 2007-06-30 18:15:02:078 3560 728 COMAPI >>-- RESUMED -- COMAPI: Install
    | [ClientId = MicrosoftUpdate]
    | 2007-06-30 18:15:02:078 3560 728 COMAPI - Install call failed
    | 2007-06-30 18:15:02:078 3560 728 COMAPI - Reboot required = No
    | 2007-06-30 18:15:02:078 3560 728 COMAPI - WARNING: Exit code = 0x80240FFF;
    | Call error code = 0x80004002
    | 2007-06-30 18:15:02:078 3560 728 COMAPI ---------
    | 2007-06-30 18:15:02:078 3560 728 COMAPI -- END -- COMAPI: Install
    | [ClientId = MicrosoftUpdate]
    | 2007-06-30 18:15:02:078 3560 728 COMAPI -------------
    | 2007-06-30 18:15:02:078 1068 710 Agent WARNING: WU client failed installing
    | updates with error 0x80004002
    | 2007-06-30 18:15:02:843 3560 85c COMAPI WARNING: Operation failed due to
    | earlier error, hr=80004002
    |
    | Error code looks to be 0x80004002
    | --
    | Roger A.
    |
    |
    | "TaurArian [MS-MVP]" wrote:
    |
    | > We need some more information -
    | >
    | > On the WU Website, select your history of updates - now click on failed update (red
    mark)
    | > and see if there is an error code.
    | > If there is an error code, write it down and post back or in the alternative, do a
    search
    | > for the error code.
    | >
    | > Also - how to view the Update log in Windows:-
    | >
    | > Click Start, and then click Run.
    | > In the Open box, type: %windir%\windowsupdate.log
    | > and then click OK.
    | >
    | > Scroll down towards the bottom for the latest entries to locate the error code(s)
    | > associated with the latest failed attempt to download/install. If appropriate copy and
    | > paste the error codes into this thread so someone may be able to assist you. On the
    other
    | > hand, you may be able to find the error code and other suggestions by searching the
    | > Newsgroup.
    | >
    | > Also check Windows folder for file called KB******.log (****** = number of update ie
    | > KB896688) and post the contents of the failed update.
    | > This may provide further clues as to why the update failed.
    | >
    | > How to read the Windowsupdate.log file:
    | > http://support.microsoft.com/?kbid=902093
    | >
    | > You cannot install updates that you download from the Windows Update Web site on a
    Windows
    | > XP-based computer
    | > http://support.microsoft.com/?kbid=934648
    | >
    | > --
    | > ====================================
    | > TaurArian [MS-MVP] 2005-2007 - Australia
    | > ====================================
    | > How to make a good post: http://www.dts-l.org/goodpost.htm
    | > Defending your machine: http://defendingyourmachine2.blogspot.com/
    | > http://taurarian.mvps.org/index.htm
    | >
    | >
    | > "DustDevil_007" <[email protected]> wrote in message
    | > news:[email protected]...
    | > | Keep trying to install updates and above installer 3.1 will not install. Auto
    | > | update is turned on. Yesterday there were several updates not installed.
    | > | Today, I just get the one message about the MS Win installer 3.1. The shield
    | > | remains in the taskbar advising me that updates are ready to be installed,
    | > | but I keep getting the same response. Any thoughts on this??
    | > | --
    | > | Roger A.
    | >
    | >
    | >



  6. #6
    DustDevil_007 Guest

    Re: Microsoft Windows Installer 3.1 will not install

    I checked which version I had of the MSI, and it was 3.1.4000.4039. I have
    tried every suggestion that was given, except to reinstall the ActiveX
    compents, which I don't know how to do. At last check, I have 74 security and
    other updates to install, but they fail to install every time. Here is latest
    entries from windowsupdate.log
    007-07-01 13:43:01:703 1068 f00 Agent *
    {C2367B85-F734-481B-967E-6C8B6F4FEBA1}.101
    2007-07-01 13:43:01:703 1068 f00 Agent * Title = Security Update for
    Windows XP (KB935839)
    2007-07-01 13:43:01:703 1068 f00 Agent * UpdateId =
    {E2E1C013-B99A-4683-921C-B99663F3F8ED}.103
    2007-07-01 13:43:01:703 1068 f00 Agent * Bundles 1 updates:
    2007-07-01 13:43:01:703 1068 f00 Agent *
    {6E945291-FDE4-45E9-BA16-4A6B11411772}.103
    2007-07-01 13:43:05:968 1068 f00 Handler Attempting to create remote handler
    process as ARMSTRON-8DFD60\Owner in session 0
    2007-07-01 13:43:06:250 3856 f14 Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-07-01 13:43:06:250 3856 f14 Misc = Process:
    C:\WINDOWS\system32\wuauclt.exe
    2007-07-01 13:43:06:250 3856 f14 AUClnt FATAL: Error: 0x80004002. wuauclt
    handler: failed to spawn COM server
    2007-07-01 13:43:07:125 1068 f00 Handler FATAL: 0x80004002: ERROR: Remote
    update handler container process created (PID: 3856), but exited before
    signaling event
    2007-07-01 13:43:07:250 1068 f00 Agent * WARNING: Exit code = 0x80004002
    2007-07-01 13:43:07:250 1068 f00 Agent *********
    2007-07-01 13:43:07:250 1068 f00 Agent ** END ** Agent: Installing
    updates [CallerId = MicrosoftUpdate]
    2007-07-01 13:43:07:250 1068 f00 Agent *************
    2007-07-01 13:43:07:250 1068 f00 Agent WARNING: WU client failed installing
    updates with error 0x80004002
    2007-07-01 13:43:07:562 3536 dec COMAPI >>-- RESUMED -- COMAPI: Install
    [ClientId = MicrosoftUpdate]
    2007-07-01 13:43:07:562 3536 dec COMAPI - Install call failed
    2007-07-01 13:43:07:562 3536 dec COMAPI - Reboot required = No
    2007-07-01 13:43:07:562 3536 dec COMAPI - WARNING: Exit code = 0x80240FFF;
    Call error code = 0x80004002
    2007-07-01 13:43:07:562 3536 dec COMAPI ---------
    2007-07-01 13:43:07:562 3536 dec COMAPI -- END -- COMAPI: Install
    [ClientId = MicrosoftUpdate]
    2007-07-01 13:43:07:562 3536 dec COMAPI -------------
    2007-07-01 13:43:08:328 3536 dd4 COMAPI WARNING: Operation failed due to
    earlier error, hr=80004002
    2007-07-01 14:10:09:703 2324 850 Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-07-01 14:10:09:703 2324 850 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2007-07-01 14:10:09:703 2324 850 Misc = Module:
    C:\WINDOWS\system32\wuapi.dll
    2007-07-01 14:10:09:703 2324 850 COMAPI ----------- COMAPI:
    IUpdateServiceManager::AddService -----------
    2007-07-01 14:10:09:703 2324 850 COMAPI - ServiceId =
    {7971f918-a847-4430-9279-4a52d1efe18d}
    2007-07-01 14:10:09:703 2324 850 COMAPI - AuthorizationCabPath =
    C:\WINDOWS\SoftwareDistribution\AuthCabs\muauth.cab
    2007-07-01 14:10:09:718 1068 ee0 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\7971f918-a847-4430-9279-4a52d1efe18d.auth.cab.temp\muauth.cab:
    2007-07-01 14:10:09:718 1068 ee0 Misc Microsoft signed: Yes
    2007-07-01 14:10:09:734 3068 c00 Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-07-01 14:10:09:734 3068 c00 Misc = Process:
    C:\WINDOWS\system32\wuauclt.exe
    2007-07-01 14:10:09:734 3068 c00 Misc = Module:
    C:\WINDOWS\system32\wuaueng.dll
    2007-07-01 14:10:09:734 3068 c00 DtaStor Update service properties: service
    registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2007-07-01 14:10:09:734 2324 850 COMAPI - Added service, URL =
    http://update.microsoft.com/microsoftupdate/
    2007-07-01 14:10:09:734 2324 850 COMAPI ----------- COMAPI:
    IUpdateServiceManager::RegisterServiceWithAU -----------
    2007-07-01 14:10:09:734 2324 850 COMAPI - ServiceId =
    {7971f918-a847-4430-9279-4a52d1efe18d}
    2007-07-01 14:10:09:796 2324 850 Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-07-01 14:10:09:796 2324 850 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2007-07-01 14:10:09:796 2324 850 Misc = Module:
    C:\WINDOWS\system32\muweb.dll
    2007-07-01 14:10:09:796 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-07-01 14:10:09:843 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:10:250 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-07-01 14:10:10:265 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:10:281 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab:
    2007-07-01 14:10:10:296 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:10:437 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab:
    2007-07-01 14:10:10:453 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:11:937 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wsus3setup.cab:
    2007-07-01 14:10:11:953 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:11:968 2324 850 Setup *********** Setup: Checking whether
    self-update is required ***********
    2007-07-01 14:10:11:968 2324 850 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\WebSetup\wsus3setup.inf
    2007-07-01 14:10:11:968 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:11:968 2324 850 Setup * IsUpdateRequired = No
    2007-07-01 14:10:11:984 2324 850 Misc =========== Logging initialized
    (build: 7.0.6000.374, tz: -0500) ===========
    2007-07-01 14:10:11:984 2324 850 Misc = Process: C:\Program Files\Internet
    Explorer\iexplore.exe
    2007-07-01 14:10:11:984 2324 850 Misc = Module:
    C:\WINDOWS\system32\wuweb.dll
    2007-07-01 14:10:11:984 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-07-01 14:10:12:000 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:140 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-07-01 14:10:12:140 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:171 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab:
    2007-07-01 14:10:12:171 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:437 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wuident.cab:
    2007-07-01 14:10:12:437 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:453 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wsus3setup.cab:
    2007-07-01 14:10:12:453 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:734 2324 850 Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\WebSetup\wsus3setup.cab:
    2007-07-01 14:10:12:734 2324 850 Misc Microsoft signed: Yes
    2007-07-01 14:10:12:750 2324 850 Setup *********** Setup: Checking whether
    self-update is required ***********
    2007-07-01 14:10:12:750 2324 850 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\WebSetup\wsus3setup.inf
    2007-07-01 14:10:12:750 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version
    = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version
    = 7.0.6000.374
    2007-07-01 14:10:12:765 2324 850 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required
    version = 7.0.6000.374
    It looks to me like some updates are not required now, but others are still
    failing.
    I also sent a message to Microsoft about the problem, don't know how long
    they have to respond.
    I had to reinstall windows a couple months ago and used the CD that came
    with the computer, so that version was probably from 2001 or 2002. It looks
    like the updates have been failing since then. The BITS has been set to
    automatic and is started.
    --
    Roger A.


    "PA Bear" wrote:

    > 1. First install the newly released 'standalone' version of Windows Update
    > Agent 3.0, v7.0.6000.374
    > http://support.microsoft.com/kb/932494
    >
    > 2. Now (re)install this (updated) fix:
    > http://support.microsoft.com/kb/927891
    >
    > NB: Windows Update/Automatic Updates started offering 927891 on 22 May-07.
    > If "Update for Windows XP (KB927891)" is listed in Add/Remove Programs (make
    > sure Show Updates box is checked), it's already installed. cf.
    > http://www.microsoft.com/technet/sec...ry/927891.mspx
    >
    > 3. Reboot.
    > --
    > ~Robear Dyer (PA Bear)
    > MS MVP-Windows (IE, OE, Security, Shell/User)
    > AumHa VSOP & Admin; DTS-L.org
    >
    >
    > DustDevil_007 wrote:
    > > some recent entries in the windowsupdate.log are reproduced below..
    > >
    > > 2007-06-30 18:14:57:859 1068 710 EEHndlr FATAL: MSI DLL version is 3.0.
    > > Version 3.1 is required.
    > > 2007-06-30 18:14:57:859 1068 710 Agent WARNING: Failed to evaluate
    > > Installed
    > > rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr = 80241001
    > > 2007-06-30 18:15:00:312 1068 710 Handler Attempting to create remote
    > > handler
    > > process as ARMSTRON-8DFD60\Owner in session 0
    > > 2007-06-30 18:15:00:671 1628 ecc Misc =========== Logging initialized
    > > (build: 7.0.6000.374, tz: -0500) ===========
    > > 2007-06-30 18:15:00:671 1628 ecc Misc = Process:
    > > C:\WINDOWS\system32\wuauclt.exe
    > > 2007-06-30 18:15:00:671 1628 ecc AUClnt FATAL: Error: 0x80004002. wuauclt
    > > handler: failed to spawn COM server
    > > 2007-06-30 18:15:02:078 1068 710 Handler FATAL: 0x80004002: ERROR: Remote
    > > update handler container process created (PID: 1628), but exited before
    > > signaling event
    > > 2007-06-30 18:15:02:078 1068 710 Agent * WARNING: Exit code = 0x80004002
    > > 2007-06-30 18:15:02:078 1068 710 Agent *********
    > > 2007-06-30 18:15:02:078 1068 710 Agent ** END ** Agent: Installing
    > > updates [CallerId = MicrosoftUpdate]
    > > 2007-06-30 18:15:02:078 1068 710 Agent *************
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI >>-- RESUMED -- COMAPI: Install
    > > [ClientId = MicrosoftUpdate]
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI - Install call failed
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI - Reboot required = No
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI - WARNING: Exit code =
    > > 0x80240FFF;
    > > Call error code = 0x80004002
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI ---------
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI -- END -- COMAPI: Install
    > > [ClientId = MicrosoftUpdate]
    > > 2007-06-30 18:15:02:078 3560 728 COMAPI -------------
    > > 2007-06-30 18:15:02:078 1068 710 Agent WARNING: WU client failed
    > > installing
    > > updates with error 0x80004002
    > > 2007-06-30 18:15:02:843 3560 85c COMAPI WARNING: Operation failed due to
    > > earlier error, hr=80004002
    > >
    > > Error code looks to be 0x80004002
    > >
    > >> We need some more information -
    > >>
    > >> On the WU Website, select your history of updates - now click on failed
    > >> update (red mark) and see if there is an error code.
    > >> If there is an error code, write it down and post back or in the
    > >> alternative, do a search for the error code.
    > >>
    > >> Also - how to view the Update log in Windows:-
    > >>
    > >> Click Start, and then click Run.
    > >> In the Open box, type: %windir%\windowsupdate.log
    > >> and then click OK.
    > >>
    > >> Scroll down towards the bottom for the latest entries to locate the error
    > >> code(s) associated with the latest failed attempt to download/install. If
    > >> appropriate copy and paste the error codes into this thread so someone
    > >> may
    > >> be able to assist you. On the other hand, you may be able to find the
    > >> error code and other suggestions by searching the Newsgroup.
    > >>
    > >> Also check Windows folder for file called KB******.log (****** = number
    > >> of
    > >> update ie KB896688) and post the contents of the failed update.
    > >> This may provide further clues as to why the update failed.
    > >>
    > >> How to read the Windowsupdate.log file:
    > >> http://support.microsoft.com/?kbid=902093
    > >>
    > >> You cannot install updates that you download from the Windows Update Web
    > >> site on a Windows XP-based computer
    > >> http://support.microsoft.com/?kbid=934648
    > >>
    > >> "DustDevil_007" <[email protected]> wrote in message
    > >> news:[email protected]...
    > >>> Keep trying to install updates and above installer 3.1 will not install.
    > >>> Auto update is turned on. Yesterday there were several updates not
    > >>> installed. Today, I just get the one message about the MS Win installer
    > >>> 3.1. The shield remains in the taskbar advising me that updates are
    > >>> ready
    > >>> to be installed, but I keep getting the same response. Any thoughts on
    > >>> this?? --
    > >>> Roger A.

    >
    >


  7. #7
    PA Bear Guest

    Re: Microsoft Windows Installer 3.1 will not install

    Thread history:
    http://groups.google.com/group/micro...d3cd13e462dd40

    Your problem now isn't installing MS Windows Installer 3.1 and Windows
    Update Agent version is current.

    Have you tried TauArian's recommendation?...

    <QP>
    [1.] Click Start, select run and type the following (pressing okay after
    each one):-

    net.exe stop wuauserv

    regsvr32 wuapi.dll
    regsvr32 wups.dll
    regsvr32 wuaueng.dll
    regsvr32 wucltui.dll
    regsvr32 MSXML3.dll

    net.exe start wuauserv

    [2.] Try WU again.
    </QP>

    If still no joy, open a free Support Incident. Customers in the U.S. and
    Canada can receive technical support from Microsoft Product Support Services
    at 1-866-PCSAFETY. There is no-charge for support calls that are associated
    with security updates. When you call, clearly state that your problem is
    related to a Security Update and cite the update's KB number (e.g.,
    KB931678).

    In other countries, see http://support.microsoft.com/security > "No-Charge
    Support...for virus and other security-related" issues in right-hand menu
    for localized contact information.

    For more information about how to contact Microsoft for support issues,
    visit the International Support Web site:
    https://support.microsoft.com/common/international.aspx
    --
    ~PA Bear

    DustDevil_007 wrote:
    > I checked which version I had of the MSI, and it was 3.1.4000.4039. I
    > have
    > tried every suggestion that was given, except to reinstall the ActiveX
    > compents, which I don't know how to do. At last check, I have 74 security
    > and other updates to install, but they fail to install every time. Here is
    > latest entries from windowsupdate.log
    > 007-07-01 13:43:01:703 1068 f00 Agent *
    > {C2367B85-F734-481B-967E-6C8B6F4FEBA1}.101
    > 2007-07-01 13:43:01:703 1068 f00 Agent * Title = Security Update for
    > Windows XP (KB935839)
    > 2007-07-01 13:43:01:703 1068 f00 Agent * UpdateId =
    > {E2E1C013-B99A-4683-921C-B99663F3F8ED}.103
    > 2007-07-01 13:43:01:703 1068 f00 Agent * Bundles 1 updates:
    > 2007-07-01 13:43:01:703 1068 f00 Agent *
    > {6E945291-FDE4-45E9-BA16-4A6B11411772}.103
    > 2007-07-01 13:43:05:968 1068 f00 Handler Attempting to create remote
    > handler
    > process as ARMSTRON-8DFD60\Owner in session 0
    > 2007-07-01 13:43:06:250 3856 f14 Misc =========== Logging initialized
    > (build: 7.0.6000.374, tz: -0500) ===========
    > 2007-07-01 13:43:06:250 3856 f14 Misc = Process:
    > C:\WINDOWS\system32\wuauclt.exe
    > 2007-07-01 13:43:06:250 3856 f14 AUClnt FATAL: Error: 0x80004002. wuauclt
    > handler: failed to spawn COM server
    > 2007-07-01 13:43:07:125 1068 f00 Handler FATAL: 0x80004002: ERROR: Remote
    > update handler container process created (PID: 3856), but exited before
    > signaling event
    > 2007-07-01 13:43:07:250 1068 f00 Agent * WARNING: Exit code = 0x80004002
    > 2007-07-01 13:43:07:250 1068 f00 Agent *********
    > 2007-07-01 13:43:07:250 1068 f00 Agent ** END ** Agent: Installing
    > updates [CallerId = MicrosoftUpdate]
    > 2007-07-01 13:43:07:250 1068 f00 Agent *************
    > 2007-07-01 13:43:07:250 1068 f00 Agent WARNING: WU client failed
    > installing
    > updates with error 0x80004002
    > 2007-07-01 13:43:07:562 3536 dec COMAPI >>-- RESUMED -- COMAPI: Install
    > [ClientId = MicrosoftUpdate]
    > 2007-07-01 13:43:07:562 3536 dec COMAPI - Install call failed
    > 2007-07-01 13:43:07:562 3536 dec COMAPI - Reboot required = No
    > 2007-07-01 13:43:07:562 3536 dec COMAPI - WARNING: Exit code =
    > 0x80240FFF;
    > Call error code = 0x80004002
    > 2007-07-01 13:43:07:562 3536 dec COMAPI ---------
    > 2007-07-01 13:43:07:562 3536 dec COMAPI -- END -- COMAPI: Install
    > [ClientId = MicrosoftUpdate]
    > 2007-07-01 13:43:07:562 3536 dec COMAPI -------------
    > 2007-07-01 13:43:08:328 3536 dd4 COMAPI WARNING: Operation failed due to
    > earlier error, hr=80004002

    <snip>
    > 2007-07-01 14:10:11:968 2324 850 Setup Update NOT required for
    > C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required
    > version = 7.0.6000.374
    > 2007-07-01 14:10:11:968 2324 850 Setup * IsUpdateRequired = No

    <snip>
    > It looks to me like some updates are not required now, but others are
    > still
    > failing.
    > I also sent a message to Microsoft about the problem, don't know how long
    > they have to respond.
    > I had to reinstall windows a couple months ago and used the CD that came
    > with the computer, so that version was probably from 2001 or 2002. It
    > looks
    > like the updates have been failing since then. The BITS has been set to
    > automatic and is started.
    >
    >> 1. First install the newly released 'standalone' version of Windows
    >> Update
    >> Agent 3.0, v7.0.6000.374
    >> http://support.microsoft.com/kb/932494
    >>
    >> 2. Now (re)install this (updated) fix:
    >> http://support.microsoft.com/kb/927891
    >>
    >> NB: Windows Update/Automatic Updates started offering 927891 on 22
    >> May-07.
    >> If "Update for Windows XP (KB927891)" is listed in Add/Remove Programs
    >> (make sure Show Updates box is checked), it's already installed. cf.
    >> http://www.microsoft.com/technet/sec...ry/927891.mspx
    >>
    >> 3. Reboot.
    >> --
    >> ~Robear Dyer (PA Bear)
    >> MS MVP-Windows (IE, OE, Security, Shell/User)
    >> AumHa VSOP & Admin; DTS-L.org
    >>
    >>
    >> DustDevil_007 wrote:
    >>> some recent entries in the windowsupdate.log are reproduced below..
    >>>
    >>> 2007-06-30 18:14:57:859 1068 710 EEHndlr FATAL: MSI DLL version is 3.0.
    >>> Version 3.1 is required.
    >>> 2007-06-30 18:14:57:859 1068 710 Agent WARNING: Failed to evaluate
    >>> Installed
    >>> rule, updateId = {B627A8FF-19CD-45F5-A938-32879DD90123}.100, hr =
    >>> 80241001
    >>> 2007-06-30 18:15:00:312 1068 710 Handler Attempting to create remote
    >>> handler
    >>> process as ARMSTRON-8DFD60\Owner in session 0
    >>> 2007-06-30 18:15:00:671 1628 ecc Misc =========== Logging initialized
    >>> (build: 7.0.6000.374, tz: -0500) ===========
    >>> 2007-06-30 18:15:00:671 1628 ecc Misc = Process:
    >>> C:\WINDOWS\system32\wuauclt.exe
    >>> 2007-06-30 18:15:00:671 1628 ecc AUClnt FATAL: Error: 0x80004002.
    >>> wuauclt
    >>> handler: failed to spawn COM server
    >>> 2007-06-30 18:15:02:078 1068 710 Handler FATAL: 0x80004002: ERROR:
    >>> Remote
    >>> update handler container process created (PID: 1628), but exited before
    >>> signaling event
    >>> 2007-06-30 18:15:02:078 1068 710 Agent * WARNING: Exit code =
    >>> 0x80004002
    >>> 2007-06-30 18:15:02:078 1068 710 Agent *********
    >>> 2007-06-30 18:15:02:078 1068 710 Agent ** END ** Agent: Installing
    >>> updates [CallerId = MicrosoftUpdate]
    >>> 2007-06-30 18:15:02:078 1068 710 Agent *************
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI >>-- RESUMED -- COMAPI:
    >>> Install
    >>> [ClientId = MicrosoftUpdate]
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI - Install call failed
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI - Reboot required = No
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI - WARNING: Exit code =
    >>> 0x80240FFF;
    >>> Call error code = 0x80004002
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI ---------
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI -- END -- COMAPI: Install
    >>> [ClientId = MicrosoftUpdate]
    >>> 2007-06-30 18:15:02:078 3560 728 COMAPI -------------
    >>> 2007-06-30 18:15:02:078 1068 710 Agent WARNING: WU client failed
    >>> installing
    >>> updates with error 0x80004002
    >>> 2007-06-30 18:15:02:843 3560 85c COMAPI WARNING: Operation failed due to
    >>> earlier error, hr=80004002
    >>>
    >>> Error code looks to be 0x80004002
    >>>
    >>>> We need some more information -
    >>>>
    >>>> On the WU Website, select your history of updates - now click on failed
    >>>> update (red mark) and see if there is an error code.
    >>>> If there is an error code, write it down and post back or in the
    >>>> alternative, do a search for the error code.
    >>>>
    >>>> Also - how to view the Update log in Windows:-
    >>>>
    >>>> Click Start, and then click Run.
    >>>> In the Open box, type: %windir%\windowsupdate.log
    >>>> and then click OK.
    >>>>
    >>>> Scroll down towards the bottom for the latest entries to locate the
    >>>> error
    >>>> code(s) associated with the latest failed attempt to download/install.
    >>>> If
    >>>> appropriate copy and paste the error codes into this thread so someone
    >>>> may
    >>>> be able to assist you. On the other hand, you may be able to find the
    >>>> error code and other suggestions by searching the Newsgroup.
    >>>>
    >>>> Also check Windows folder for file called KB******.log (****** = number
    >>>> of
    >>>> update ie KB896688) and post the contents of the failed update.
    >>>> This may provide further clues as to why the update failed.
    >>>>
    >>>> How to read the Windowsupdate.log file:
    >>>> http://support.microsoft.com/?kbid=902093
    >>>>
    >>>> You cannot install updates that you download from the Windows Update
    >>>> Web
    >>>> site on a Windows XP-based computer
    >>>> http://support.microsoft.com/?kbid=934648
    >>>>
    >>>> "DustDevil_007" <[email protected]> wrote in
    >>>> message
    >>>> news:[email protected]...
    >>>>> Keep trying to install updates and above installer 3.1 will not
    >>>>> install.
    >>>>> Auto update is turned on. Yesterday there were several updates not
    >>>>> installed. Today, I just get the one message about the MS Win
    >>>>> installer
    >>>>> 3.1. The shield remains in the taskbar advising me that updates are
    >>>>> ready
    >>>>> to be installed, but I keep getting the same response. Any thoughts
    >>>>> on
    >>>>> this?? --
    >>>>> Roger A.



  8. #8
    Fede Guest

    RE: Microsoft Windows Installer 3.1 will not install



    DustDevil_007, I suggest running Dial-a-fix to repair Windows Update. It
    does miracles.
    http://wiki.djlizard.net/Dial-a-fix



  9. #9
    Join Date
    Jul 2007
    Posts
    1
    Hi
    Dustdevil isn't the only one with this problem - I have two pc's doing exactly the same thing with exactly the same results.
    I also have tried everything mentioned here and would dearly love a solution.
    Autoupdates fail every time. If i download and install each individual patch manually it works. (But who wants to do 72 patches manually...).

    Autoupdate appears to download the patches correctly and verifies them as well. However it refuses to install whatever it downloads and says the files all have 0 bytes size. The files it downloads are on the HDD and can be manually installed, but then that's missing the point...

    I've also tried reregistering the wu*.dll's, but (altho I've checked that the files are actually there and where they're supposed to be) it says I don't have the module I want to reregister...

    Suggestions?

    Thanks in advance
    Sledge

Similar Threads

  1. Microsoft Windows Installer 3.1 download fails
    By RussM in forum Windows Update
    Replies: 15
    Last Post: 13-02-2010, 09:44 PM
  2. Microsoft Windows Installer Clean Up Utility
    By SidharthGore in forum Windows XP Support
    Replies: 3
    Last Post: 25-01-2009, 04:04 AM
  3. Can't install Windows Installer 3.1
    By Sandy M in forum Windows Update
    Replies: 9
    Last Post: 02-01-2009, 03:49 AM
  4. Problem downloading Microsoft Windows Installer 3.1
    By Jaisal in forum Windows XP Support
    Replies: 1
    Last Post: 26-02-2008, 04:23 PM
  5. Microsoft Windows Installer 3.1
    By Polaris in forum Windows Update
    Replies: 6
    Last Post: 12-02-2008, 10:35 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,750,376,021.79139 seconds with 16 queries