The application failed to initialize properly (0xc0000135)

The application failed to initialize properly (0xc0000135) is a typical 0xc0000135 error message users receive when attempting to open a Windows application. The application failed to initialize properly (0xc0000135) error is not as bad as 0xc0000135 error that occurs at startup, and the troubleshooting is easier. We hope the information on this page helps you resolve “The application failed to initialize properly (0xc0000135)”.

Below you can read about some instances of "the application failed to initialize properly (0xc0000135)" error that can be resolved either manually or by applying a hotfix or service pack from Microsoft. Note: fixing the “the application failed to initialize properly (0xc0000135)” error manually requires advanced computer skills.

The application failed to initialize properly (0xc0000135) and corrupt shortcut file

Sounds simple, but 0xc0000135 and the inability to initiate an application may be caused by a corrupt shortcut file. Try to start the application from it's program folder. If it starts, create a new shortcut. If it remains, see other suggestions on this page.

Reinstall the application

Try removing and reinstallign the application. Restart the computer when the installation is complete and try to initiate the application again. Sometimes that resolves the "application failed to initialize properly (0xc0000135)" error.

0xc0000135 and logon.scr - application error

You may get the following 0xc0000135 error message: logon.scr - Application Error (in title bar of window) The application failed to initialize properly (0xc0000135). Click OK to terminate the application. you click "OK" as prompted, then you get the black screen with only mouse cursor on it. Then the computer restarts and starts to loop repeating the same scenario. In this case "The application failed to initialize properly (0xc0000135)" most likely refers to one of startup applications or services. You'll have to determine which one causes the problem and disable or repair it. The best way is to use clean boot troubleshooting{:title="clean boot troubleshooting"} method. First, you need to perform clean boot procedure and see if 0xc0000135 stops. If it does, disable half of startup services and see if 0xc0000135 error goes away after restarting. If it doesn't disable half of the remaining services. If it does, enable half of the previously disabled services, and see if the error appears, and so on. Use this method until you pinpoint the problematic service or file. If you have Vista may try to use Startup Repair tool in you cannot access Windows even in Safe Mode.

0xc0000135 and FRxReportManager

You may get the following message when starting Report Manager (FRxReportManager): "FRxReportManager.exe - Application Error: The application failed to initialize properly (0xc0000135). Click on OK to terminate the application." 0xc0000135 error{:title="0xc0000135"} occurs because the .NET Framework 1.1 Service Pack 1 and Microsoft .NET Framework 1.1 are not installed on your server or workstation. Download the .NET Framework 1.1 Service Pack 1 and the .NET Framework 1.1 and apply to all servers and workstations where you are using planning to use Microsoft FRx applications. That should resolve "the application failed to initialize properly (0xc0000135)" error.

The application failed to initialize properly (0xc0000135) while logging on Windows User Account

If you get the "application failed to initialize properly (0xc0000135)" while logging on Windows account, the error is most likely caused by a startup service or application. Try to perform clean boot procedure and see if 0xc0000135 goes away. If it does, use clean boot troubleshooting guide to pinpoint the problematic file or service that causes 0xc0000135 and disable it.

Basic Self-Help Info: