{"id":323,"date":"2009-05-12T00:20:03","date_gmt":"2009-05-11T16:20:03","guid":{"rendered":"http:\/\/www.jhouseconsulting.com\/?p=323"},"modified":"2009-05-12T10:41:03","modified_gmt":"2009-05-12T02:41:03","slug":"http-default-icon-issue","status":"publish","type":"post","link":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/2009\/05\/12\/http-default-icon-issue-323","title":{"rendered":"HTTP Default Icon issue"},"content":{"rendered":"

Sometimes you may find that the HTTP URL shortcut icon is “broken”; referencing %SystemRoot%\\system32\\SHELL32.dll,0 instead of %SystemRoot%\\system32\\url.dll,0. This is due to a bug that does not consistently set the default type and data for the HKEY_CLASSES_ROOT\\HTTP\\DefaultIcon value. When the icons are not displaying correctly, it will have a default value of type REG_SZ with Data “%1” when it should be of type REG_EXPAND_SZ with Data “%SystemRoot%\\system32\\url.dll,0”. Strangely, the DefaultIcon for the HTTPS (HKEY_CLASSES_ROOT\\HTTPS\\DefaultIcon) URL shortcut does not suffer from the same problem. I hope you find this information of value.<\/p>\n

\"Incorrect<\/a>
Incorrect registry entry<\/figcaption><\/figure>\n
\"Icon<\/a>
Icon displayed incorrectly in Internet Explorer 6<\/figcaption><\/figure>\n
\"Icon<\/a>
Icon for URL shortcut displayed incorrectly<\/figcaption><\/figure>\n
This registry setting will fix the DefaultIcon for the HTTP URL.<\/div>\n
\n
\"Correct<\/a>
Correct registry entry<\/figcaption><\/figure>\n<\/div>\n
\"Icon<\/a>
Icon displayed correctly in Internet Explorer 6<\/figcaption><\/figure>\n
\"Icon<\/a>
Icon for URL shortcut displayed correctly<\/figcaption><\/figure>\n

How to fix this?
\n<\/strong>
\nUse a registry import…<\/p>\n

Windows Registry Editor Version 5.00
\n[HKEY_CLASSES_ROOT\\http\\DefaultIcon]
\n@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\\
\n 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,75,00,72,00,\\
\n 6c,00,2e,00,64,00,6c,00,6c,00,2c,00,30,00,00,00<\/code><\/p>\n

…or an ADM template…<\/p>\n

CLASS MACHINE
\n CATEGORY \"MACHINE Custom Settings\"
\n Policy \"Fix the DefaultIcon for HTTP URL's\"
\n Explain \"This registry setting will fix the DefaultIcon for HTTP URL's so that they display correctly. More Information: Sometimes you find that the ICON for HTTP URL shortcuts have a broken icon that references %SystemRoot%\\system32\\SHELL32.dll,0 instead of %SystemRoot%\\system32\\url.dll,0. This is due to a bug that does not consistently set the default type and data for the HKEY_CLASSES_ROOT\\HTTP\\DefaultIcon value. When the icons are not displaying correctly, it will have a default value of type REG_SZ with Data ''%1'' when it should be of type REG_EXPAND_SZ with Data ''%SystemRoot%\\system32\\url.dll,0''\"
\n KEYNAME \"SOFTWARE\\Classes\\HTTP\\DefaultIcon\"
\n PART \"Enter the Default Icon location\" EDITTEXT EXPANDABLETEXT
\n DEFAULT \"%SystemRoot%\\system32\\url.dll,0\"
\n VALUENAME \"\"
\n END PART
\n END POLICY
\n END CATEGORY<\/code><\/p>\n

The following screenshot shows the policy setting once the ADM has been added to the Group Policy Object.<\/p>\n

\"Custom<\/a>
Custom Group Policy Setting<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

Sometimes you may find that the HTTP URL shortcut icon is “broken”; referencing %SystemRoot%\\system32\\SHELL32.dll,0 instead of %SystemRoot%\\system32\\url.dll,0. This is due to a bug that does not consistently set the default type and data for the HKEY_CLASSES_ROOT\\HTTP\\DefaultIcon value. When the icons are not displaying correctly, it will have a default value of type REG_SZ with Data … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[35,38],"tags":[142,141,143],"class_list":["post-323","post","type-post","status-publish","format-standard","hentry","category-os-tuning","category-xenapp","tag-default","tag-http","tag-icon"],"aioseo_notices":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/posts\/323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/comments?post=323"}],"version-history":[{"count":9,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/posts\/323\/revisions"}],"predecessor-version":[{"id":332,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/posts\/323\/revisions\/332"}],"wp:attachment":[{"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/media?parent=323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/categories?post=323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jhouseconsulting.com\/jhouseconsulting\/wp-json\/wp\/v2\/tags?post=323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}