Home How To Windows 11 KB5013943 update causes 0xc0000135 application errors

Windows 11 KB5013943 update causes 0xc0000135 application errors

0

After installing the current Windows 11 KB5013943 cumulative update, customers are encountering 0xc0000135 errors while attempting to run applications.

The Windows 11 KB5013943 update provided a patch for a bug that caused.NET Framework 3.5 apps that used the Windows Communication Foundation (WCF) and Windows Workflow Foundation (WWF) components to fail to open.

KB5013943 update breaks .NET  applications

However, Microsoft’s remedy appears to have exacerbated the problem, as users of Windows 11 are reporting [1, 2, 3, 4, 5] a slew of applications that won’t launch after installing the KB5013943 update.

Affected software vary by user, however ProtonVPN, PowerShell, Event Viewer, Sound Blaster Command, KeePass, Visual Studio, Discord, ShareX, and others have been reported to have issues.

When you try to access the app with Windows 11, you get an error message that says, “The application failed to start properly (0xc0000135). To exit the programme, click OK “as illustrated in the diagram below.

 

“So I just upgraded my laptop to Windows 11 and I’m getting a lot of programme issues and auto starting difficulties. Is it possible to repair this? Error 0xc0000135, “a member on the Microsoft Answers forum wrote.

 

“Is anyone getting an error after KB5013628 / KB5013943 – The application was unable to start correctly (0xc0000135) unable to launch any.NET 4.8 programmes – bing/visual studio etc,” said one Twitter user.

 

The 0xc0000135 error means that the application was unable to start because it was unable to locate a DLL file essential for the programme to function properly. It appears that the application is looking for.NET DLLs and is unable to locate them in this case.

 

The problem is resolved by uninstalling the Windows 11 KB5013943 update, however the device is no longer protected against newly fixed vulnerabilities.

 

Users of Windows 11 have noticed that ensuring the.NET 3.5 framework is activated or reinstalling it might resolve the problem.
To do so, go to Control Panel > Programs > Turn Windows features on or off and tick the boxes for.NET Framework 3.5 (which includes.NET 2.0 and 3.0) and Net Framework 4.8 Advanced Services.

To enable the features, start a Windows 11 elevated command prompt (Run cmd.exe as an administrator) and run the commands.

 

If this does not fix the problem, you should uninstall the.NET features from the Control Panel and then reinstall them.

Finally, if all else fails, the KB5013943 update can be uninstalled. This is, however, strongly discouraged because it leaves your device vulnerable to the current security threats.