> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/microsoft-.net-runtime-update-causes-remote-desktop-manager-to-crash.md).

# Microsoft .net runtime update causes Remote Desktop Manager to crash

Remote Desktop Manager crashing after a silent Microsoft .NET runtime update from Windows Update is a known issue fixed by restarting the application.

The Microsoft .NET runtime may be updated silently in the background by Windows Update while Remote Desktop Manager is running. In certain situations, this can result in unexpected application crashes.

This behavior is a [known issue reported to Microsoft](https://github.com/dotnet/runtime/issues/60144). At the time of writing, no official fix has been released. The issue typically occurs following a minor security update to the .NET runtime (for example, an update from .NET 8.0.7 to .NET 8.0.8).

Currently, the only available workaround is to restart Remote Desktop Manager if the crash occurs.

### Detailed analysis

Applications such as Remote Desktop Manager may experience crashes during .NET runtime updates pushed via Windows Update. This occurs because the update process removes the previous version of the runtime that the application is currently using. When the application tries to load a new assembly after the runtime has been updated in the background, it fails because the required files have been removed.

When updating the .NET runtime manually using the installer, the older version of the runtime is typically not deleted immediately. This prevents the issue of missing assemblies because the application can still access the necessary files from the previous version. However, when the update is performed via Windows Update, the older runtime version is removed, leading to potential crashes.

{% hint style="info" %}
For a complete detailed analysis of this issue, see [this comment](https://github.com/dotnet/runtime/issues/60144#issuecomment-2289137821) on the related GitHub issue.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/microsoft-.net-runtime-update-causes-remote-desktop-manager-to-crash.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.