{"id":24437,"date":"2022-05-11T14:49:15","date_gmt":"2022-05-11T12:49:15","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=24437"},"modified":"2022-05-15T00:07:20","modified_gmt":"2022-05-14T22:07:20","slug":"windows-11-update-kb5013943-erzeugt-fehler-0xc0000135","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/05\/11\/windows-11-update-kb5013943-erzeugt-fehler-0xc0000135\/","title":{"rendered":"Windows 11: Update KB5013943 results in application error 0xc0000135"},"content":{"rendered":"

\"Windows\"[German<\/a>]Microsoft released the cumulative update KB5013943 for Windows 11 (build 22000.675) on May 10, 2022. In the meantime, there are increasing reports of users who subsequently receive error 0xc0000135. This can occur with various applications, PowerShell, Event Viewer, services, etc. It is probably crystallizing into a problem with the .NET framework. Here is a brief overview of what I have found out so far.<\/p>\n

<\/p>\n

Windows 11 Update KB5013943<\/h2>\n

\"\"Cumulative Update KB5013943<\/a> raises the OS build on Windows 11 to 22000.675 (see alsoPatchday: Windows 11\/Server 2022-Updates (May 10, 2022)<\/a>). According to Microsoft, the update is intended to fix a known issue that can cause the screen to flicker when you boot a device in Safe Mode. This problem was caused by preview update KB5012643 for Windows 11 – I had addressed this in the blog post Windows 11: Preview update KB5012643 causes display issues in safe mode<\/a>. There Microsoft rolled the whole thing back via Known Issues Rollback (KIR). So now a new attempt takes place.<\/p>\n

Microsoft also writes that components that rely on explorer.exe, such as File Explorer, the Start menu and the taskbar, can also be affected by a problem and appear unstable. This is also supposed to be fixed by the cumulative update KB5013943<\/a>.<\/p>\n

Update causes App error 0xc0000135<\/h2>\n

Meanwhile, I have several reports that after installing the update KB5013943<\/a>, various applications quit with the error code 0xc0000135. The first report I encountered is here, and reads.<\/p>\n

For the first time, a Windows update totally destroyed my productivity. I had no issues with .exe files but now I do. I removed the Windows update but when I restarted my PC, it was back.<\/p>\n

The error I receive is: 0xc0000135, which means there is no .NET Framework installed on PC but it's not true.<\/p><\/blockquote>\n

In the Microsoft Answers forum there are also several threads like here<\/a> and here<\/a>. In the latter link, a user writes the following about May 10, 2022:<\/p>\n

So I just updated my laptop to the newest version of windows 11 and I am getting a lot of application errors and auto startup errors for apps. Is there a way to fix this? Error 0xc0000135<\/p><\/blockquote>\n

\"App<\/p>\n

By now it is clear that it can hit various applications. The comment here on the blog confirms this, with the error occurring on a \"brand new\" Windows 11 machine. According to the comment, many services, even rudimentary system programs like the event viewer, cannot be opened and report this error.<\/p>\n

What does the error 0xc0000135 mean?<\/h3>\n

The error code 0xc0000135 is an application error and simply stands for STATUS_DLL_NOT_FOUND. The application in question fails at startup because a required DLL library file is probably not found. This can affect, besides applications, also services from Windows or peripheral devices. Ultimately, it is no longer possible to work with the system.<\/p>\n

Based on the current error image and the above error description, it seems that an assembly from the .NET framework is not found. This reminds me of the problems with .NET applications with the Preview Update KB5012643 from the end of April 2022, see Windows 11: Preview Update KB5012643 causes issues with .NET Framework 3.5 applications<\/a>. There only uninstalling the update remained as a solution.<\/p>\n

Attempt to fix this application error<\/h2>\n

At this point, there are two approaches to fix this application error on Windows 11. One can try to see if repairing the .NET framework as well as the Windows Communication Foundation (WCF), if applicable, will do anything. If this does not help, uninstall the update.<\/p>\n

Fix #1: Repair .NET Framework 3.5<\/h3>\n

The first approach to possibly fix the error is to repair the .NET Framework 3.. There are two approaches to do this – one via Control Panel, one via Command Prompt (see<\/a>). Administrators can invoke a command prompt via Run as administrator<\/em> and then run the following commands:<\/p>\n

dism \/online \/enable-feature \/featurename:netfx3 \/all
\ndism \/online \/enable-feature \/featurename:WCF-HTTP-Activation
\ndism \/online \/enable-feature \/featurename:WCF-NonHTTP-Activation<\/p>\n

These instructions should reinstall the .NET framework and, if applicable, the Windows Communication Foundation (WCF). The WCF only needs to be activated if it was in use.<\/p>\n

Alternatively, it is possible to search for Features <\/em>in the Start menu search box and select the hit Turn Windows features on or off <\/em>the old Control Panel.<\/p>\n

\"Windows-Features\"<\/p>\n

There you have to activate the option for the .Net Framework 3.5 (and if used also WCF) again and restart the system. Maybe this will help.<\/p>\n

Fix #2: Uninstall update<\/h3>\n

In the article about the preview update , Microsoft suggests mitigating this problem by uninstalling the update. To do this, follow the steps below:<\/p>\n

    \n
  1. Go to Windows Update Settings<\/em> page using the Start<\/em> button.<\/li>\n
  2. In the Windows Update<\/em> settings window, select the option Show update history<\/em> and then the option Uninstall update<\/em>.<\/li>\n
  3. Then find the entry for the update in the list, select it and click the Uninstall <\/em>button.<\/li>\n<\/ol>\n

    After uninstalling, you can test whether the problem has been solved. If not, restart Windows 11 if necessary.<\/p>\n

    A list of more issues may be found at Windows, Office: May 2022 Patchday issues and mysteries<\/a><\/p>\n

    Similar articles:
    \n<\/strong>    Microsoft Office Updates (May 3, 2022)<\/a>
    \n    Microsoft Security Update Summary (May 10, 2022)<\/a>
    \n    Patchday: Windows 10-Updates (May 10, 2022)<\/a>
    \n    Patchday: Windows 11\/Server 2022-Updates (May 10, 2022)<\/a>
    \n    Windows 7\/Server 2008R2; Windows 8.1\/Server 2012R2: Updates (May 10, 2022)<\/a><\/p>\n

    MS-Patchday wrap-up: Issues with April 2022 updates<\/a>
    \n    Windows 11: Preview update KB5012643 causes display issues in safe mode<\/a>
    \n    Windows 11: Preview Update KB5012643 causes issues with .NET Framework 3.5 applications<\/a>
    \n    Windows Server 2022: March 2022 update KB5011497 breaks remote desktop gateway role<\/a>
    \n    Windows Server 2022: Fix for Remote Desktop problems with update KB5011497<\/a>
    \n    Windows Server 2022: Wie ist der Status beim RDS-Bug (RDCB-Rolle), verursacht durch KB5011497?<\/a>
    \n    Windows Update KB5012599: Microsoft plans fix for install error 0x8024200B and 0x800F0831<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    [German]Microsoft released the cumulative update KB5013943 for Windows 11 (build 22000.675) on May 10, 2022. In the meantime, there are increasing reports of users who subsequently receive error 0xc0000135. This can occur with various applications, PowerShell, Event Viewer, services, etc. … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[166,195,2643],"class_list":["post-24437","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issues","tag-update","tag-windows-11"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/24437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=24437"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/24437\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=24437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=24437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=24437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}