This article applies to Windows 7 Professional for Embedded Systems, to Windows 7 Ultimate for Embedded Systems, and to Windows Server 2008 R2 for Embedded Systems.

Symptoms

Consider the following scenario:

  • You have a device that is running a 64-bit version¬†of Windows 7 for Embedded Systems or of Windows Server 2008 R2 for Embedded Systems.

  • You call the Wow64DisableWow64FsRedirection¬†function to disable the file system redirection feature.

  • You call the CreateProcess function from a 32-bit process.



In this scenario, the CreateProcess function fails. Therefore, the 32-bit process cannot create any child processes.

Cause

This issue occurs because of a check in the embedded system.

By default, the file system redirection feature is enabled when a 32-bit process is started in a device that is running a 64-bit version of Windows 7 for Embedded Systems or of Windows Server 2008 R2 for Embedded Systems.

If the Wow64DisableWow64FsRedirection function is called to disable the file system redirection feature before the CreateProcess function is called, the CreateProcess function checks whether the child process can run or not. However, the check fails when the check tries to load the Embdtrst.dll file into the address space of the 32-bit process. Therefore, the 32-bit process cannot create any child processes in the embedded system.

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:

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

No prerequisites are required.

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


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 x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ntdll.dll

6.1.7600.16564

1,736,608

01-Apr-2010

08:18

x64

Ntdll.dll

6.1.7600.20682

1,737,632

01-Apr-2010

07:54

x64

Ntdll.dll

6.1.7600.16564

1,290,064

01-Apr-2010

07:39

x86

Ntdll.dll

6.1.7600.20682

1,290,064

01-Apr-2010

18:55

x86

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 Windows Embedded, visit the following Microsoft website:

General information about Windows EmbeddedFor more information about the CreateProcess function, visit the following Microsoft Developer Network (MSDN) website:

General information about the "CreateProcess" functionFor more information about a file system redirector, visit the following MSDN website:

General information about a file system redirectorFor 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 x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_4b4c97dda67b31403ea23b01d9aa97dd_31bf3856ad364e35_6.1.7600.20682_none_a4673cfe64a1fd1e.manifest

File version

Not applicable

File size

697

Date (UTC)

01-Apr-2010

Time (UTC)

23:53

Platform

Not applicable

File name

Amd64_63531f51d005768cbf539e71246ab930_31bf3856ad364e35_6.1.7600.16564_none_433be78e8be1a871.manifest

File version

Not applicable

File size

697

Date (UTC)

01-Apr-2010

Time (UTC)

23:53

Platform

Not applicable

File name

Amd64_a974694bfe71dda3d4e4d8dfb44685a1_31bf3856ad364e35_6.1.7600.16564_none_15cd72ba8019f84c.manifest

File version

Not applicable

File size

697

Date (UTC)

01-Apr-2010

Time (UTC)

23:53

Platform

Not applicable

File name

Amd64_c70f86838d7465795fe90207663bf3d8_31bf3856ad364e35_6.1.7600.20682_none_e914f031a7a1a1f2.manifest

File version

Not applicable

File size

697

Date (UTC)

01-Apr-2010

Time (UTC)

23:53

Platform

Not applicable

File name

Amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16564_none_b4e0734315cf5bd2.manifest

File version

Not applicable

File size

3,806

Date (UTC)

01-Apr-2010

Time (UTC)

09:18

Platform

Not applicable

File name

Amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20682_none_b5526fa22eff00d0.manifest

File version

Not applicable

File size

3,806

Date (UTC)

01-Apr-2010

Time (UTC)

20:26

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,329

Date (UTC)

01-Apr-2010

Time (UTC)

23:53

Platform

Not applicable

File name

Wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.16564_none_bf351d954a301dcd.manifest

File version

Not applicable

File size

3,566

Date (UTC)

01-Apr-2010

Time (UTC)

08:03

Platform

Not applicable

File name

Wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7600.20682_none_bfa719f4635fc2cb.manifest

File version

Not applicable

File size

3,566

Date (UTC)

01-Apr-2010

Time (UTC)

20:01

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×