Windows Installer problems with WM5.1 - FAO Jonathan Kay

  • Thread starter Thread starter Daern's Instant Fortress
  • Start date Start date
D

Daern's Instant Fortress

It seems that several people (myself included) are having nightmare
problems with the latest WM5.1 upgrade from WM5.0. I'd love to pull this
patch from my AD, but recent security issues mean that I have to roll it
out, even if it sucks....and unfortunately, it does :-(

I've tried everything I can think of to resolve this issue, but so far
the only solution I've come up with that works is...
Msiexec /x {C3A6819F-62D3-4750-AF1C-28206DDF2C2E}
....followed by a reinstall of the software and, it appears, that
sometimes this doesn't work and requires an msiexec /f too :-(

We deploy this with AD so mucking about with scripts to fix it isn't my
idea of fun and anyway, it shouldn't screw up like this. I'm not even
sure what combination of software causes it to break, but even if it is
Acrobat (which is the most commonly reported problem), we've seen it
happening purely within Outlook 2003 (specifically with copy 'n' paste).

Jonathan, would it be possible for Microsoft to be made aware of the
pain that this is causing so that a fix / workaround could be developed?

Thanks

DIF
 
Daern's Instant Fortress said:
It seems that several people (myself included) are having nightmare
problems with the latest WM5.1 upgrade from WM5.0. I'd love to pull this
patch from my AD, but recent security issues mean that I have to roll it
out, even if it sucks....and unfortunately, it does :-(

I've tried everything I can think of to resolve this issue, but so far
the only solution I've come up with that works is...
Msiexec /x {C3A6819F-62D3-4750-AF1C-28206DDF2C2E}
...followed by a reinstall of the software and, it appears, that
sometimes this doesn't work and requires an msiexec /f too :-(

We deploy this with AD so mucking about with scripts to fix it isn't my
idea of fun and anyway, it shouldn't screw up like this. I'm not even
sure what combination of software causes it to break, but even if it is
Acrobat (which is the most commonly reported problem), we've seen it
happening purely within Outlook 2003 (specifically with copy 'n' paste).

Jonathan, would it be possible for Microsoft to be made aware of the
pain that this is causing so that a fix / workaround could be developed?

Thanks

DIF
Click to expand...

Just spoken with a chap at Microsoft. A bug has been identified and a
fix is in progress. Should be out next week...

DIF
 
Back
Top