Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An event log may not be saved when you �Save and Clear� an event log in Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

You try to save and clear event logs in the .txt, .xml, or .csv formats by using Event Viewer (Eventvwr.msc) on a computer that is running Windows 7 or Windows Server 2008 R2. However, the event logs are truncated, or no event logs are saved.

Note When you experience this issue, the event logs are cleared.

For example, you follow these steps to save and clear the event log:
  1. Click Start, click Run, type Eventvwr.msc, and then click OK.
  2. Expand Windows Logs, and then click Application.
  3. Right-click Application, and then select Clear log....
  4. Click the Save and Clear button in the dialog box.
  5. Select Text (Tab delimited) (*.txt) in the drop-down list of Save as type.
  6. Type a file name and then click Save.
In this example, you experience one of the following results:
  • A 0 byte .txt file is generated.
  • The event logs are truncated.
  • All the event logs are saved correctly.

↑ Back to the top


Resolution

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: 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, your computer must be running Windows Server 2008 R2 or Windows 7.

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 English (United States) 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
Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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 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
File nameFile versionFile sizeDateTimePlatform
Miguicontrols.dll6.1.7600.206653,416,06411-Mar-201012:28x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Miguicontrols.dll6.1.7600.206653,416,06411-Mar-201012:28x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Miguicontrols.dll6.1.7600.206653,416,06411-Mar-201012:28x86

↑ Back to the top


Status

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

↑ Back to the top


More information

More information about how to troubleshoot the event viewer, visit the following Microsoft Web site:
Troubleshooting event viewer

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
File nameMsil_miguicontrols_31bf3856ad364e35_6.1.7600.20665_none_aebe6f20b6fc0ab4.manifest
File version
File size2,607
Date (UTC)11-Mar-2010
Time (UTC)13:00
PlatformNot Applicable
File nameX86_6ce0ec3fe69776e876a9dd46ececf126_31bf3856ad364e35_6.1.7600.20665_none_7fff6b16f430ac24.manifest
File version
File size684
Date (UTC)11-Mar-2010
Time (UTC)16:53
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_6ce0ec3fe69776e876a9dd46ececf126_31bf3856ad364e35_6.1.7600.20665_none_dc1e069aac8e1d5a.manifest
File version
File size686
Date (UTC)11-Mar-2010
Time (UTC)16:53
PlatformNot Applicable
File nameMsil_miguicontrols_31bf3856ad364e35_6.1.7600.20665_none_aebe6f20b6fc0ab4.manifest
File version
File size2,607
Date (UTC)11-Mar-2010
Time (UTC)13:00
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_6ce0ec3fe69776e876a9dd46ececf126_31bf3856ad364e35_6.1.7600.20665_none_80010f0cf42eb520.manifest
File version
File size685
Date (UTC)11-Mar-2010
Time (UTC)16:53
PlatformNot Applicable
File nameMsil_miguicontrols_31bf3856ad364e35_6.1.7600.20665_none_aebe6f20b6fc0ab4.manifest
File version
File size2,607
Date (UTC)11-Mar-2010
Time (UTC)13:00
PlatformNot Applicable

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, KB981466

↑ Back to the top

Article Info
Article ID : 981466
Revision : 1
Created on : 4/21/2010
Published on : 4/21/2010
Exists online : False
Views : 479