CiceroUIWndFrame Not Responding Error

Can you try and disable 'Office Quick Start' from startup? It loads the common files of MS Office when you start your PC to make it load faster, that might be causing the problem. You can do that by right-clicking on the quick start icon in system tray after your PC boots up or via MSconfig.

Alternatively, try looking in Windows Event Viewer by typing eventvwr in Start->Run and having a look at Application category. All things with red crosses are errors and have a look at the most recent red cross entry.

No Office Quick Start running at startup. That is the type of stuff I stay on top of and disable or remove if it is not needed to run at startup.

This event is not making any entry into the Application log.

Could you run a HijackThis log and post it here? we can analyse what is running in the background and what can cause the problem.

This is definitely an Outlook problem. When the Outlook.exe process is running, either in the foreground with the UI open or in the background to check for mail, the CiceroUIWndFrame Not Responding Error occurs when shutting down. When Outlook.exe is not running, the computer can be shutdown and the error does not occur.
For years I have been in the habit of shutting down the computer and letting the Windows shutdown process close any open programs, which usually includes Outlook since it is always open. Suddenly one day this errors starts occurring at shutdown. Probably an update of Windows or Office that triggered it.

I can shutdown Outlook, but sometime Outlook.exe is running in the background checking mail when I shutdown. Sure would be nice to fix it.

The "AVG Exchange Extension" add-in appears to be the cause. When it is off, no shutdown error. When it is on, shutdown error.

I am not sure if this is needed for e-mail malware scanning or not, or if it is a known issue. I am researching it right now.

Good, it seems we have zeroed in on the problem... let me know, what you find. I am thinking that on shutting down the machine this linked component is not unlinking itself from Outlook and that is possibly causing this message to appear.

I am in communication with AVG on the issue and will let you know what comes of it. Apparently this is not known issue.

You have answered my original question as far as what the cause is. Thanks for the help.

Good to know, that the problem has been found and I hope that AVG can devise a solution pretty quick. Thanks for the points.