Ever since installing VDT, on both my office machine and my home machine, Word 2003 no longer exits cleanly -- every time I try to quit, it crashes, popping up an annoying Microsoft Application Error Reporting (DW20.exe) dialog that refuses to go away, and locks up Explorer, until I hit "Send Error Report" or "Don't Send" -- only either way, the very next thing the stupid error reporter exec does, is launch another Word instance. Ugh. The only way out of this is to kill Word from the TaskManager (or from SysInternal's Process Explorer </shameless_plug>).
This only cropped up once I installed VDT, making me think VDT might be doing something interesting behind the scenes. Any ideas what's up?
Config: Office:
Win XP Japanese, Office 2003 English Home:
Win XP English (w/ Japanese fonts etc. installed), Office 2003 English All patches applied on both machines. VDT 2.72.3 on both.
This is probably due to the hook process that displays the sticky pin in the caption.
Can you try this: run the registry editor, go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\R2d2KernelAuthority\Parameters key, edit (or create if it doesn't exist yet) the _NeverSubClassPrograms REG_MULTI_SZ value and add *\WinWord.exe to the content (see the NeverSubClassPrograms value as a template).
Sorry for the delay in replying. It looks like that's done the trick.
R2D2 Confirms It -- Word 2003 Is Crufty -- Film at 11
Heh. So I guess the next issue is how to get Word to accept hooking without dying ungracefully when the application is quit. If this is even possible, of course...