Audit event ID 560 incorrectly displays the name of a deleted file in an 8.3 file name format if you delete the file at a command prompt in Windows Server 2003, in Windows XP, or in Windows Vista

Consider the following scenario:

• You configure the system to audit object access in Windows Server 2003, in Windows XP, or in Windows Vista.
• At a command prompt, you delete a file that has a long file name.

In this scenario, the Object Name field in audit event ID 560 incorrectly displays the name of the deleted file in an 8.3 file name format.

For example, audit event ID 560 may resemble the following:

Event Type: Success Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
Object Open:
Object Server: Security
Object Type: File
Object Name: Drive:\Path\Sample~1.EXE
New Handle ID: 92
Operation ID: {0,16979818}
Process ID: 1960
Primary User Name: UserName
Primary Domain: DomanName
Primary Logon ID: (0x0,0x19116)
Client User Name: -
Client Domain: -
Client Logon ID: -
Accesses DELETE
ReadAttributes
Privileges –

When you delete a file that has a long file name in Windows Explorer, the Object Name field in audit event ID 560 displays the complete file name as expected.

This problem occurs because an 8.3 file name string is incorrectly passed as a parameter when the command prompt program (Cmd.exe) deletes a file.

Windows Vista service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

Windows Server 2003

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. 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, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 1, x86-based versionsWindows Server 2003 with Service Pack 2, x86-based versionsWindows Server 2003 with Service Pack 1, Itanium-based versionsWindows Server 2003 with Service Pack 2, Itanium-based versionsWindows Server 2003, x64-based versionsWindows Server 2003 with Service Pack 2, x64-based versions

Windows XP

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. 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, you must have Windows XP Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with Service Pack 2, x86-based versions

Windows Vista

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. 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, 32-bit versionsWindows Vista, 64-bit versions

To work around this problem, use only Windows Explorer to delete files that have long file names.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

After you install this hotfix, the complete file name appears in the Object Name field of audit event ID 560. The following is a sample event:

Event Type: Success Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
Object Open:
Object Server: Security
Object Type: File
Object Name: Drive:\Path\This is a long file name.txt
Handle ID: 124
Operation ID: {0,179196}
Process ID: 1536
Image File Name: C:\WINDOWS\system32\cmd.exe
Primary User Name: UserName
Primary Domain: DomainName
Primary Logon ID: (0x0,0x1EDF0)
Client User Name: -
Client Domain: -
Client Logon ID: -
Accesses: DELETE
ReadAttributes

Privileges: -
Restricted Sid Count: 0
Access Mask: 0x10080

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: