# Elastic Agent - Upgrading Windows Elastic Agent failing via UI

**URL:** <https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790>\
**Category:** Elastic Observability\
**Tags:** elastic-agent\
**Created:** [April 6, 2022, 5:58pm UTC](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790 "2022-04-06T17:58:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [April 8, 2022, 4:39pm UTC](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790/3 "2022-04-08T16:39:39Z")

</div>

@matled,

I have seen this before and think the root problem is the same and requires Elastic to resolve their build and distribution process.

> [@Fleet Call to action - osquerybeat-7.15.0-linux-arm64.tar.gz' returned unsuccessful status code: 404](https://discuss.elastic.co/t/fleet-call-to-action-osquerybeat-7-15-0-linux-arm64-tar-gz-returned-unsuccessful-status-code-404/285065):
>
> When adding the Osquery Manager to a policy, I get the following error and the Elastic-Agent remains on UNHEALTHY until i remove the integration from the policy. The file doesn't exist on the repository, is it missing ? osquerybeat-7.15.0-linux-arm64.tar.gz Running Agent policy on Raspberry Pi 4 Model Linux 5.10.60-v8+ #1449 SMP PREEMPT Wed Aug 25 15:01:33 BST 2021 aarch64 GNU/Linux failed to dispatch actions, error: operator: failed to execute step sc-run, error: 2 errors occurred: \* pac…

---

_[View the full topic](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790)._