Write Cache Warnings on Hyper-V Guest after KB2853952

Starting in September 2013, Windows Server 2012 R2 machines running as Hyper-V guests started issuing these warnings on reboot [8/18/2020:  see comments—applies to 2012 but not R2]:

Log Name:      System
Source:        Disk
Event ID:      32
Level:         Warning
Description:
The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may occur.

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Event ID:      1539
Level:         Warning
Description:
Active Directory Domain Services could not disable the software-based disk write cache on the following hard disk.
Hard disk:
c:
Data might be lost during system failures.

It turns out this started after the patch described in KB2853952 was installed with the September 2013 updates. Before the patch, when a Hyper-V guest tried to disable write caching on a virtual IDE disk, it would report success even though it didn’t really succeed. With the patch, it reports failure.

The background on this is covered in this thread and this blog post [8/18/2020 link was no longer active; updated to refer to post on archive.org]. In summary:  it’s a Good Thing that the guest knows write caching can’t be disabled, because then Active Directory falls back to non-cached updating. The 1539 message says “Data might be lost during system failures” but really it means “Active Directory data will NOT be lost during system failures because Active Directory will not use write caching.”

2 thoughts on “Write Cache Warnings on Hyper-V Guest after KB2853952

  1. Jeffrey Fox

    Hi! It seems this should say “Windows Server 2012” not “Windows Server 2012 R2”. KB2853952 didn’t apply to 2012 R2, as Hyper-V 2012 R2 didn’t ever have this bug. And there was no September 2013 update rollup for 2012 R2, unless you’re talking about pre-release updates, as it went GA in October that year.

    KB2853952 was included in the July 2013 update for Windows Server 2012 and Windows Server 2008 R2. It seems that for many people who had automatic updates, it didn’t show up as “recommended” or “critical”, and thus get installed automatically, until September, which is why posts about this started appearing then.

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.

This site uses Akismet to reduce spam. Learn how your comment data is processed.