Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
There are no prerequisites for installing this hotfix.
Restart information
You may have to restart the computer after you apply this hotfix.
File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name | File version | File size | Date | Time |
---|
Mf.dll | 12.0.7600.16506 | 3,177,472 | 18-Jan-2010 | 23:29 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:06 |
Mfpmp.exe | 12.0.7600.16385 | 23,040 | 14-Jul-2009 | 01:14 |
Mfps.dll | 12.0.7600.16385 | 103,424 | 14-Jul-2009 | 01:15 |
Rrinstaller.exe | 11.0.7600.16385 | 50,176 | 14-Jul-2009 | 01:14 |
Mf.dll | 12.0.7600.20621 | 3,179,008 | 19-Jan-2010 | 11:55 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:06 |
Mfpmp.exe | 12.0.7600.16385 | 23,040 | 14-Jul-2009 | 01:14 |
Mfps.dll | 12.0.7600.16385 | 103,424 | 14-Jul-2009 | 01:15 |
Rrinstaller.exe | 11.0.7600.16385 | 50,176 | 14-Jul-2009 | 01:14 |
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
Collapse this tableExpand this table
File name | File version | File size | Date | Time | Platform |
---|
Mf.dll | 12.0.7600.16506 | 4,062,720 | 19-Jan-2010 | 09:04 | x64 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:28 | x64 |
Mfpmp.exe | 12.0.7600.16385 | 24,576 | 14-Jul-2009 | 01:39 | x64 |
Mfps.dll | 12.0.7600.16506 | 206,848 | 19-Jan-2010 | 09:04 | x64 |
Rrinstaller.exe | 11.0.7600.16385 | 55,808 | 14-Jul-2009 | 01:39 | x64 |
Mf.dll | 12.0.7600.20621 | 4,064,256 | 19-Jan-2010 | 10:28 | x64 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:28 | x64 |
Mfpmp.exe | 12.0.7600.16385 | 24,576 | 14-Jul-2009 | 01:39 | x64 |
Mfps.dll | 12.0.7600.20621 | 206,848 | 19-Jan-2010 | 10:28 | x64 |
Rrinstaller.exe | 11.0.7600.16385 | 55,808 | 14-Jul-2009 | 01:39 | x64 |
Mf.dll | 12.0.7600.16506 | 3,177,472 | 18-Jan-2010 | 23:29 | x86 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:06 | x86 |
Mfpmp.exe | 12.0.7600.16385 | 23,040 | 14-Jul-2009 | 01:14 | x86 |
Mfps.dll | 12.0.7600.16385 | 103,424 | 14-Jul-2009 | 01:15 | x86 |
Rrinstaller.exe | 11.0.7600.16385 | 50,176 | 14-Jul-2009 | 01:14 | x86 |
Mf.dll | 12.0.7600.20621 | 3,179,008 | 19-Jan-2010 | 11:55 | x86 |
Mferror.dll | 12.0.7600.16385 | 2,048 | 14-Jul-2009 | 01:06 | x86 |
Mfpmp.exe | 12.0.7600.16385 | 23,040 | 14-Jul-2009 | 01:14 | x86 |
Mfps.dll | 12.0.7600.16385 | 103,424 | 14-Jul-2009 | 01:15 | x86 |
Rrinstaller.exe | 11.0.7600.16385 | 50,176 | 14-Jul-2009 | 01:14 | x86 |
Additional notes
The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are
listed separately. 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 (attributes not listed) are signed with a Microsoft digital signature.