From 67fe6827dca22e356ddac4e7277569396b2a6099 Mon Sep 17 00:00:00 2001 From: Meterel <114000274+Meterel@users.noreply.github.com> Date: Sat, 22 Aug 2026 12:00:12 +0200 Subject: [PATCH] Process.Kill isn't immediate Process.Kill isn't immediate as it's asynchronous like it's specified in the note and as confirmed by the Windows implementation that uses the asynchronous TerminateProcess function --- xml/System.Diagnostics/Process.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml index 7bb8fb247d3..e6d2a3106d1 100644 --- a/xml/System.Diagnostics/Process.xml +++ b/xml/System.Diagnostics/Process.xml @@ -1986,7 +1986,7 @@ You cannot cause processes on remote computers to exit. You can only view inform - Immediately stops the associated process. + Stops the associated process. To be added. The associated process could not be terminated. You are attempting to call for a process that is running on a remote computer. The method is available only for processes running on the local computer. @@ -2037,7 +2037,7 @@ You cannot cause processes on remote computers to exit. You can only view inform to kill the associated process and its descendants; to kill only the associated process. - Immediately stops the associated process, and optionally its child/descendent processes. + Stops the associated process, and optionally its child/descendent processes. When is set to , processes where the call lacks permissions to view details are silently skipped by the descendant termination process because the termination process is unable to determine whether those processes are descendants. The associated process could not be terminated.