Microsoft KB Archive Search

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.

  1. Home
  2. Embedded Lockdown Manager does not set a shell in a system that uses seven or more language packs

Embedded Lockdown Manager does not set a shell in a system that uses seven or more language packs

View products that this article applies to.

Symptoms

When Windows Embedded 8.1 Industry has seven or more language packs installed, the Shell Launcher setting in Embedded Lockdown Manager does not set a shell as expected. Additionally, Mmc.exe stops running and generates the following error event:

Application: mmc.exe

Framework Version: v4.0.30319

Description: The application requested process termination through System.Environment.FailFast(string message).

Message: Call cancelled

Stack:

at System.Environment.FailFast(System.String)

at Microsoft.Windows.Embedded.Lockdown.UnifiedConfiguration.SafeThread+<>c__DisplayClass2.<.ctor>b__0()

at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Threading.ThreadHelper.ThreadStart()

↑ Back to the top

Cause

This problem occurs because there is not enough available memory to enable WMI to run successfully.

↑ Back to the top

Workaround

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

To work around this problem, follow these steps:
  1. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM
  2. In this subkey, create an ArbSystemHighMaxLimitFactor DWord entry.
  3. In this entry, set the following value:

    0x0000004b (75)
  4. Configure the data range of the new value to range from 0x00000032 (50) to 0x00000064 (100).
Note This value lets WMI use the specified percentage of the available memory. This percentage may vary among systems. However, the maximum value is less than 512 MB. If there is no value created, the system sets the default maximum value at 50 percent of available memory.

↑ Back to the top

Keywords: kbprb, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 3076960
Revision : 1
Created on : 1/7/2017
Published on : 7/7/2015
Exists online : False
Views : 257