Add Documentation for Windows Defender Check

Documentation for
eclipse-platform/eclipse.platform.ui#1453

eclipse.platform.common/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm

@@ -14,11 +14,8 @@ <h1 class="Head">Startup and Shutdown</h1>
   <p class="Para">The <a class="command-link" href=
   'javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Startup)")'>
   <img src="PLUGINS_ROOT/org.eclipse.help/command_link.svg" alt="command link"> <strong>General &gt; Startup and
-  Shutdown</strong></a> preference page allows the selection of plug-ins to be automatically activated during workbench
-  startup.</p>
-  <p class="Para">Normally plug-ins are not activated until they are needed. However some plug-ins may specify that
-  they wish to be activated during startup. This preference page allows the selection of which of these plug-ins will
-  actually be activated during startup.</p>
+  Shutdown</strong></a> preference page allows you to configure the start up behaviour.</p>
+  <h2>General</h2>
   <table border="1" cellspacing="0">
     <tr>
       <th>
@@ -89,21 +86,43 @@ <h1 class="Head">Startup and Shutdown</h1>
         </div>
       </td>
     </tr>
-    <tr>
-      <td>
-        <div class="Para">
-          Plug-ins activated on startup
-        </div>
-      </td>
-      <td>
-        <div class="Para">
-          This option allows you to select which available plug-ins should be activated on startup.
-        </div>
-      </td>
-      <td>
-        <div class="Para"></div>
-      </td>
-    </tr>
   </table>
+  <h2>Windows Defender Exclusion Check</h2>
+  <p>On Mirosoft Windows 10 or later the <i>Microsoft Defender</i> can significantly slow-down the startup and 
+     overall performance of Eclipse-based applications.
+     These application can now detect if <i>Microsoft Defender</i> is active, inform you about that and if wanted 
+     can exclude itself from future <i>Microsoft Defender</i> scans.
+  </p>
+  <p>If <i>Microsoft Defender</i> is active, on first startup of a new installation, a dialog is shown.
+     Depending on your choice the exclusion is performed for the running installation or the 
+     <i>Microsoft Defender</i> configuration is left untouched. 
+     In both cases the choice is persisted and it is not asked again for this installation. 
+     If you choose to cancel the dialog (by clicking &quot;Cancel&quot; or &quot;Escape&quot;) the dialog is shown 
+     again on the next startup.
+  </p>
+  <p>In the &quot;Windows Defender Exclusion Check&quot; section of this preference page you get more detailed 
+     information about the <i>Microsoft Defender</i> handling, you can choose to disable the startup-check for 
+     all installations, run the exclusion check or to see the powershell script used to exclude the current 
+     installation.
+     Clicking &quot;Run exclusion check&quot; opens the startup dialog regardless of all persisted preferences. 
+     Clicking the &quot;Show Powershell script&quot; button, unfolds the code of that script for review.
+  </p>
+  <h3>Note</h3>
+  <p>Be aware that in general adding excludion could affect your computer's security level and therefore needs 
+      administrator privileges. 
+     The exclusion from <i>Microsoft Defender</i> scaning is done on process level. This means that 
+  <i>Microsoft Defender</i> won't real-time scan any file opened by the excluded process. 
+     This way the performance improvement applies to all files touched by the process and not only the jars 
+     forming the application. At the same time it allows scheduled or on demand scans to still check all files.
+   </p>
+   <p>
+     In general if you do not trust the installed application, plug-ins or content in the workspace, it is not 
+     recommended to apply any exclusion.
+  </p>
+  <h2>Plug-Ins Activated on Startup</h2>
+  <p>The &quot;plug-ins activated on startup&quot; section allows the selection of plug-ins to be automatically 
+     activated during workbench startup. Normally plug-ins are not activated until they are needed. However 
+     some plug-ins may specify that they wish to be activated during startup. This list allows the selection 
+     of which of these plug-ins will actually be activated during startup.</p>
 </body>
 </html>