Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You have a computer that is running a 64-bit version of Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2.

  • On this computer, a process calls the CreateProcessWithTokenW function to create a child process that runs under Windows 32-bit on Windows 64-bit (WOW64).

  • The WOW64 child process is created to redirect standard input (STDIN), standard output (STDOUT), and standard error (STDERR).

In this scenario, the redirections do not work in the WOW64 child process. Therefore, any applications or services that depend on the redirection feature do not work.

Cause

There are two Process Environment Blocks (PEBs) for every WOW64child process. One PEB is used for 64-bit processes, and the other PEB is used for 32-bit processes that are running under the WOW64 emulation environment.

The CreateProcessWithTokenW function only duplicates the handles for STDIN, STDOUT, and STDERR from the parent process to the PEB for 64-bit processes. However, this function does not duplicate these handles to the PEB for 32-bit processes that are running under the WOW64 emulation environment. This behavior causes the child process that is running under WOW64 to be unable to use the redirected handles. Therefore, the redirections fail.

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

To apply this hotfix, your computer must be running one of the following operating systems:

  • Windows Vista Service Pack 1 (SP1)

  • Windows Vista Service Pack 2 (SP2)

  • Windows Server 2008

  • Windows Server 2008 Service Pack 2 (SP2)

  • Windows 7

  • Windows Server 2008 R2

Restart requirement

You must restart the computer after you apply this hotfix.

Registry information

You do not have to make any change to the registry.

File information

The English (United States) 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 Vista and Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    1.
    22xxx

    Windows Vista and Windows Server 2008

    SP1

    LDR

    6.0.600
    2.
    22xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • Service Pack 1 is integrated into the release version of Windows Server 2008.

  • 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 and for Windows Vista" section. MUM files 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 Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Seclogon.dll

6.0.6001.22431

29,184

12-May-2009

16:06

x64

Seclogon.dll

6.0.6002.22134

29,184

12-May-2009

15:41

x64

For all supported Itanium-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Seclogon.dll

6.0.6001.22431

57,856

12-May-2009

15:46

IA-64

Seclogon.dll

6.0.6002.22134

57,856

12-May-2009

15:33

IA-64

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

Seclogon.dll

6.1.7600.20787

30,720

21-Aug-2010

07:24

x64

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

File name

File version

File size

Date

Time

Platform

Seclogon.dll

6.1.7600.20787

65,024

21-Aug-2010

06:29

IA-64

Workaround

To work around this issue, call the CreateProcessAsUser function to create a child process.

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 CreateProcessWithTokenW function, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/ms682434(VS.85).aspxFor more information about the CreateProcessAsUser function, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/ms682429(VS.85).aspxFor more information, 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 Vista and for Windows Server 2008

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

File name

Amd64_4a7908b357eecad45497e7a614da5ab2_31bf3856ad364e35_6.0.6001.22431_none_eff62086a34ac976.manifest

File version

Not Applicable

File size

713

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

File name

Amd64_e18aeae085cca5f39361c0ace1ecfedf_31bf3856ad364e35_6.0.6002.22134_none_c800fbe0d1aafeca.manifest

File version

Not Applicable

File size

713

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

File name

Amd64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.0.6001.22431_none_48ed2db26d293c6b.manifest

File version

Not Applicable

File size

7,582

Date (UTC)

12-May-2009

Time (UTC)

19:30

Platform

Not Applicable

File name

Amd64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.0.6002.22134_none_4ad6a0786a4cdd94.manifest

File version

Not Applicable

File size

7,582

Date (UTC)

12-May-2009

Time (UTC)

19:25

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,598

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

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

File name

Ia64_23caceaa3d7286a9ff4a23775ef4da54_31bf3856ad364e35_6.0.6002.22134_none_d01b4e8816bf0190.manifest

File version

Not Applicable

File size

711

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

File name

Ia64_68069bedf1d5a4bd9f3dc637561ff507_31bf3856ad364e35_6.0.6001.22431_none_349d44d96d664fea.manifest

File version

Not Applicable

File size

711

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

File name

Ia64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.0.6001.22431_none_ecd03624b4c9d431.manifest

File version

Not Applicable

File size

7,572

Date (UTC)

12-May-2009

Time (UTC)

19:14

Platform

Not Applicable

File name

Ia64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.0.6002.22134_none_eeb9a8eab1ed755a.manifest

File version

Not Applicable

File size

7,572

Date (UTC)

12-May-2009

Time (UTC)

19:07

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,924

Date (UTC)

13-May-2009

Time (UTC)

03:32

Platform

Not Applicable

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_445df96a83014fe57068b08a79da6683_31bf3856ad364e35_6.1.7600.20787_none_20591bc8c261086c.manifest

File version

Not Applicable

File size

713

Date (UTC)

21-Aug-2010

Time (UTC)

12:03

Platform

Not Applicable

File name

Amd64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.1.7600.20787_none_48e4f3e3ce639760.manifest

File version

Not Applicable

File size

4,810

Date (UTC)

21-Aug-2010

Time (UTC)

08:37

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,886

Date (UTC)

21-Aug-2010

Time (UTC)

12:03

Platform

Not Applicable

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

File name

Ia64_a48ab9ecdf2f4b1206e2ae93b7bb6a43_31bf3856ad364e35_6.1.7600.20787_none_172788f1fbdb93a7.manifest

File version

Not Applicable

File size

711

Date (UTC)

21-Aug-2010

Time (UTC)

12:03

Platform

Not Applicable

File name

Ia64_microsoft-windows-secondarylogonservice_31bf3856ad364e35_6.1.7600.20787_none_ecc7fc5616042f26.manifest

File version

Not Applicable

File size

4,808

Date (UTC)

21-Aug-2010

Time (UTC)

08:17

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,684

Date (UTC)

21-Aug-2010

Time (UTC)

12:03

Platform

Not Applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×