This article describes an issue that occurs when you set the MinDiffAreaFileSize registry value to specify the minimum initial size in Windows Server 2012 R2. You can fix this issue by using the update in this article. Before you install this update, see the Prerequisites section.
Symptoms
The MinDiffAreaFileSize registry is ignored, and the initial size of the diff area is calculated by other logic that's based on free space and filesystem size.
How to get this update
You can get this update by using one of the following methods. We have released an update through Windows Update and Microsoft Download Center. Even though this issue is observed only in Windows Server 2012 R2, the update also applies to Windows 8.1 and Windows RT 8.1. Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
Method 1: Windows Update
This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.
Method 2: Microsoft Download Center
The following files are available for download from the Microsoft Download Center:
|
Operating system |
Update |
|---|---|
|
All supported x86-based versions of Windows 8.1 |
|
|
All supported x64-based versions of Windows 8.1 |
|
|
All supported x64-based versions of Windows Server 2012 R2 |
Note The update for Windows RT 8.1 can be downloaded only from Windows Update. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services 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.
Update detail information
Prerequisites
To apply this update, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.
Registry information
To apply this update, you don't have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this update.
Update replacement information
This update doesn't replace a previously released update.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
File Information
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
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:
Version
Product
Milestone
Service branch
6.3.960 0.18Â xxx
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
RTM
GDR
-
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.
Windows RT 8.1
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Volsnap.sys |
6.3.9600.18230 |
244,584 |
06-Feb-2016 |
22:52 |
Not applicable |
x64 Windows 8.1 and Windows Server 2012 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Volsnap.sys |
6.3.9600.18230 |
316,760 |
06-Feb-2016 |
22:41 |
x64 |
x86 Windows 8.1
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Volsnap.sys |
6.3.9600.18230 |
265,048 |
06-Feb-2016 |
22:46 |
x86 |
Windows RT 8.1
|
File property |
Value |
|---|---|
|
File name |
Arm_volume.inf_31bf3856ad364e35_6.3.9600.18230_none_aa8acd5e1786f3db.manifest |
|
File version |
Not applicable |
|
File size |
2,103 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:00 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,585 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:00 |
|
Platform |
Not applicable |
x64 Windows 8.1 and Windows Server 2012 R2
|
File property |
Value |
|---|---|
|
File name |
Amd64_volume.inf_31bf3856ad364e35_6.3.9600.18230_none_06a6f689cfe7464b.manifest |
|
File version |
Not applicable |
|
File size |
2,107 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:07 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,593 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:00 |
|
Platform |
Not applicable |
x86 Windows 8.1
|
File property |
Value |
|---|---|
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
1,585 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:00 |
|
Platform |
Not applicable |
|
File name |
X86_volume.inf_31bf3856ad364e35_6.3.9600.18230_none_aa885b061789d515.manifest |
|
File version |
Not applicable |
|
File size |
2,103 |
|
Date (UTC) |
06-Feb-2016 |
|
Time (UTC) |
23:04 |
|
Platform |
Not applicable |
