CiceroUIWndFrame

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

For the last couple of years, I have the now popular shutdown hang caused by
CiceroUIWndFrame. For the last couple of years, I keep reading the
"solution". All of them agree that it is caused by a bug in MS Office related
to "Speech and Handwriting Recognition" part of Office XP. The consistent
solution is to de-install it, go to
"Control Panel"
"Add/Remove Programs"
"Microsoft Office," click on the "Change" button
browse to "Office Shared Features," "Alternative User Input," and select for
Speech and Handwriting Recognition (both) "Not available" from the drop-down
box.

Perform the change and the CiceroUIWndFrame messages disappear.

I keep following the solutions and within a few weeks I am back to where I
was.
I found a suggestion to use the Repair and I did it and I am still on the
same boat.
What else uses Cicero.... there most be other reasons to hang the shutdowns.
I am now keeping the system idle for half hour before going thru the shutdonw
procedure. That seems to do the job but I suspect there are other causes.

Anybody has other suggestions?
 
Have you updated your version of Office XP to the latest SP-3?
http://support.microsoft.com/kb/307841/

Some have reported that installing MDAC 2.8 fixes it, others not:
http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en
After installing this, run Windows Update to check for any security patches
for this.

You may have to also search within the Office individual products to turn
off that "feature":
http://www.attention-to-details.com/newslog/391-remove-cicerouiwndframe-to-avoid-crashes.asp#c307390
(Visio, FrontPage, Project, etc.)

See this article and do everything it says to stop the process ctfmon.exe
from running:

Frequently asked questions about Ctfmon.exe
http://support.microsoft.com/kb/282599 - see the "Note" bit under Step1,
then do Step 2 and Step 3.
 
Back
Top