From 5007940d7290580b4f0cadd1bc177e3382a066f9 Mon Sep 17 00:00:00 2001
From: RitikRaj <evilgenious15@gmail.com>
Date: Fri, 9 Oct 2026 22:26:41 +0530
Subject: [PATCH] Remove outdated UseShellExecute requirement from
 ProcessWindowStyle.Hidden

---
 xml/System.Diagnostics/ProcessWindowStyle.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Diagnostics/ProcessWindowStyle.xml b/xml/System.Diagnostics/ProcessWindowStyle.xml
index 3ee53aa37d2..f132fe1b9f8 100644
--- a/xml/System.Diagnostics/ProcessWindowStyle.xml
+++ b/xml/System.Diagnostics/ProcessWindowStyle.xml
@@ -77,7 +77,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The hidden window style. A window can be either visible or hidden. The system displays a hidden window by not drawing it. If a window is hidden, it is effectively disabled. A hidden window can process messages from the system or from other windows, but it cannot process input from the user or display output. Frequently, an application may keep a new window hidden while it customizes the window's appearance, and then make the window style <see cref="F:System.Diagnostics.ProcessWindowStyle.Normal" />. To use <see cref="F:System.Diagnostics.ProcessWindowStyle.Hidden" />, the <see cref="P:System.Diagnostics.ProcessStartInfo.UseShellExecute" /> property must be <see langword="true" />.</summary>
+        <summary>The hidden window style. A window can be either visible or hidden. The system displays a hidden window by not drawing it. If a window is hidden, it is effectively disabled. A hidden window can process messages from the system or from other windows, but it cannot process input from the user or display output. Frequently, an application may keep a new window hidden while it customizes the window's appearance, and then make the window style <see cref="F:System.Diagnostics.ProcessWindowStyle.Normal" />.</summary>
       </Docs>
     </Member>
     <Member MemberName="Maximized">