This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
On a client computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP, an HTML file or an XML file that you archived to a secondary storage device may appear without an icon in Windows Explorer. This problem occurs if Microsoft Office XP, Microsoft Office 2003, or the 2007 Microsoft Office system is installed.
Microsoft Office installs one shell icon handler for the HTML file type and for the MHTML file type. Additionally, Microsoft Office installs another shell icon handler for the XML file type. Microsoft Office uses the shell icon handlers to display a different icon depending on the Microsoft Office application that created the file. The shell icon handlers read the file content to determine the Microsoft Office application that created the file. Then, the shell icon handlers return an icon that is based on this information for Windows Explorer to display. This process works well in most cases.
You may have archived the file to a secondary storage device by using Windows Remote Storage or by using a third-party remote storage system. In this case, the file content is not immediately available for the shell icon handlers to read without accessing the secondary storage device. Therefore, Windows Explorer examines the file for the Offline attribute. If the file contains the Offline attribute, Windows Explorer does not call the shell icon handlers. This behavior is designed to avoid the performance cost of a remote read and to avoid pulling the file back to the primary storage.
However, because of a problem in the shell, Windows Explorer does not display a generic icon for the file when Windows Explorer does not call the shell icon handlers. Therefore, a file that contains the Offline attribute appears without an icon if the file type is set to use a shell icon handler.
To resolve this problem, upgrade the operating system to Windows Vista.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this problem, use one of the following methods on the client computer.
These methods can restore the image for a remote file. However, these methods may have side effects for the remote storage system that you use. Additionally, these methods may require testing in the corporate environment before you use these methods widely.
Method 1: Apply a hotfix that lets Windows Explorer call the shell icon handlers even when the file is offline
On a computer that is running Windows XP with Service Pack 2 (SP2) or Windows XP with Service Pack 1 (SP1), apply hotfix 895115. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
895115 Windows Explorer does not display icons for .htm files, for .html files, or for .msg files after you enable offline files in Windows XP
Then, enable a policy that lets Windows Explorer call the shell icon handlers even when the file is offline. To enable the policy, follow these steps:
Under this registry key, create the PerInstanceIconHandlerForOffline registry entry of the DWORD type.
Set the value of the PerInstanceIconHandlerForOffline registry entry to 1.
Method 2: Change the registry keys to use static icon images
Change the registry keys that are associated with the HTML file type, with the MHTML file type, and with the XML file type. Make the registry keys use static icon images instead of using the shell icon handlers. To do this, follow these steps:
Create a new text file, and then paste the following information in the new text file.
Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT\htmlfile\DefaultIcon]@="C:\\Program Files\\Internet Explorer\\IEXPLORE.EXE,-32529"[HKEY_CLASSES_ROOT\mhtmlfile\DefaultIcon]@="C:\\Program Files\\Internet Explorer\\IEXPLORE.EXE,-32554"[HKEY_CLASSES_ROOT\xmlfile\DefaultIcon]@="msxml.dll,-128"[-HKEY_CLASSES_ROOT\htmlfile\ShellEx\IconHandler][-HKEY_CLASSES_ROOT\mhtmlfile\ShellEx\IconHandler][-HKEY_CLASSES_ROOT\xmlfile\ShellEx\IconHandler]
Save the new text file as the RestoreHandlerKeys.reg file. Make sure that you use the .reg extension so that the file is associated as a Windows registry script file.
Right-click the RestoreHandlerKeys.reg file, and then click Merge. If you receive a message that asks you to allow the merge, click Yes.
Note You may have to log off from the computer and then log on to the computer.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem does not harm the file or the file content. This problem is a display issue on a client computer that is running Windows Server 2003 or Windows XP.
Remote Storage is a part of Windows Server 2003 Enterprise Edition and of Windows Server 2003 Datacenter Edition. This problem is not specific to Remote Storage. However, this problem is an issue in Windows Explorer on a client computer that is running Windows Server 2003 or Windows XP if Remote Storage is in the network data center. For more information about Remote Storage, click the following article number to view the article in the Microsoft Knowledge Base:
816588 How to use Remote Storage in Windows Server 2003
Microsoft Windows XP Professional, Microsoft Windows XP Home Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Office Ultimate 2007, Microsoft Office Enterprise 2007, Microsoft Office Professional Plus 2007, Microsoft Office Professional 2007, Microsoft Office Small Business 2007, Microsoft Office Standard 2007