Skip to content

Commit 5eeffcc

Browse files
[Release notes] Add known issue for Elastic Agent failing to enroll into Fleet (#1578)
Contributes to [#1800](elastic/ingest-docs#1800) by adding a known issue for release 9.x about Elastic Agent failing to re-enroll into Fleet. **Preview** [Fleet and Elastic Agent known issues](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1578/release-notes/fleet-elastic-agent/known-issues) **Corresponding PRs** 8.x: elastic/ingest-docs#1801
1 parent b460a3d commit 5eeffcc

File tree

1 file changed

+28
-2
lines changed

1 file changed

+28
-2
lines changed

release-notes/fleet-elastic-agent/known-issues.md

Lines changed: 28 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,37 @@ Known issues are significant defects or limitations that may impact your impleme
1212
% On [Month Day, Year], a known issue was discovered that [description of known issue].
1313
% For more information, check [Issue #](Issue link).
1414

15-
% **Workaround**
15+
% **Workaround**
1616
% Workaround description.
1717

1818
% :::
1919

20+
:::{dropdown} [Windows] {{agent}} is unable to re-enroll into {{fleet}}
21+
22+
**Applies to: {{agent}} 9.0.0, 9.0.1, 9.0.2 (Windows only)**
23+
24+
On April 9, 2025, a known issue was discovered where an {{agent}} installed on Windows and previously enrolled into {{fleet}} is unable to re-enroll. Attempting to enroll the {{agent}} fails with the following error:
25+
26+
```shell
27+
Error: the command is executed as root but the program files are not owned by the root user.
28+
```
29+
30+
For more information, check [Issue #7794](https://github.com/elastic/elastic-agent/issues/7794).
31+
32+
**Workaround**
33+
34+
Until a bug fix is available in a later release, you can resolve the issue temporarily using the following workaround:
35+
36+
1. Change the ownership of the {{agent}} directory:
37+
38+
```shell
39+
icacls "C:\Program Files\Elastic\Agent" /setowner "NT AUTHORITY\SYSTEM" /t /l
40+
```
41+
42+
2. After the output confirms all files were successfully processed, run the `enroll` command again.
43+
44+
:::
45+
2046
:::{dropdown} [macOS] Osquery integration fails to start on fresh agent installs
2147

2248
**Applies to: {{agent}} 9.0.0 and 9.0.1 (macOS only)**
@@ -25,7 +51,7 @@ On May 26th, 2025, a known issue was discovered that causes the `osquery` integr
2551

2652
For more information, check [Issue #8245](https://github.com/elastic/elastic-agent/issues/8245).
2753

28-
**Workaround**
54+
**Workaround**
2955

3056
As a workaround, you can manually restore the `osquery.app/` directory as follows:
3157

0 commit comments

Comments
 (0)