fix files not in toc

.openpublishing.redirection.json

@@ -2477,7 +2477,7 @@
     },
     {
       "source_path": "windows/deploy/windows-10-upgrade-paths.md",
-      "redirect_url": "/windows/deployment/upgrade/windows-10-upgrade-paths",
+      "redirect_url": "/windows/deployment/upgrade/windows-upgrade-paths",
       "redirect_document_id": false
     },
     {

.openpublishing.redirection.windows-deployment.json

@@ -1594,6 +1594,16 @@
       "source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md",
       "redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-update-policies",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/deployment/update/PSFxWhitepaper.md",
+      "redirect_url": "/windows/deployment/update/forward-reverse-differentials",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/deployment/upgrade/windows-10-upgrade-paths.md",
+      "redirect_url": "/windows/deployment/upgrade/windows-upgrade-paths",
+      "redirect_document_id": false
     }
   ]
 }

windows/deployment/TOC.yml

@@ -79,6 +79,8 @@ items:
               href: update/media-dynamic-update.md
             - name: Migrating and acquiring optional Windows content
               href: update/optional-content.md
+            - name: Deploy feature updates for user-initiated installations
+              href: update/feature-update-user-install.md
             - name: Safeguard holds
               items:
                 - name: Safeguard holds
@@ -322,6 +324,8 @@ items:
           href: update/fod-and-lang-packs.md
         - name: Add fonts in Windows
           href: windows-missing-fonts.md
+        - name: Windows Updates using forward and reverse differentials
+          href: update/forward-reverse-differentials.md
 
     - name: Deployment tools
       items:

windows/deployment/update/feature-update-user-install.md

@@ -1,9 +1,9 @@
 ---
-title: Best practices - user-initiated feature update installation
+title: Deploy feature updates for user-initiated installations
-description: Learn recommendations and best practices for manually deploying a feature update for a user-initiated installation.
+description: Learn recommendations and best practices for manually deploying a feature update for a user-initiated installation during a fixed service window.
 ms.service: windows-client
 ms.subservice: itpro-updates
-ms.topic: best-practice
+ms.topic: how-to
 author: mestew
 ms.author: mstewart
 manager: aaroncz
@@ -14,14 +14,15 @@ appliesto:
 ms.date: 07/10/2018
 ---
 
-# Deploy feature updates for user-initiated installations (during a fixed service window)
+# Deploy feature updates for user-initiated installations
 
 Use the following steps to deploy a feature update for a user-initiated installation.
 
 ## Get ready to deploy feature updates
 
-### Step 1: Enable Peer Cache
+### Step 1: Enable peer cache
-Use **Peer Cache** to help manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
+
+Use **peer cache** to help manage deployment of content to clients in remote locations. Peer cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.
 
 [Enable Configuration Manager client in full OS to share content](/mem/configmgr/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update).
 
@@ -31,14 +32,14 @@ If you're deploying **Feature update to Windows 10, version 1709** or later, by
 
 %systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
 
-```
+```ini
 [SetupConfig]
 Priority=Normal
 ```
 
 You can use the new [Run Scripts](/mem/configmgr/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
 
-```
+```powershell
 #Parameters
 Param(
   [string] $PriorityValue = "Normal"
@@ -88,6 +89,7 @@ or documentation, even if Microsoft has been advised of the possibility of such
 The following sections provide the steps to manually deploy a feature update.
 
 ### Step 1: Specify search criteria for feature updates
+
 There are potentially a thousand or more feature updates displayed in the Configuration Manager console. The first step in the workflow for manually deploying a feature update is to identify the feature updates that you want to deploy.
 
 1. In the Configuration Manager console, select **Software Library**.
@@ -98,7 +100,8 @@ There are potentially a thousand or more feature updates displayed in the Config
 
 4. Save the search for future use.
 
-### Step 2: Download the content for the feature update(s)
+### Step 2: Download the content for the feature update
+
 Before you deploy the feature updates, you can download the content as a separate step. Do this download so you can verify that the content is available on the distribution points before you deploy the feature updates. Downloading first helps you avoid any unexpected issues with the content delivery. Use the following procedure to download the content for feature updates before creating the deployment.
 
 1. In the Configuration Manager console, navigate to **Software Library > Windows 10 Servicing**.
@@ -146,12 +149,14 @@ Before you deploy the feature updates, you can download the content as a separat
 9. On the **Completion** page, verify that the software updates were successfully downloaded, and then select **Close**.
 
 #### To monitor content status
+
 1. To monitor the content status for the feature updates, select **Monitoring** in the Configuration Manager console.
 2. In the Monitoring workspace, expand **Distribution Status**, and then select **Content Status**.
 3. Select the feature update package that you previously identified to download the feature updates.
 4. On the **Home** tab, in the Content group, select **View Status**.
 
-### Step 3: Deploy the feature update(s) 
+### Step 3: Deploy the feature update
+
 After you determine which feature updates you intend to deploy, you can manually deploy the feature update(s). Use the following procedure to manually deploy the feature update(s).
 
 1. In the Configuration Manager console, select **Software Library**.
@@ -200,21 +205,26 @@ After you determine which feature updates you intend to deploy, you can manually
 7. On the User Experience page, configure the following settings:
    - **User notifications**: Specify **Display in Software Center and show all notifications**.
    - **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window.
+
      > [!NOTE]
      > Remember that the installation deadline date and time will be well into the future to allow plenty of time for the user-initiated install during a fixed servicing window.
+
    - **Device restart behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify whether to suppress a system restart on servers and workstations after software updates are installed and a system restart is required to complete the installation.
 
      > [!IMPORTANT]
      > Suppressing system restarts can be useful in server environments or for cases in which you do not want the computers that are installing the software updates to restart by default. However, doing so can leave computers in an insecure state, whereas allowing a forced restart helps to ensure immediate completion of the software update installation.
+
    - **Write filter handling for Windows Embedded devices**: When you deploy software updates to Windows Embedded devices that are write filter enabled, you can specify to install the software update on the temporary overlay and either commit changes later or commit the changes at the installation deadline or during a maintenance window. When you commit changes at the installation deadline or during a maintenance window, a restart is required and the changes persist on the device.
 
      > [!NOTE]
      > When you deploy a software update to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window.
+
    - **Software updates deployment re-evaluation behavior upon restart**: Starting in Configuration Manager version 1606, select this setting to configure software updates deployments to have clients run a software updates compliance scan immediately after a client installs software updates and restarts. This enables the client to check for additional software updates that become applicable after the client restarts, and to then install them (and become compliant) during the same maintenance window.
 8. On the Alerts page, configure how Configuration Manager and System Center Operations Manager generate alerts for this deployment. You can configure alerts only when **Type of deployment** is set to **Required** on the Deployment Settings page.
 
    > [!NOTE]
    > You can review recent software updates alerts from the **Software Updates** node in the **Software Library** workspace.
+
 9. On the Download Settings page, configure the following settings:
    - Specify whether the client will download and install the software updates when a client is connected to a slow network or is using a fallback content location.
    - Specify whether to have the client download and install the software updates from a fallback distribution point when the content for the software updates isn't available on a preferred distribution point.
@@ -224,10 +234,12 @@ After you determine which feature updates you intend to deploy, you can manually
 
      > [!NOTE]
      > Clients request the content location from a management point for the software updates in a deployment. The download behavior depends upon how you have configured the distribution point, the deployment package, and the settings on this page. For more information, see [Content source location scenarios](/mem/configmgr/core/plan-design/hierarchy/content-source-location-scenarios).
+
 10. On the Summary page, review the settings. To save the settings to a deployment template, select **Save As Template**, enter a name and select the settings that you want to include in the template, and then select **Save**. To change a configured setting, select the associated wizard page and change the setting.
 11. Select **Next** to deploy the feature update(s).
 
 ### Step 4: Monitor the deployment status
+
 After you deploy the feature update(s), you can monitor the deployment status. Use the following procedure to monitor the deployment status:
 
 1. In the Configuration Manager console, navigate to **Monitoring > Overview > Deployments**.

windows/deployment/update/forward-reverse-differentials.md

@@ -1,6 +1,6 @@
 ---
 title: Windows Updates using forward and reverse differentials
-description: A technique to produce compact software updates optimized for any origin and destination revision pair
+description: A technique to produce compact software updates optimized for any origin and destination revision pair.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: reference
@@ -29,7 +29,7 @@ technique to build compact software update packages that are applicable to any
 revision of the base version, and then describe how Windows quality updates
 use this technique.
 
-## General Terms
+## General terms
 
 The following general terms apply throughout this document:
 
@@ -76,7 +76,7 @@ The flip side of express download is that the size of PSF files can be large dep
 
 In the following sections, we describe how quality updates use this technique based on forward and reverse differentials for newer releases of Windows  and Windows Server to overcome the challenges with express downloads.
 
-## High-level Design
+## High-level design
 
 ### Update packaging
 
@@ -98,7 +98,7 @@ Below is a high-level sequence of activities that the component servicing infras
 - Resolve any dependencies and install components.
 - Clean up older state (V<sub>N-1</sub>); the previous state V<sub>N</sub> is retained for uninstallation and restoration or repair.
 
-### **Resilient Hydration**
+### Resilient hydration
 
 To ensure resiliency against component store corruption or missing files that could occur due to susceptibility of certain types of hardware to file system corruption, a corruption repair service has been traditionally used to recover the component store automatically (automatic corruption repair) or on demand (manual corruption repair) using an online or local repair source. This service will continue to offer the ability to repair and recover content for hydration and successfully install an update, if needed.
 

windows/deployment/update/waas-quick-start.md

@@ -32,7 +32,7 @@ Some new terms have been introduced as part of Windows as a service, so you shou
 
 For more information, see [Overview of Windows as a service](waas-overview.md).
 
-For some interesting in-depth information about how cumulative updates work, see [Windows Updates using forward and reverse differentials](PSFxWhitepaper.md).
+For some interesting in-depth information about how cumulative updates work, see [Windows Updates using forward and reverse differentials](forward-reverse-differentials.md).
 
 ## Key concepts
 

windows/deployment/upgrade/windows-10-upgrade-paths.md

@@ -1,104 +0,0 @@
----
-title: Windows 10 upgrade paths
-description: You can upgrade to Windows 10 from a previous version of Windows if the upgrade path is supported.
-ms.service: windows-client
-ms.localizationpriority: medium
-author: frankroj
-manager: aaroncz
-ms.author: frankroj
-ms.topic: conceptual
-ms.collection:
-  - highpri
-  - tier2
-ms.subservice: itpro-deploy
-ms.date: 02/13/2024
-appliesto:
-  - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
----
-
-# Windows 10 upgrade paths
-
-> [!IMPORTANT]
->
-> This article deals with upgrading from Windows versions that are out of support. For a current version of this article, please see [Windows upgrade paths](windows-upgrade-paths.md) that deals with currently supported versions of Windows.
->
-> For more information, see:
->
-> - [Windows 8.1 support ended on January 10, 2023](https://support.microsoft.com/windows/windows-8-1-support-ended-on-january-10-2023-3cfd4cde-f611-496a-8057-923fba401e93).
-> - [Windows 7 support ended on January 14, 2020](https://support.microsoft.com/windows/windows-7-support-ended-on-january-14-2020-b75d4580-2cc7-895a-2c9c-1466d9a53962).
-> - [FAQ about Windows 7 ESU](/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq).
-
-## Upgrade paths
-
-This article provides a summary of available upgrade paths to Windows 10. You can upgrade to Windows 10 from Windows 7 or a later operating system. Paths include upgrading from one release of Windows 10 to later release of Windows 10. Migrating from one edition of Windows 10 to a different edition of the same release is also supported.
-
-If you're also migrating to a different edition of Windows, see [Windows edition upgrade](windows-edition-upgrades.md). Methods and supported paths are described on this page to change the edition of Windows. These methods require that you input a license or product key for the new Windows edition prior to starting the upgrade process. Edition downgrade is also supported for some paths. However, applications and settings aren't maintained when the Windows edition is downgraded.
-
-- **Windows 10 version upgrade**: You can directly upgrade any General Availability Channel version of Windows 10 to a newer, supported General Availability Channel version of Windows 10, even if it involves skipping versions. Work with your account representative if your current version of Windows is out of support. See the [Windows lifecycle fact sheet](/lifecycle/faq/windows) for availability and service information.
-
-- **In-place upgrade from Windows 7, Windows 8.1, or [Windows 10 General Availability Channel](/windows/release-health/release-information)** to Windows 10 LTSC isn't supported. Windows 10 LTSC 2015 didn't block this in-place upgrade path. This issue was corrected in the Windows 10 LTSC 2016 release, which only allows data-only and clean install options.
-
-  You can upgrade from Windows 10 LTSC to Windows 10 General Availability Channel if you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process using Windows setup. The Product Key switch needs to be used if you want to keep your apps. If you don't use the switch, the option **Keep personal files and apps** option is grayed out. The command line would be `setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`, using your relevant Windows 10 GA Channel product key. For example, if using a KMS, the command line would be `setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43`.
-
-- **Windows N/KN**: Windows "N" and "KN" SKUs (editions without media-related functionality) follow the same upgrade paths shown in the following tables. If the pre-upgrade and post-upgrade editions aren't the same type (for example, Windows 8.1 Pro N to Windows 10 Pro), personal data is kept but applications and settings are removed during the upgrade process.
-
-- **Windows 8.0**: You can't upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the [Windows 8.1 update](https://support.microsoft.com/help/15356/windows-8-install-update-kb-2919355).
-
-## Windows 10
-
-✔ = Full upgrade is supported including personal data, settings, and applications.
-
-D = Edition downgrade; personal data is maintained, applications and settings are removed.
-
----
-| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
-|---|---|---|---|---|---|
-| **Home**  | | ✔  | ✔  | ✔  | |
-| **Pro**   | D | | ✔   | ✔  | ✔  |
-| **Education**  | | | | | D  |
-| **Enterprise**  | | | | ✔ | |
-
----
-
-## Windows 8.1
-
-✔ = Full upgrade is supported including personal data, settings, and applications.
-
-D = Edition downgrade; personal data is maintained, applications and settings are removed.
-
----
-|  | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
-|---|---|---|---|---|---|
-| **(Core)**  | ✔  | ✔  | ✔  | ✔  | |
-| **Connected**   | ✔  | ✔  | ✔  | ✔  | |
-| **Pro**  | D   | ✔  | ✔   | ✔  | ✔  |
-| **Pro Student**  | D | ✔  | ✔  | ✔  | ✔  |
-| **Pro WMC**  | D  | ✔  | ✔  | ✔  | ✔  |
-| **Enterprise**  | | | | ✔  | ✔  |
-| **Embedded Industry** | | | | | ✔  |
-
----
-
-## Windows 7
-
-✔ = Full upgrade is supported including personal data, settings, and applications.
-
-D = Edition downgrade; personal data is maintained, applications and settings are removed.
-
----
-|  | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
-|---|---|---|---|---|---|
-| **Starter**   | ✔  | ✔  | ✔  | ✔  | |
-| **Home Basic**  | ✔  | ✔  | ✔  | ✔  | |
-| **Home Premium**  | ✔  | ✔  | ✔  | ✔  | |
-| **Professional**  | D  | ✔  | ✔ | ✔  | ✔  |
-| **Ultimate**  | D  | ✔   | ✔   | ✔  | ✔  |
-| **Enterprise**  |  |  |  | ✔  | ✔  |
-
----
-
-## Related articles
-
-- [Windows 10 deployment scenarios](../windows-deployment-scenarios.md).
-- [Windows upgrade and migration considerations](windows-upgrade-and-migration-considerations.md).
-- [Windows 10 edition upgrade](windows-edition-upgrades.md).