Friday, April 21, 2006 11:17 PM bart

When patching hurts ... more on MS06-015, KB918165, verclsid.exe and a non-responding Office suite

This evening a friend of mine pinged me on MSN about a problem, with the scary nickname "XYZ starting to hate the microsoft office suite". Apparently, Word (and other Office applications) stopped to respond when he tried to open or save a document through the File/Open or File/Save dialog, navigating through the folder hierarchy.

So I suggested to open a remote assistance session to take a look at it. Some KB articles later without a solution I decided to download RegMon from SysInternals on his pc (download here), entered a filter for winword.exe and started to capture events. Jumped back to Word to do File, Open and clicked on some folder causing Word to hang and (after > 9000 registry events) RegMon to stop capturing events. And there it was, the latest registry read operation telling something about verclsid.exe. What's next? The KB at happened to be the solution, pointing me to KB article 918165, released to the web one day ago.

When I saw this KB article, I knew it was the latest Microsoft Update patch cycle that caused the problem, more specifically the MS06-015 patch that conflicts with HP Share-to-Web which was installed on the machine. Some quotes from the KB article:

Microsoft Office applications stop responding when you try to save or to open Office files in the "My Documents" folder.

There have been reported issues where software that was previously distributed by Hewlett Packard (HP) causes the Verclsid.exe program to stop responding. The specific component that causes problems is the Share-to-Web namespace daemon (Hpgs2wnd.exe). This software is no longer distributed by HP ...

Security update 908531 includes an "allow list." The Verclsid.exe program does not scan any file that has an extension that appears in this list. ... To resolve this problem, you can add the HP shell extension to the list. To you do this, you must follow these steps to modify the registry ...

So, check out the KB article for instructions on how to resolve this issue. | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Filed under: ,


No Comments