Document.7\ShellEx\{BB2E617C-0920-11D1-9A0B-
00C04FC2D6C1}
HKEY_CLASSES_ROOT\SystemFileAssociations\.pdf\ShellEx\IconHandler
HKEY_CLASSES_ROOT\SystemFileAssociations\.pdf\ShellEx\{BB2E617C-0920-11D1-
9A0B-00C04FC2D6C1}
HKEY_CLASSES_ROOT\SystemFileAssociations\image\ShellEx\IconHandler
HKEY_CLASSES_ROOT\SystemFileAssociations\image\ShellEx\{BB2E617C-0920-11D1-
9A0B-00C04FC2D6C1}
File Type Associations | 129
The Registry
As it turns out, Adobe chose the fourth key to register its IconHandler. The
(Default) value in that key contains a 38-digit class ID that points to an
entry in HKEY_CLASSES_ROOT\CLSID, which in turn contains all the details
about the .dll file.
If the reference to the IconHandler is contained in one of the
keys named IconHandler, the .dll is responsible for the
dynamically generated icon. But newer programs will use the
{BB2E617C-0920-11d1-9A0B-00C04FC2D6C1} key, which facilitates
image previews for the Preview pane in Windows
Explorer, as well as dynamic icons. See ???Expand the Scope
of Your File Types,??? later in this chapter, for more information
on the SystemFileAssociations key.
Once you find the reference to the IconHandler, you can delete the key??”
either the IconHandler key or the {BB2E617C-0920-11d1-9A0B-00C04FC2D6C1}
key??”to disable the IconHandler and allow Windows Explorer to use the
static icon defined in the DefaultIcon key.
Figure 3-13. If an IconHandler is defined for a file type, Windows generates icons
dynamically for each file instead of using the static icon referenced in the DefaultIcon key
130 | Chapter 3: The Registry
But what if you want to fix a broken file type for which icon previews have
stopped working? Often it??™s easier to just reinstall the associated application
to repair the IconHandler keys, but if that application is Windows itself,
then you??™ll probably want to follow these steps to reinstate icon previews on
your PC:
1.
Pages:
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200