Computer does not crash when the disk is full after CrashOnAuditFail is set in Windows 7 or in Windows Server 2008 R2

Article translations Article translations
Article ID: 2492505 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You enable the following Local Security Policy setting on a computer that is running Windows 7 or Windows Server 2008 R2:
    Audit: Shut down system immediately if unable to log security audits

    Note The CrashOnAuditFail registry value is set when this Local Security Policy setting is enabled.
  • The disk volume that contains the audit log is full, and the operating system cannot log a new audit entry.
In this scenario, the operating system does not shut down.

CAUSE

This issue occurs because the DiskIsFull event is treated as a separate event. Therefore, the DiskIsFull event is not converted to a LogIsFull event, and the Local Security Policy does not work.

RESOLUTION

After you install the following hotfix, the DiskIsFull event is converted to a LogIsFull event, and the computer crashes.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site:
http://support.microsoft.com/contactus/?ws=support
Note 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 be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Registry information

To use the hotfix 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 hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows 7 and Windows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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 nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.1.7600.208791,087,48813-Jan-201105:43x86
Wevtsvc.dll6.1.7601.216401,087,48813-Jan-201105:38x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.1.7600.208791,648,12813-Jan-201106:24x64
Wevtsvc.dll6.1.7601.216401,646,59213-Jan-201106:25x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.1.7600.208792,900,48013-Jan-201105:28IA-64
Wevtsvc.dll6.1.7601.216402,900,48013-Jan-201105:16IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size2,773
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameX86_0abf4e4cdcbf7c7dc5cf383e5dba2284_31bf3856ad364e35_6.1.7600.20879_none_7d8a869f34dd71d6.manifest
File versionNot applicable
File size696
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameX86_b97991975bfa80930ef7174862a9a89c_31bf3856ad364e35_6.1.7601.21640_none_ac3c9ebb13c98157.manifest
File versionNot applicable
File size696
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameX86_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7600.20879_none_dd3327b48d3ea2c6.manifest
File versionNot applicable
File size40,903
Date (UTC)13-Jan-2011
Time (UTC)06:17
PlatformNot applicable
File nameX86_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7601.21640_none_df30f1e48a54d6d0.manifest
File versionNot applicable
File size40,903
Date (UTC)13-Jan-2011
Time (UTC)06:10
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_bec91be63fe6d6eef5524e731539ebea_31bf3856ad364e35_6.1.7601.21640_none_729a71c9bebed4e4.manifest
File versionNot applicable
File size700
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameAmd64_d8e2c5a22400dd0a15337583f1b4cee7_31bf3856ad364e35_6.1.7600.20879_none_3b97a6d3663d3500.manifest
File versionNot applicable
File size700
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameAmd64_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7600.20879_none_3951c338459c13fc.manifest
File versionNot applicable
File size40,907
Date (UTC)13-Jan-2011
Time (UTC)07:04
PlatformNot applicable
File nameAmd64_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7601.21640_none_3b4f8d6842b24806.manifest
File versionNot applicable
File size40,907
Date (UTC)13-Jan-2011
Time (UTC)07:03
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,215
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_0a22a3feef8c5fac51bfef88176563ab_31bf3856ad364e35_6.1.7600.20879_none_0169ff2e6b80f12a.manifest
File versionNot applicable
File size698
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameIa64_56e10fd2d07ee6845b36738b8b8429b1_31bf3856ad364e35_6.1.7601.21640_none_29d76dad8b60ac9b.manifest
File versionNot applicable
File size698
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable
File nameIa64_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7600.20879_none_dd34cbaa8d3cabc2.manifest
File versionNot applicable
File size40,905
Date (UTC)13-Jan-2011
Time (UTC)06:59
PlatformNot applicable
File nameIa64_microsoft-windows-eventlog_31bf3856ad364e35_6.1.7601.21640_none_df3295da8a52dfcc.manifest
File versionNot applicable
File size40,905
Date (UTC)13-Jan-2011
Time (UTC)07:00
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,168
Date (UTC)13-Jan-2011
Time (UTC)15:56
PlatformNot applicable

Properties

Article ID: 2492505 - Last Review: February 10, 2011 - Revision: 1.0
APPLIES TO
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Starter
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Web Server 2008 R2
Keywords: 
kbautohotfix kbqfe kbfix kbhotfixserver kbsurveynew kbexpertiseinter KB2492505

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com