This article describes various known issues that occur when system files or device drivers are compressed in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.
Symptoms
Assume that you have a computer that is running Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2 and has Advanced Format disks that have a 4,096 bytes (4K) physical sector size.
The servicing stack in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 may enable NTFS compression on some device drivers and other system files in order to save disk space. For example, this may occur after you install a Windows Update. Because of a problem in the Ntfs.sys file, when the compressed files are loaded from a 4K sector disk, various drivers may encounter failures because of random access memory (RAM) that is expected to be initialized to zero contains random data instead.Known Issues that are fixed in this hotfix
-
You try to mount a virtual hard disk (VHD or VHDX) on the computer. In this situation, you receive a Stop error that resembles the following:
-
During the start of the computer, you receive a Stop error that resembles the following:
If you analyze the memory dump file by using a debugger, you may notice that intelppm.sys has tried to execute some code at an invalid address. Or, you may see a failure occurred when the wpprecorder.sys was loaded during the initialization of another driver, such as cdrom.sys.
Notes-
The parameters in the Stop error messages vary, depending on the configuration of the computer.
-
Not all "0x0000003B" or "0x0000007E" Stop errors are caused by this issue.
-
Sometimes system files are compressed after you install a Windows update.
Cause
This issue occurs because the read of the compressed file has to be double-buffered. When the compressed binaries on 4K sector disks are read into memory, some memory may be copied beyond the original buffer length.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain 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 do not 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:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 8.1 and Windows Server 2012 R2 file information and notes
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
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:
Version
Product
Milestone
Service branch
6.3.960 0.17xxx
Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2
RTM
GDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately 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.
For all supported x86-based versions of Windows 8.1
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Ntfs.sys |
6.3.9600.17631 |
1,687,872 |
14-Jan-2015 |
20:06 |
x86 |
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Ntfs.sys |
6.3.9600.17631 |
2,022,720 |
14-Jan-2015 |
20:12 |
x64 |
For all supported ARM-based versions of Windows 8.1
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Ntfs.sys |
6.3.9600.17631 |
1,495,888 |
14-Jan-2015 |
20:18 |
Not applicable |
Additional file information
Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File property |
Value |
---|---|
File name |
X86_a5d431249bef2b5984ca7827a947e986_31bf3856ad364e35_6.3.9600.17633_none_b0057fc0d2074ef4.manifest |
File version |
Not applicable |
File size |
692 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:30 |
Platform |
Not applicable |
File name |
X86_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_3b45ec80385d9adb.manifest |
File version |
Not applicable |
File size |
16,008 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:34 |
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File property |
Value |
---|---|
File name |
Amd64_c6023eb259ca802b99b3e661e37dc48b_31bf3856ad364e35_6.3.9600.17633_none_bd094807436c299f.manifest |
File version |
Not applicable |
File size |
696 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:30 |
Platform |
Not applicable |
File name |
Amd64_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_97648803f0bb0c11.manifest |
File version |
Not applicable |
File size |
16,014 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:38 |
Platform |
Not applicable |
Additional files for all supported ARM-based versions of Windows 8.1
File property |
Value |
---|---|
File name |
Arm_bc13181ffa3e7154af502f1530c9b6f8_31bf3856ad364e35_6.3.9600.17633_none_2efec30083ff7f01.manifest |
File version |
Not applicable |
File size |
692 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:30 |
Platform |
Not applicable |
File name |
Arm_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_3b485ed8385ab9a1.manifest |
File version |
Not applicable |
File size |
16,008 |
Date (UTC) |
14-Jan-2015 |
Time (UTC) |
20:30 |
Platform |
Not applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.