I changed DWORD value but programs still freeze

M

Msch

I added the new DWORD value and set it to 1 according to the instructions on
the link posted by "Bob I", however, my MicroSoft Office products still lock
up after I go to File - Open. The box pops up, but it freezes up when I try
to open a sub-folder to find the file I need. I do not have this problem in
non-MicroSoft programs that I run.

Also, "Mary Sauer" has posted a quick fix link, however, my computer can't
find the website she lists with "kellys-korner..." I click on it and get "Web
site not found".
 
G

garfield-n-odie [MVP]

The http://support.microsoft.com/kb/918165 registry modification
works for most people, but a few users have reported that it does
not fix the problem for them. Two other workarounds are to either:
1. Rename the VERCLSID.EXE file to VERCLSID.OLD. This
effectively disables the http://support.microsoft.com/kb/908531
(MS06-015) update, but does not uninstall the update. Renaming
the VERCLSID.EXE file will leave your system unprotected against
the issue described at
http://www.microsoft.com/technet/security/bulletin/ms06-015.mspx
..
2. Uninstall the http://support.microsoft.com/kb/908531
(MS06-015) update from Start | Control Panel | Add or Remove
Programs. If automatic updates are enabled on your computer,
then the update may be reinstalled automatically. Uninstalling
the MS06-015 update will leave your system unprotected against
the issue described at
http://www.microsoft.com/technet/security/bulletin/ms06-015.mspx
..
 
M

Msch

After some more trouble shooting I have been told that I am one of the few
users that is not helped by the registry modification. Since I was nervous
about being unprotected by disabling the verclsid.exe file MicroSoft
Technicians are supposed to call me back regarging this problem. Until then I
just have to work around it.
 
M

Msch

This link to the kellys-korner website worked for me. Unfortunately, the
patch didn't. I finally called MicroSoft for Technical support and found that
I am one of the few users that the registry fix does not help. Another
MicroSoft Technical support representative is supposed to call me back later
this week regarding this problem.
 
Top