Windows 10: SoftwareUpdateNotification.exe-Application Error, Code 0Xc0000135

I am getting this message frequently as popup while working on my desktop. I was getting another error message SoftwareUpdateNotification.exe Application Error with error code 0X9007007E.


I updated Windows 10 yesterday and started getting this new error with error code 0Xc0000135.

What do I have to udpate ? How to find the root cause of error through the error code number ?


I am not able to open some of the application such as Microsoft Power BI Desktop. I can install but not able to open it, Power BI is not responding to launch command.


I am using Windows10. Please help.

:)

 

0xc0000135 error when opening most applications

This problem started about 1 week or 2 ago; I have a Dell XPS 13 9460 computer running Windows 10.

Whenever I try opening many applications, including Steam, NordVPN, Microsoft Word, Spotify and more, I get this error, "The application was unable to start correctly (0xc0000135)".

I have tried doing a clean boot, but it doesn't work and I have tried doing system restores but they say they were unsuccessful.

Does anyone have any other suggestions?

 

BIOS error codes

So I have motherboard with installed small LED screen, which presents BIOS error codes.

Where can I find a list of those errors. And I don't mean beep codes, but the "number" codes.

Ex after installing sound card, the motherboard startup fails with the code 15.

Example picture of code is here.

 

Exception code: 0xc0000135

We had a scheduled task that will extract data and generate an excel file.

It encountered the below error:

Faulting application name: openssl.exe, version: 0.0.0.0, time stamp: 0x52cb893c

Faulting module name: MSVCR90.dll, version: 6.3.9600.19153, time stamp: 0x5b93ffa7

Exception code: 0xc0000135

Fault offset: 0x00000000000ecf30

Faulting process id: 0x1080

Faulting application start time: 0x01d4b4e45d0a7dc9

Faulting application path: C:\OpenSSL-Win64\bin\openssl.exe

Faulting module path: MSVCR90.dll

Report Id: 9bdc4c13-20d7-11e9-80f2-005056ab5812

This is the first time we got the error. After this instance, the processing went to normal, that is, no errors encountered on the succeeding runs.

We have checked the file and it is existing. Looked for a number of possible root cause and solutions, and all are pointing to reinstallation of .NET Framework