From 792b13f2bc6221a805ecfb988c1f5d661a72c25d Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 28 Apr 2025 06:56:18 -0400 Subject: [PATCH 1/3] updates --- .../hello-for-business/includes/expiration.md | 12 +++++------- .../hello-for-business/includes/history.md | 9 ++++----- 2 files changed, 9 insertions(+), 12 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/includes/expiration.md b/windows/security/identity-protection/hello-for-business/includes/expiration.md index 88a546837d..9972048e4a 100644 --- a/windows/security/identity-protection/hello-for-business/includes/expiration.md +++ b/windows/security/identity-protection/hello-for-business/includes/expiration.md @@ -16,11 +16,9 @@ The default value is 0. | **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityexpiration)

`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityexpiration) | | **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity**| -> [!NOTE] -> Starting with Windows 11, version 23H2, Windows Hello uses Virtualization-based security (VBS) to isolate credentials on devices that support [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security). -> -> Starting with Windows 11, version 24H2, Windows Hello uses VBS to isolate credentials on all devices that have VBS enabled. -> -> On such devices, PIN expiration is not supported. - +> [!IMPORTANT] +> PIN expiration is not supported on: +> +> - Devices with [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security) enabled, since Windows Hello uses Virtualization-based Security (VBS) to isolate credentials. +> - Starting with Windows 11, version 24H2, on all devices that have with VBS enabled. diff --git a/windows/security/identity-protection/hello-for-business/includes/history.md b/windows/security/identity-protection/hello-for-business/includes/history.md index 2b1c3e1f91..46ac380c74 100644 --- a/windows/security/identity-protection/hello-for-business/includes/history.md +++ b/windows/security/identity-protection/hello-for-business/includes/history.md @@ -19,9 +19,8 @@ The default value is 0. | **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityhistory)

`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityhistory) | | **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity** | -> [!NOTE] -> Starting with Windows 11, version 23H2, Windows Hello uses Virtualization-based security (VBS) to isolate credentials on devices that support [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security). +> [!IMPORTANT] +> PIN history is not supported on: > -> Starting with Windows 11, version 24H2, Windows Hello uses VBS to isolate credentials on all devices that have VBS enabled. -> -> On such devices, PIN history is not supported. +> - Devices with [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security) enabled, since Windows Hello uses Virtualization-based Security (VBS) to isolate credentials. +> - Starting with Windows 11, version 24H2, on all devices that have with VBS enabled. \ No newline at end of file From 3607d17bf7cbc6318e8f6e555d784e903ac90f91 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 28 Apr 2025 07:01:54 -0400 Subject: [PATCH 2/3] update --- .../hello-for-business/includes/expiration.md | 2 +- .../identity-protection/hello-for-business/includes/history.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/includes/expiration.md b/windows/security/identity-protection/hello-for-business/includes/expiration.md index 9972048e4a..e0f48877ad 100644 --- a/windows/security/identity-protection/hello-for-business/includes/expiration.md +++ b/windows/security/identity-protection/hello-for-business/includes/expiration.md @@ -21,4 +21,4 @@ The default value is 0. > PIN expiration is not supported on: > > - Devices with [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security) enabled, since Windows Hello uses Virtualization-based Security (VBS) to isolate credentials. -> - Starting with Windows 11, version 24H2, on all devices that have with VBS enabled. +> - Starting with Windows 11, version 24H2, on all devices that have VBS enabled. diff --git a/windows/security/identity-protection/hello-for-business/includes/history.md b/windows/security/identity-protection/hello-for-business/includes/history.md index 46ac380c74..6d127a8f13 100644 --- a/windows/security/identity-protection/hello-for-business/includes/history.md +++ b/windows/security/identity-protection/hello-for-business/includes/history.md @@ -23,4 +23,4 @@ The default value is 0. > PIN history is not supported on: > > - Devices with [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security) enabled, since Windows Hello uses Virtualization-based Security (VBS) to isolate credentials. -> - Starting with Windows 11, version 24H2, on all devices that have with VBS enabled. \ No newline at end of file +> - Starting with Windows 11, version 24H2, on all devices that have VBS enabled. \ No newline at end of file From f38b92ba30aea8a10263102ffe55fcc5d2a5e5a3 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 28 Apr 2025 07:13:12 -0400 Subject: [PATCH 3/3] Updated link for Insider --- windows/configuration/taskbar/pinned-apps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/configuration/taskbar/pinned-apps.md b/windows/configuration/taskbar/pinned-apps.md index c577ca1d3c..dffa4197dc 100644 --- a/windows/configuration/taskbar/pinned-apps.md +++ b/windows/configuration/taskbar/pinned-apps.md @@ -112,7 +112,7 @@ You can change the apps pinned to the taskbar by modifying the `` [!INCLUDE [insider-setting](../includes/insider-setting.md)] -On [Windows Insider (Beta Channel)][KB-1] devices, you can allow certain pinned apps to be unpinned by users. This is useful when you want to allow users to unpin apps that are pinned via policy settings, but you don't want the pins to be pinned again during the next policy update cycle. +On [Windows Insider 22635.5305 (Beta Channel)][KB-1] devices, you can allow certain pinned apps to be unpinned by users. This is useful when you want to allow users to unpin apps that are pinned via policy settings, but you don't want the pins to be pinned again during the next policy update cycle. To use this option, add `PinGeneration="1"` to the pins you want to allow users to unpin. The value of `PinGeneration` can be any number, and it's used to identify the pin version. If the value changes, the app is pinned again during the next policy update cycle. This allows IT admins to repin an app, if needed. @@ -340,4 +340,4 @@ To provide feedback, open [**Feedback Hub**][FHUB] and use the category **Deskto [OEM-1]: /windows-hardware/customize/desktop/customize-the-windows-11-taskbar [WIN-1]: /windows/client-management/mdm/policy-csp-start [MEM-1]: /mem/intune/configuration/custom-settings-windows-10 -[KB-1]: /windows-insider/flight-hub +[KB-1]: https://blogs.windows.com/windows-insider/2025/04/25/announcing-windows-11-insider-preview-build-22635-5305-beta-channel/ \ No newline at end of file