Merge pull request #10465 from MicrosoftDocs/main

Publish main to live, Friday 10:30 AM PST, 12/13

windows/deployment/update/waas-wu-settings.md

@@ -213,6 +213,11 @@ To do this, follow these steps:
 
      * **7**:  Notify for install and notify for restart. (Windows Server 2016 and later only)
 
+   * ScheduledInstallEveryWeek (REG_DWORD):
+
+     * **0**: Do not enforce a once-per-week scheduled installation.
+     * **1**: Enforce automatic installations once a week on the specified day and time. (Requires ***ScheduledInstallDay*** and ***ScheduledInstallTime*** to be set.)
+
    * ScheduledInstallDay (REG_DWORD):
 
      * **0**: Every day.

windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-feature-update-summary-dashboard.md

@@ -48,6 +48,9 @@ The following information is available in the Summary dashboard:
 | Not ready | Total device count reporting the Not ready status. For more information, see [Not ready](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md#not-up-to-date-devices). |
 | % with the target feature update | Percent of [Up to Date](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md#up-to-date-devices) devices on the targeted feature update. |
 
+> [!NOTE]
+> The Windows Autopatch feature update report always displays the higher Windows version a device is taking. If target versions are identical, the report shows the most recent release or binding time. Release takes precedence over standalone DSS policy.<!-- MAXADO-9618138 -->
+
 ## Report options
 
 The following options are available: