1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

msiexec.exe runtime error - abnormal termination

Discussion in 'Windows XP' started by oserdavid, 2007/03/28.

  1. 2007/03/28
    oserdavid

    oserdavid Inactive Thread Starter

    Joined:
    2005/08/16
    Messages:
    216
    Likes Received:
    0
    Well, I may have got that title a bit mangled, but I'm sure some of you know what this is about.

    I've given up trying to instal the security updates for .Net Framework 1.1 - because they don't install. I've been all the way through the Microsoft procedure for uninstalling and reinstalling .Net Framework 1.1, including all the registry modifications, the deletions of files, etc, etc. One of the errors concerns msiexec. I've run msiexec /unregister and /regserver a few times to no avail.

    Now I've just tried to instal .Net Framework 3.0 (don't ask why, I'm not sure myself...) and it does at least get two thirds the way (by bar line) through the installation, when we get the error specifically concerning msiexec and runtime.

    Quite honestly I'm not all that concerned about .Net Framework - I've actually only come across a couple of programs that require it - and those only 1.1. I wish I could instal the security fixes for it, but 'tough s**t' I guess.

    However, I'm slightly more concerned about the state of my msiexec.exe - because I'm likely to need this in future for more important things... so, any ideas, experience? Anyone?
     
  2. 2007/03/28
    charlesvar

    charlesvar Inactive Alumni

    Joined:
    2002/02/18
    Messages:
    7,024
    Likes Received:
    0

  3. to hide this advert.

  4. 2007/03/29
    oserdavid

    oserdavid Inactive Thread Starter

    Joined:
    2005/08/16
    Messages:
    216
    Likes Received:
    0
    Thanks Charlesvar - but I'm afraid neither of those do it. I suspect I already had the latest Windows Installer, anyway - and reinstalling repaired nothing.

    I can, however report that the problems (so far) are only with .Net Framework 1.1 and 3.0. In the former case, updating with security patches/version and in the latter case initial installation.

    Microsoft appears to be aware of the problem with version 1.1 of .Net Framework, it's just that their solution does not work for me, although I tried following it to the letter...

    Tant pis...

    David
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.