From ee8c88945d12e6de961840f98b484e283ef2fc11 Mon Sep 17 00:00:00 2001 From: Steve Dougherty Date: Mon, 31 Mar 2025 20:13:01 -0400 Subject: [PATCH 1/4] Fix spelling of "to" --- .../data-protection/bitlocker/recovery-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/operating-system-security/data-protection/bitlocker/recovery-process.md b/windows/security/operating-system-security/data-protection/bitlocker/recovery-process.md index 9da8c4e609..9fb7e9ec41 100644 --- a/windows/security/operating-system-security/data-protection/bitlocker/recovery-process.md +++ b/windows/security/operating-system-security/data-protection/bitlocker/recovery-process.md @@ -34,7 +34,7 @@ A recovery key can't be stored in any of the following locations: If you have access to the recovery key, enter the 48-digits in the preboot recovery screen. - If you are having issues entering the recovery password in the preboot recovery screen, or you can no longer boot your device, you can connect the drive to another device as a secondary drive. For more information about the unlock process, see [Unlock a drive](operations-guide.md#unlock-a-drive) -- If unlocking with recovery password doesn't work you can use the [BitLocker Repair tool](#bitlocker-repair-tool) to regain access yo your drive +- If unlocking with recovery password doesn't work you can use the [BitLocker Repair tool](#bitlocker-repair-tool) to regain access to your drive ### Self-recovery in Microsoft Entra ID From 5337965c2caf36aa10c8167d62d8a841d713230b Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 1 Apr 2025 14:22:47 -0700 Subject: [PATCH 2/4] add-comgmt-info --- windows/deployment/update/wufb-wsus.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md index 01e99c23c0..9ae243af65 100644 --- a/windows/deployment/update/wufb-wsus.md +++ b/windows/deployment/update/wufb-wsus.md @@ -11,7 +11,7 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 04/22/2024 +ms.date: 04/01/2025 --- # Use Windows Update client policies and WSUS together @@ -23,7 +23,8 @@ The Windows update scan source policy enables you to choose what types of update We added the scan source policy starting with the [September 1, 2021—KB5005101 (OS Builds 19041.1202, 19042.1202, and 19043.1202) Preview](https://support.microsoft.com/help/5005101) update and it applies to Window 10, version 2004 and above and Windows 11. This policy changes the way devices determine whether to scan against a local WSUS server or Windows Update service. > [!IMPORTANT] -> The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update. +> - The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update. +> - If you use Configuration Manager and have co-managed devices, see [Integrate with Windows Update client policies](/intune/configmgr/sum/deploy-use/integrate-windows-update-for-business-windows-10) for more information about configuring clients. ## About the scan source policy From 7526072c00a270c4c2eb8a4fd6e0f80ba34db687 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 1 Apr 2025 14:31:19 -0700 Subject: [PATCH 3/4] add-comgmt-info --- windows/deployment/update/wufb-wsus.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md index 9ae243af65..d2fdcadc77 100644 --- a/windows/deployment/update/wufb-wsus.md +++ b/windows/deployment/update/wufb-wsus.md @@ -39,13 +39,13 @@ We recommend using this policy on your transition from fully on-premises managed ## Default scan behavior -To help you better understand the scan source policy, see the default scan behavior below and how we can change it: +To help you better understand the scan source policy, see the following default scan behavior and how we can change it: -- If no policies are configured: All of your updates will come from Windows Update. +- If no policies are configured: All of your updates come from Windows Update. - If you configure only the WSUS server policy: - - On Windows 10: All of your updates will come from WSUS. - - On Windows 11: All of your updates will still come from WSUS unless you configure the specify scan source policy. + - On Windows 10: All of your updates come from WSUS. + - On Windows 11: All of your updates still come from WSUS unless you configure the specify scan source policy. - If you configure a WSUS server and deferral policies on Windows 10: All of your updates will come from Windows Update unless you specify the scan source policy or have disabled dual scan. - If you configure a WSUS server and the scan source policy: All of your updates will come from the source chosen in the scan source policy. From 85a29afd074bbf60124c8c58a19c0ec1bd3fe5cf Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 1 Apr 2025 15:04:31 -0700 Subject: [PATCH 4/4] add-comgmt-info --- windows/deployment/update/wufb-wsus.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md index d2fdcadc77..d320df4f52 100644 --- a/windows/deployment/update/wufb-wsus.md +++ b/windows/deployment/update/wufb-wsus.md @@ -23,8 +23,9 @@ The Windows update scan source policy enables you to choose what types of update We added the scan source policy starting with the [September 1, 2021—KB5005101 (OS Builds 19041.1202, 19042.1202, and 19043.1202) Preview](https://support.microsoft.com/help/5005101) update and it applies to Window 10, version 2004 and above and Windows 11. This policy changes the way devices determine whether to scan against a local WSUS server or Windows Update service. > [!IMPORTANT] -> - The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update. > - If you use Configuration Manager and have co-managed devices, see [Integrate with Windows Update client policies](/intune/configmgr/sum/deploy-use/integrate-windows-update-for-business-windows-10) for more information about configuring clients. +> - The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update. + ## About the scan source policy