Does Anyone Know of a Fix for the 0xc0000142 Problem

After my computer is inactive for a few hours and I come back to start using it again, almost always, any icon that I click on, I will get the following: a message box comes up over with the text "The application failed to initialize properly (0x0000142). Click OK to terminate the application."
If I reboot the computer, all seems to be fine until it sits inactive for a while. This is getting to be a real nuisance. I have done a lot of searching in google and so far I have not found the fix. I have seen a lot of messages where others or having the same problem. I sure hope someone in the Windows 7 forums has the fix for this. I am using Windows 7 RTM (64 bit) on an almost new Dell XPS 420 with 8 gig of ram with an intel Core 2 Quad processor.

Try Systen restore to restore the comtputer to a date/time prior to when the problems began.

Also might try running sfc /scannow from the Run command to replace any damage or missing system files.

You must be getting BSOD's with that error code. could you go into c:\windows\minidump, zip the dum file (*.dmp) and upload it for us to see. If its not in minidump you can search for *.dmp

Ken

Reply concerning 0xc0000142 error

No, not getting a BSOD, only getting what I posted.

What I've found so far and I've been looking around a LOT, since this is aproblem for me too, is this:
Error message when you call the CreateProcess function to start a process of a console application by using an account other than the current logon account in Windows Server 2003: "The application failed to initialize properly (0xc0000142
This seems to be the only valid explanation and could maybe be linked to this solution:
Unexpected behavior occurs when you run many processes on a computer that is running SQL Server

Sadly, no solutions are suggested to work with Windows 7 and currently I'm afraid to reboot my computer, in fear of running into even more severe issues.

All solutions suggested by Microsoft themselves for this issue on other OSs mention this file, Winsrv.dll, as the culprit. This reference can also be found in the kb/824422-article above, since that is listed in that particular registry value.
I will not, ever, use System Restore to fix anything on my computer, so that is never a valid solution. I should be able to fix anything on a current system, with replacing files or editing system settings. There's no telling what changes has been made since last restore point was saved and will be lost forever if I "go back".

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO\" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Here's the test.nfo.

I had to shutdown my computer since it was time to go away for the Christmas celebrations. When booting again the error hasn't (yet) reccurred.

/Kim

No file was uploaded, please give it another go!
Thanks!

usasma said:

No file was uploaded, please give it another go!
Thanks!

Click to expand...

I edited my post.
I had forgotten to zip it, so it was refused the first couple of times

Someone fixed it like this but I'm not familor with the program.

In responce to this question.
Has anyone had msys working on Windows 7 64 bit version?
I'm getting "The application failed to initialize properly (0xc0000142)"
error.
I tried both 1.0.10 and 1.011 with the same result.

Alex.

Hello,
I had the same problem with Msys and Windows Seven, but found a workaround : start msys without Rxvt

msys.bat -norxvt

chev65 said:

Someone fixed it like this but I'm not familor with the program.

In responce to this question.
Has anyone had msys working on Windows 7 64 bit version?
I'm getting "The application failed to initialize properly (0xc0000142)"
error.
I tried both 1.0.10 and 1.011 with the same result.

Alex.

Hello,
I had the same problem with Msys and Windows Seven, but found a workaround : start msys without Rxvt

msys.bat -norxvt

Click to expand...

Thank you, chev65, but I don't think your suggested solution is relevant to the issue as such, but maybe for just running that particular program. The 0xc142 problem affected almost the entire system, expecially all console programs.

The .nfo file is unreadable by me. Please try this:

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO\" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Click to expand...

usasma said:

The .nfo file is unreadable by me. Please try this:

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO\" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Click to expand...

Click to expand...

Hey

The command you suggest is incorrect. It has to be "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" without the \ at the end. If it is included it will give an error and not create the .nfo at all.
How to use System Information (MSINFO32) command-line tool switches

You should be able to read the test.nfo in any texteditor, but I too get an error when trying to double-click and load in MSinfo program. It says file is damaged or incompatible. It opens just fine in Notepad++.

Here I added a few more testfiles.

Thanks for catching that!

The text versions of the report have an enormous amount of stuff in them - which makes it difficult to sort through.
Also, I've got eye problems and can't stand to stare at that amount of data for long periods of time.

Let's try this:
- recreate the problem and note the time.
- open up the MSINFO32 program and select the Software Environment category, then the Windows Error Reporting category.
- look there for events that occurred around the time that you noted for the problem.
- select those events by holding down "Ctrl" and clicking on each one.
Then press "Ctrl" and "C" to copy them - then press "Ctrl" and "P" to paste them into your next post.
That'll cut down on the amount of text to be scanned through and will make it easier to check.

usasma said:

...

Let's try this:
- recreate the problem and note the time.

...

That'll cut down on the amount of text to be scanned through and will make it easier to check.

Click to expand...

I can't recreate it, so I guess I'll just have to wait till it returns.
Thank you for now and hope you're enjoying the rest of the holidays.
/Kim