Elastic Defend known issue

Author: natasha-moore-elastic

docs/release-notes/8.19.asciidoc

@@ -35,6 +35,29 @@
 [[release-notes-8.19.9]]
 === 8.19.9
 
+[discrete]
+[[known-issue-8.19.9]]
+==== Known issues
+
+// tag::known-issue[]
+[discrete]
+.Intermittent blue screen due to conflict with Windows ODX in {elastic-defend}
+[%collapsible]
+====
+*Details* +
+An issue in {elastic-defend} on Windows can result in `KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL` or `PAGE_FAULT_IN_NONPAGED_AREA` bug checks (blue screens) when [Offloaded Data Transfer (ODX)](https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/offloaded-data-transfer) is used to copy files.
+
+*Workaround* +
+If you're unable to upgrade to the fixed version, you can disable the affected code by setting the `windows.advanced.kernel.filewrite` <<adv-policy-settings,advanced setting>> to `false` in your {elastic-defend} integration policy.
+
+*Resolved* +
+This issue is fixed in {agent} version 8.19.10.
+
+TIP: As long as the major and minor versions match, you can run a newer patch version of {agent} than the {stack}. For example, you can use 8.19.10 {agent} with 8.19.9 {stack}.
+
+====
+// end::known-issue[]
+
 [discrete]
 [[features-8.19.9]]
 ==== New features
@@ -60,6 +83,29 @@
 [[release-notes-8.19.8]]
 === 8.19.8
 
+[discrete]
+[[known-issue-8.19.8]]
+==== Known issues
+
+// tag::known-issue[]
+[discrete]
+.Intermittent blue screen due to conflict with Windows ODX in {elastic-defend}
+[%collapsible]
+====
+*Details* +
+An issue in {elastic-defend} on Windows can result in `KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL` or `PAGE_FAULT_IN_NONPAGED_AREA` bug checks (blue screens) when [Offloaded Data Transfer (ODX)](https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/offloaded-data-transfer) is used to copy files.
+
+*Workaround* +
+If you're unable to upgrade to the fixed version, you can disable the affected code by setting the `windows.advanced.kernel.filewrite` <<adv-policy-settings,advanced setting>> to `false` in your {elastic-defend} integration policy.
+
+*Resolved* +
+This issue is fixed in {agent} version 8.19.10.
+
+TIP: As long as the major and minor versions match, you can run a newer patch version of {agent} than the {stack}. For example, you can use 8.19.10 {agent} with 8.19.8 {stack}.
+
+====
+// end::known-issue[]
+
 [discrete]
 [[enhancements-8.19.8]]
 ==== Enhancements