"0xC0000142" or "-1073741502" Stop error when many PowerShell scripts call the Console.Write method or when you try to start many console applications on a PowerShell console in Windows 7 or in Windows Server 2008 R2
Symptoms
Assume that many Windows PowerShell scripts call the Console.Write method, or you try to start many console applications on a Windows PowerShell console on a computer that is running Windows 7 or Windows Server 2008 R2. In this situation, the script exits or the console applications do not start, and you receive one of the following exit codes:
0xC0000142
-1073741502
Additionally, you cannot start any of the console applications from the PowerShell console.
Notes
•The exit code describes a STATUS_DLL_INIT_FAILED issue.
•This issue is resolved temporarily when you stop the PowerShell script and then restart the PowerShell console.
Cause
This issue is caused by an error in the Microsoft.powershell.consolehost.dll file. When a Windows PowerShell script calls the Console.Write method, or when you run an executable file for an application from a Windows PowerShell session, values are written into the PowerShell console. Additionally, a corresponding console handle is created. When many console handles are created, the console handles leak, and the issue that is described in the "Symptoms" section occurs.
Resolution
This hotfix is also available at Microsoft Update Catalog.
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=support
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.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:•Windows 7
•Windows 7 Service Pack 1 (SP1)
•Windows Server 2008 R2
•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 this hotfix, 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.
Please see - https://support.microsoft.com/en-us...-stop-error-when-many-powershell-scripts-call
