Batch files for which you create a hash rules do not work on a Windows XP-based client computer

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
You specify the following software restriction policies on the network. Or, you specify these policies locally:
  • You set the default security levels to Disallowed.
  • You create a new hash rule for some batch files.
  • You set the security level to Unrestricted.
When you set these policies, you expect that the batch files that you have specified in the hash rule can run on the client computers without restriction. However, when you try to run one of these batch files on a Windows XP-based client computer, the file does not work. A command prompt blinks on the screen and then disappears immediately. Additionally, an event that resembles the following is logged in Application log:

Event Type: Warning
Event Source: Software Restriction Policies
Event Category: None
Event ID: 865
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:Access to Path\filename.bat has been restricted by your Administrator by the default software restriction policy level.
For more information, see Help and Support Center at

Note This problem does not occur on a Windows Server 2003-based client computer.
Windows XP uses the Cmd.exe process to pass the hashing flag to the Software Restriction Policies engine. However, the Cmd.exe process ignores the hash rules that you specify for batch files. Therefore, this issue occurs.

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


To install this hotfix, you must have Windows XP Service Pack 2 installed.

Restart requirement

You have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 SP2, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
To configure software restriction Policies on a domain controller, follow these steps:
  1. Open the Active Directory Users and Computers MMC snap-in, right-click the organizational unit to which you want to apply the software restriction policies, and then click Properties.
  2. On the Group Policy tab, click Add, and then click Edit to open Group Policy Object Editor.
  3. In Group Policy Object Editor, expand User Configuration, expand Windows Settings, expand Software Restriction Policies, and then set the security levels and additional rules.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
324036 How to use software restriction policies in Windows Server 2003
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 943854 - Last Review: 01/16/2015 17:28:54 - Revision: 3.0

Microsoft Windows XP Professional

  • kbnosurvey kbarchive kbautohotfix kbexpertiseadvanced kbfix kbqfe kbhotfixserver KB943854