Yep, as in the Subject. 72 was a typo
We did a SMS push of the KBs. The unloads and reloads fixed it and since we
have very few instances of MSAS running, it was not widespread. But removal
of the KB and MSAS fixed it. Reload of the KB worked. Now running the
newer version. Another set had the same issue with the same scenario.
Cannot get a repeat performance now.
"Bill Sanderson" <(E-Mail Removed)> wrote in message
news:7Bm$(E-Mail Removed)...
> This is KB867282, rather than 72.
>
> I have this in place on my system and don't see this issue, so I don't
think
> this is a simple incompatibility with the patch.
>
> Consider installing the new February 16th .509 build and re-checking the
> behavior?
> --
> FAQ for Microsoft Antispyware:
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "George Ellis" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > MS KB867272 (MS05-014) may have issues with MSAS. After installed and
> > restarted, IE will crash with a fault that includes the address
> > 0xcbe1e3ba,
> > Faulting module unknown (eventvwr info). Also seen was a crash blaming
> > msctf.dll at loc 0x00004172. Uninstalling MSAS and the KB, restart,
> > reinstall the KB fixes the issue.
> >
> >
> >
>
>