# 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:** 4
**Page:** 1
### Author:  [@zx8086](https://discuss.elastic.co/u/zx8086)
#### Post date: [April 6, 2022, 5:58pm UTC](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790/1 "2022-04-06T17:58:19Z")
Upgrading from 8.1.1 to 8.1.2
Same happens from 8.0.0, seems the file it is looking for isn't downloaded first.
Windows 10 Enterprise
```auto
failed to dispatch actions, error: failed verification of agent binary: 2 errors occurred:
* fetching asc file from 'C:\Program Files\Elastic\Agent\data\elastic-agent-7f30bb\downloads\elastic-agent-8.1.2-windows-x86_64.zip.asc': open C:\Program Files\Elastic\Agent\data\elastic-agent-7f30bb\downloads\elastic-agent-8.1.2-windows-x86_64.zip.asc: The system cannot find the file specified.
* open C:\Program Files\Elastic\Agent\data\elastic-agent-7f30bb\downloads\elastic-agent-8.1.2-windows-x86_64.zip.sha512: The system cannot find the file specified.
```
---
### Author:  [@matled](https://discuss.elastic.co/u/matled)
#### Post date: [April 8, 2022, 3:29pm UTC](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790/2 "2022-04-08T15:29:21Z")
We have the same problem upgrading from 8.1.1 to 8.1.2 on Debian 11
```auto
[elastic_agent][error] failed to dispatch actions, error: failed verification of agent binary: 2 errors occurred:
* fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-8.1.2-linux-x86_64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-8.1.2-linux-x86_64.tar.gz.asc: no such file or directory
* open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-8.1.2-linux-x86_64.tar.gz.sha512: no such file or directory
```
---
### Author:  [@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")
@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…
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 4, 2022, 8:35am UTC](https://discuss.elastic.co/t/elastic-agent-upgrading-windows-elastic-agent-failing-via-ui/301790/4 "2022-11-04T08:35:02Z")