This article describes an issue in which the chkdsk command together with the spotfix option doesn't fix extended volumes corruption in Windows Server 2012 R2. A hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section.
For more information about the symptom of this issue, see the More Information section.
Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.
Before you apply this hotfix, install update 2919355 in Windows 8.1 or Windows Server 2012 R2.
To use the hotfix in this package, you don't have to make any changes to the registry.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix doesn't replace a previously released hotfix.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2
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:
6.3.960 0.16 xxx
Windows RT 8.1
6.3.960 0.17 xxx
Windows 8.1 and Windows Server 2012 R2
6.3.960 0.18 xxx
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
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 in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
See the terminology that Microsoft uses to describe software updates.
When you run the chkdsk /scan command, you receive a message that indicates that a corrupt file exists in the $Extend volume. The message looks something like this:
Found corrupt basic file structure for "\$Extend <0xb,0xb>" ... queued for offline repair.Found an unneeded link ($FILE_NAME: "$Extend") in index "$I30" of directory "\ <0x5,0x5>" ... queued for offline repair.
However, when you run the chkdsk /spotfix command to repair the corruptions, the corruptions are not repaired, and you receive a "no corruption found' message that looks something like this:
Record 2 of 5: Corrupt File "\$Extend <0xb,0xb>" ... no corruption found.Record 3 of 5: Unneeded index entry in index "$I30" of directory "\ <0x5,0x5>" ... no corruption found.
When you run the chkdsk /scan command again, you receive messages that indicate that the corruption in the $Extend volume still exists.
ID článku: 3102770 - Poslední kontrola: 11/11/2015 00:53:00 - Revize: 1.0
Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows RT 8.1