You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release-notes/fleet-elastic-agent/known-issues.md
+28-2Lines changed: 28 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,37 @@ Known issues are significant defects or limitations that may impact your impleme
12
12
% On [Month Day, Year], a known issue was discovered that [description of known issue].
13
13
% For more information, check [Issue #](Issue link).
14
14
15
-
% **Workaround**
15
+
% **Workaround**
16
16
% Workaround description.
17
17
18
18
% :::
19
19
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:
0 commit comments