System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows
(http://windows.microsoft.com/en-us/windows/help/end-support-windows-xp-sp2-windows-vista-without-service-packs)
.
How to obtain help and support for this security update
For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support website:
North American customers can also obtain instant access to unlimited no-charge email support or to unlimited individual chat support by visiting the following Microsoft website:
Note We do not recommend that you use of this Fix it now that the security bulletin MS10-46 is available. We strongly recommend that customers deploy the security update instead. However, the Fix It remains available so that customers can deploy it in situations where the security update cannot be immediately installed and so that they can undo the Fix It after they install the security update.
To implement the workaround that disables .lnk and .pif file functionality automatically on a computer that is running Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server R2, click the Fix this problem link under Enable workaround. To undo the workaround, click the Fix this problem link under Disable workaround. In either scenario, click Run in the File Download dialog box, and follow the steps in the Fix it Wizard.
Note After you apply the Fix it, you must restart the computer. After the installation of the Fix it, the user is prompted before the system is restarted. Enterprise deployments allow for unattended install with the following Display options:
Collapse this tableExpand this table
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f] Sets user interface level
n - No UI b - Basic UI r - Reduced UI f - Full UI (default)
Restart Options:
Collapse this tableExpand this table
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Note Applying the Fix it removes the graphical representation of icons on the Task bar and Start menu bar and replaces them with white icons that do not have the graphical representation of the icon.
Before you apply the Fix it, the icons on the desktop appear as follows:
Collapse this imageExpand this image
After you apply the Fix it, the icons appear on the task bar as follows:
Collapse this imageExpand this image
After you apply the Fix it, the icons appear on the Start menu bar as follows:
Note This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, save the Fix it solution to a flash drive or to a CD, and then run it on the computer that has the problem.
To implement the workaround that disables .lnk and .pif file functionality yourself, use one of the following methods.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756
(http://support.microsoft.com/kb/322756)
How to back up and restore the registry in Windows
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then select the following registry key:
HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler
Click the File menu, and then click Export.
In the Export Registry File dialog box, type LNK_Icon_Backup.reg and then click Save. Note This step creates a backup of this registry key in the My Documents folder by default.
Select the value (Default) on the right pane in Registry Editor. Press ENTER to edit the value of the key. Delete the value so that the value is blank, and then press ENTER.
Locate and then select the following registry key:
HKEY_CLASSES_ROOT\piffile\shellex\IconHandler
Click the File menu, and then click Export.
In the Export Registry File dialog box, type PIF_Icon_Backup.reg, and then click Save. Note This step creates a backup of this registry key in the My Documents folder by default.
Select the value (Default) on the right pane in Registry Editor. Press ENTER to edit the value of the key. Delete the value so that the value is blank, and then press ENTER.
Impact of the workaround
Some icons will no longer show a graphical representation and will resemble the following:
Check whether the registry key is created or modified. If the registry key is created or modified, you are finished with this article. If the registry key is not created or modified, you can contact support
(http://www.microsoft.com/protect/support/default.mspx)
.
The English (United States) version of this security update uses a Microsoft Windows Installer package to install the security update. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP and Windows Server 2003 file information
The files that apply to a specific milestone (RTM, SPn) and service branch (QFE, GDR) are noted in the "SP requirement" and "Service branch" columns.
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KB number .cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows XP
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Shell32.dll
6.0.2900.6018
8,462,336
27-Jul-2010
06:30
x86
SP3
GDR
Shell32.dll
6.0.2900.6018
8,463,360
27-Jul-2010
06:28
x86
SP3
QFE
Updspapi.dll
6.3.13.0
382,840
22-Feb-2010
14:23
x86
None
Not Applicable
For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Shell32.dll
6.0.3790.4751
10,510,336
27-Jul-2010
19:11
x64
SP2
GDR
Wshell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
19:11
x86
SP2
GDR\WOW
Shell32.dll
6.0.3790.4751
10,510,848
27-Jul-2010
19:06
x64
SP2
QFE
Wshell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
19:06
x86
SP2
QFE\WOW
Updspapi.dll
6.3.4.1
462,128
27-Jul-2010
19:16
x64
None
Not Applicable
For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Shell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
06:25
x86
SP2
GDR
Shell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
06:29
x86
SP2
QFE
Updspapi.dll
6.3.4.1
379,184
16-Apr-2010
12:15
x86
None
Not Applicable
For all supported IA-64-based versions of Windows Server 2003
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Shell32.dll
6.0.3790.4751
13,248,000
27-Jul-2010
19:11
IA-64
SP2
GDR
Wshell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
19:11
x86
SP2
GDR\WOW
Shell32.dll
6.0.3790.4751
13,249,024
27-Jul-2010
19:06
IA-64
SP2
QFE
Wshell32.dll
6.0.3790.4751
8,361,984
27-Jul-2010
19:06
x86
SP2
QFE\WOW
Updspapi.dll
6.3.4.1
655,152
27-Jul-2010
19:16
IA-64
None
Not Applicable
Windows Vista and Windows Server 2008 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.0.6000.16xxx
Windows Vista
RTM
GDR
6.0.6000.20xxx
Windows Vista
RTM
LDR
6.0.6001.18xxx
Windows Vista SP1 and Windows Server 2008 SP1
SP1
GDR
6.0.6001.22xxx
Windows Vista SP1 and Windows Server 2008 SP1
SP1
LDR
6.0.6002.18xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
GDR
6.0.6002.22xxx
Windows Vista SP2 and Windows Server 2008 SP2
SP2
LDR
Service Pack 1 is integrated into the original release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Shell32.dll
6.0.6001.18505
11,581,440
26-Jul-2010
16:55
x86
Shell32.dll
6.0.6001.22735
11,586,560
26-Jul-2010
16:56
x86
Shell32.dll
6.0.6002.18287
11,584,512
26-Jul-2010
15:51
x86
Shell32.dll
6.0.6002.22454
11,587,072
26-Jul-2010
18:04
x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Shell32.dll
6.0.6001.18505
12,898,304
26-Jul-2010
15:31
x64
Shell32.dll
6.0.6001.22735
12,904,448
26-Jul-2010
17:08
x64
Shell32.dll
6.0.6002.18287
12,898,816
26-Jul-2010
16:16
x64
Shell32.dll
6.0.6002.22454
12,901,376
26-Jul-2010
18:14
x64
Shell32.dll
6.0.6001.18505
11,581,440
26-Jul-2010
16:55
x86
Shell32.dll
6.0.6001.22735
11,586,560
26-Jul-2010
16:56
x86
Shell32.dll
6.0.6002.18287
11,584,512
26-Jul-2010
15:51
x86
Shell32.dll
6.0.6002.22454
11,587,072
26-Jul-2010
18:04
x86
For all supported IA-64-based versions of Windows Server 2008
Windows 7 and Windows Server 2008 R2 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.7600.16xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.7600.20xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Shell32.dll
6.1.7600.16644
12,867,584
27-Jul-2010
14:03
x86
Shell32.dll
6.1.7600.20765
12,869,120
27-Jul-2010
13:59
x86
For all supported x64-based versions of Windows Server 2008 R2 and of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Shell32.dll
6.1.7600.16644
14,162,944
27-Jul-2010
14:59
x64
Shell32.dll
6.1.7600.20765
14,167,552
27-Jul-2010
14:42
x64
Shell32.dll
6.1.7600.16644
12,867,584
27-Jul-2010
14:03
x86
Shell32.dll
6.1.7600.20765
12,869,120
27-Jul-2010
13:59
x86
For all supported IA-64-based versions of Windows Server 2008 R2