If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.

On a computer that is running Windows 7 or Windows Server 2008 R2, you may receive an error message that states the file system is corrupt. For example, assume that you run an application that uses the MoveFileEx() function to replace files. If this function is used multiple times during a brief period, you may receive an "ERROR_FILE_CORRUPT" error message. Additionally, you may experience one of the following issues:

A warning message is displayed in the notification area. This warning message indicates that you should run the Chkdsk.exe utility to check the disk.

A disk check is scheduled for the next time that you start the computer.

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must be running Windows 7 or Windows Server 2008 R2.

Registry information

To use the update in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

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.760
0.16xxx

Windows 7 and Windows Server 2008 R2

RTM

GDR

6.1.760
0.20xxx

Windows 7 and Windows Server 2008 R2

RTM

LDR

GDR service branches contain only those fixes that are widely released to address widespread, extremely important 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 extremely important to maintain the state of the updated components. 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

Ntkrnlpa.exe

6.1.7600.16746

3,957,120

24-Jan-2011

05:39

x86

Ntoskrnl.exe

6.1.7600.16746

3,901,824

24-Jan-2011

05:39

x86

Ntkrnlpa.exe

6.1.7600.20886

3,966,848

24-Jan-2011

05:43

x86

Ntoskrnl.exe

6.1.7600.20886

3,911,552

24-Jan-2011

05:43

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Collapse this tableExpand this table

File name

File version

File size

Date

Time

Platform

Ntoskrnl.exe

6.1.7600.16746

5,510,528

24-Jan-2011

06:31

x64

Ntoskrnl.exe

6.1.7600.20886

5,475,712

24-Jan-2011

06:28

x64

Ntkrnlpa.exe

6.1.7600.16746

3,957,120

24-Jan-2011

05:39

x86

Ntoskrnl.exe

6.1.7600.16746

3,901,824

24-Jan-2011

05:39

x86

Ntkrnlpa.exe

6.1.7600.20886

3,966,848

24-Jan-2011

05:43

x86

Ntoskrnl.exe

6.1.7600.20886

3,911,552

24-Jan-2011

05:43

x86

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: