Wednesday, November 16, 2022

AppLocker path condition does not work when a file name contains international characters in Windows 7 or in Windows Server 2008 R2 - Microsoft Support [MS]

Symptoms

Considering the following scenario:

  • You enable the AppLocker feature on a computer that is running Windows 7 or Windows Server 2008 R2.

  • You create an AppLocker rule by configuring a path condition that lets an application run on the computer.

  • You try to run an application whose executable file name contains international characters. For example, the file name of the application is Sübinacl.exe.

In this scenario, you cannot run the application.

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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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 Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply 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:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.21xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • 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 name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not Applicable

3,013

04-Feb-2012

12:24

Not Applicable

Appid.sys

6.1.7601.21915

50,176

04-Feb-2012

10:19

x86

Appidpolicyconverter.exe

6.1.7601.21915

97,792

04-Feb-2012

12:04

x86

Appidsvc.dll

6.1.7601.21915

29,696

04-Feb-2012

12:05

x86

Ntkrnlpa.exe

6.1.7601.21915

3,972,464

04-Feb-2012

12:13

Not Applicable

Ntoskrnl.exe

6.1.7601.21915

3,916,656

04-Feb-2012

12:13

Not Applicable

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not Applicable

3,013

04-Feb-2012

12:46

Not Applicable

Appid.sys

6.1.7601.21915

61,440

04-Feb-2012

10:21

x64

Appidpolicyconverter.exe

6.1.7601.21915

148,480

04-Feb-2012

12:26

x64

Appidsvc.dll

6.1.7601.21915

34,304

04-Feb-2012

12:27

x64

Ntoskrnl.exe

6.1.7601.21915

5,561,200

04-Feb-2012

12:33

x64

Appidapi.dll

6.1.7601.21915

50,688

04-Feb-2012

12:05

x86

Ntkrnlpa.exe

6.1.7601.21915

3,972,464

04-Feb-2012

12:13

Not Applicable

Ntoskrnl.exe

6.1.7601.21915

3,916,656

04-Feb-2012

12:13

Not Applicable

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Appid-ppdlic.xrm-ms

Not Applicable

3,013

04-Feb-2012

11:40

Not Applicable

Appid.sys

6.1.7601.21915

131,072

04-Feb-2012

09:39

IA-64

Appidcertstorecheck.exe

6.1.7601.21915

39,424

04-Feb-2012

11:16

IA-64

Appidpolicyconverter.exe

6.1.7601.21915

282,624

04-Feb-2012

11:16

IA-64

Appidsvc.dll

6.1.7601.21915

74,240

04-Feb-2012

11:18

IA-64

Ntoskrnl.exe

6.1.7601.21915

11,130,224

04-Feb-2012

11:27

IA-64

Appidapi.dll

6.1.7601.21915

50,688

04-Feb-2012

12:05

x86

Ntkrnlpa.exe

6.1.7601.21915

3,972,464

04-Feb-2012

12:13

Not Applicable

Ntoskrnl.exe

6.1.7601.21915

3,916,656

04-Feb-2012

12:13

Not Applicable

Workaround

To work around this issue, use only uppercase letters in the path when you configure the path rule condition.

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 the path rule condition in AppLocker, visit the following Microsoft website:

General information about the path rule conditionFor more information about the AppLocker feature, visit the following Microsoft website:

General information about the AppLocker featureFor 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 name

X86_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.21915_none_59de1cfe298615a7.manifest

File version

Not Applicable

File size

15,227

Date (UTC)

04-Feb-2012

Time (UTC)

16:39

Platform

Not Applicable

File name

X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21915_none_6ec26e532b81dc09.manifest

File version

Not Applicable

File size

16,151

Date (UTC)

04-Feb-2012

Time (UTC)

12:40

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.21915_none_b5fcb881e1e386dd.manifest

File version

Not Applicable

File size

15,231

Date (UTC)

04-Feb-2012

Time (UTC)

16:51

Platform

Not Applicable

File name

Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21915_none_cae109d6e3df4d3f.manifest

File version

Not Applicable

File size

15,291

Date (UTC)

04-Feb-2012

Time (UTC)

13:44

Platform

Not Applicable

File name

Wow64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.21915_none_c05162d4164448d8.manifest

File version

Not Applicable

File size

3,356

Date (UTC)

04-Feb-2012

Time (UTC)

12:24

Platform

Not Applicable

File name

X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21915_none_6ec26e532b81dc09.manifest

File version

Not Applicable

File size

16,151

Date (UTC)

04-Feb-2012

Time (UTC)

12:40

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.21915_none_59dfc0f429841ea3.manifest

File version

Not Applicable

File size

15,229

Date (UTC)

04-Feb-2012

Time (UTC)

16:31

Platform

Not Applicable

File name

Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21915_none_6ec412492b7fe505.manifest

File version

Not Applicable

File size

15,289

Date (UTC)

04-Feb-2012

Time (UTC)

13:40

Platform

Not Applicable

File name

Wow64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.21915_none_c05162d4164448d8.manifest

File version

Not Applicable

File size

3,356

Date (UTC)

04-Feb-2012

Time (UTC)

12:24

Platform

Not Applicable

File name

X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.21915_none_6ec26e532b81dc09.manifest

File version

Not Applicable

File size

16,151

Date (UTC)

04-Feb-2012

Time (UTC)

12:40

Platform

Not Applicable

No comments:

Post a Comment

Search This Blog

August 11, 2020—KB4571694 (OS Build 14393.3866) - Microsoft Support [MS]

August 11, 2020—KB4571694 (OS Build 14393.3866) Windows 10, version 1607,...