mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
acrolinx
This commit is contained in:
parent
972a611403
commit
804d027c4d
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Add blocked key combinations
|
||||
description: Add blocked key combinations
|
||||
ms.assetid: f51892fc-0262-4b25-b117-6e131b86fb68
|
||||
ms.date: 01/13/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Browser Support
|
||||
ms.date: 03/30/2023
|
||||
ms.topic: article
|
||||
ms.topic: concept-article
|
||||
description: Learn about browser support in Kiosk Mode
|
||||
---
|
||||
|
||||
|
@ -1,16 +1,10 @@
|
||||
---
|
||||
title: Shell Launcher
|
||||
description: Shell Launcher
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: c65f1400-9d2a-406e-8b43-74eaafb0ccae
|
||||
ms.service: windows-iot
|
||||
ms.date: 06/07/2018
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: overview
|
||||
---
|
||||
|
||||
# Shell Launcher
|
||||
|
||||
Using Shell Launcher, you can configure a kiosk device to use almost any application or executable as your custom shell. The application that you specify replaces the default shell (explorer.exe) that usually runs when a user logs on.
|
||||
|
@ -1,11 +1,8 @@
|
||||
---
|
||||
title: Multi-App Kiosk
|
||||
ms.date: 08/16/2023
|
||||
ms.topic: article
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.topic: concept-article
|
||||
description: Learn about the Multi-App Kiosk in Windows IoT Enterprise.
|
||||
keywords: Lockdown, Multi-App, Kiosk
|
||||
---
|
||||
|
||||
# Assigned access multi-app kiosk
|
||||
|
@ -1,11 +1,8 @@
|
||||
---
|
||||
title: Assigned access Single-App Kiosk
|
||||
ms.date: 03/30/2023
|
||||
ms.topic: article
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.topic: concept-article
|
||||
description: Learn about the Single-App Kiosk in Windows IoT Enterprise.
|
||||
keywords: Kiosk Mode, Single-App
|
||||
---
|
||||
|
||||
# Assigned access single-app kiosk
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WEDL\_AssignedAccess
|
||||
description: WEDL\_AssignedAccess
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 2be8d294-db13-4494-bd5f-ba97ed89528e
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WEDL\_AssignedAccess
|
||||
|
||||
This Windows Management Instrumentation (WMI) provider class configures settings for assigned access.
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting
|
||||
description: WESL_UserSetting
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 73c5bb46-bf9e-4657-a5ae-88dbd14b79e8
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/02/2017
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting
|
||||
|
||||
This class configures which application Shell Launcher starts based on the security identifier (SID) of the signed in user, and also configures the set of return codes and return actions that Shell Launcher performs when the application exits.
|
||||
@ -92,7 +85,7 @@ Only one **WESL_UserSetting** instance exists on a device with Shell Launcher.
|
||||
|
||||
Shell Launcher uses the custom configuration defined for the SID of the user currently signed in, if one exists. Otherwise, Shell Launcher uses a custom configuration defined for a group SID that the user is a member of, if any exist. If multiple group custom configurations for the user exist, Shell Launcher uses the first valid configuration it finds. The search order is not defined.
|
||||
|
||||
If there is no custom configuration for the user’s SID or any group SIDs that the user is a member of, Shell Launcher uses the default configuration.
|
||||
If there is no custom configuration for the user's SID or any group SIDs that the user is a member of, Shell Launcher uses the default configuration.
|
||||
|
||||
You can find the SID for a user and any groups that the user is a member of by using the [whoami](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771299(v=ws.10)) command-line tool.
|
||||
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetCustomShell
|
||||
description: WESL_UserSetting.GetCustomShell
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 7bd2b50c-d566-4688-8fbd-1ea0197c1cde
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.GetCustomShell
|
||||
|
||||
This method retrieves the Shell Launcher configuration for a specific user or group, based on the security identifier (SID).
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetDefaultShell
|
||||
description: WESL_UserSetting.GetDefaultShell
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 26dc7e10-6e89-44e0-aec2-322676e8b2d1
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.GetDefaultShell
|
||||
|
||||
This method retrieves the default Shell Launcher configuration.
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.IsEnabled
|
||||
description: WESL_UserSetting.IsEnabled
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 567f57b5-f9c8-4129-8279-dd351028df5d
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.IsEnabled
|
||||
|
||||
This method retrieves a value that indicates if Shell Launcher is enabled or disabled.
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.RemoveCustomShell
|
||||
description: WESL_UserSetting.RemoveCustomShell
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 161eb289-e3b5-4d16-b367-f79f2b90f291
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.RemoveCustomShell
|
||||
|
||||
This method removes a Shell Launcher configuration for a specific user or group, based on the security identifier (SID).
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetCustomShell
|
||||
description: WESL_UserSetting.SetCustomShell
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 09fa040b-0fa1-4886-bfdd-8614eead0da8
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.SetCustomShell
|
||||
|
||||
This method configures Shell Launcher for a specific user or group, based on the security identifier (SID).
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetDefaultShell
|
||||
description: WESL_UserSetting.SetDefaultShell
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: fb4040bb-7cf2-4644-bf0f-d7d0274dd080
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.SetDefaultShell
|
||||
|
||||
This method sets the default Shell Launcher configuration.
|
||||
|
@ -1,17 +1,10 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetEnabled
|
||||
description: WESL_UserSetting.SetEnabled
|
||||
MSHAttr:
|
||||
- 'PreferredSiteName:MSDN'
|
||||
- 'PreferredLib:/library/windows/hardware'
|
||||
ms.assetid: 8dc373fe-37f9-45ca-bb0a-38f0e54feef1
|
||||
ms.service: windows-iot
|
||||
ms.subservice: iot
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
|
||||
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WESL_UserSetting.SetEnabled
|
||||
|
||||
This method enables or disables Shell Launcher.
|
||||
|
@ -66,8 +66,8 @@ Add these exclusions to UWF:
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> Windows 10 Enterprise does not include System Center Endpoint Protection. You can purchase licenses and install System Center Endpoint Protection independently.
|
||||
> Windows 10 Enterprise doesn't include System Center Endpoint Protection. You can purchase licenses and install System Center Endpoint Protection independently.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Service UWF-protected devices](service-uwf-protected-devices.md)
|
||||
|
@ -35,7 +35,7 @@ echo Restarting system
|
||||
goto UPDATE_EXIT
|
||||
```
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Service UWF-protected devices](service-uwf-protected-devices.md)
|
||||
- [UWF master servicing script](uwf-master-servicing-script.md)
|
||||
|
@ -62,7 +62,7 @@ When Windows update servicing is finished, the system will disable UWF servicing
|
||||
> [!NOTE]
|
||||
> If Windows updates cannot be installed or return an error, servicing will be disabled and the system will restart with UWF-protection re-enabled and all file and registry exclusions restored to their original pre-servicing state.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
- [UWF master servicing script](uwf-master-servicing-script.md)
|
||||
|
@ -45,7 +45,7 @@ You can use the [UWF_Volume.AddExclusion](uwf-volumeaddexclusion.md) and [UWF_Vo
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter WMI provider reference](uwf-wmi-provider-reference.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -45,7 +45,7 @@ You can use the [UWF_Volume.AddExclusion](uwf-volumeaddexclusion.md) and [UWF_Vo
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter WMI provider reference](uwf-wmi-provider-reference.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -163,7 +163,7 @@ Display-UWFState
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter WMI provider reference](uwf-wmi-provider-reference.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -37,7 +37,7 @@ You must use an administrator account to disable UWF.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Filter](uwf-filter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -60,7 +60,7 @@ After you run `uwfmgr filter disable`, restart the computer and enter the servin
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Filter](uwf-filter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -41,7 +41,7 @@ If the overlay becomes full while the system is performing a large amount of wri
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Filter](uwf-filter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -81,7 +81,7 @@ shutdown -r -t 5
|
||||
EXIT /B
|
||||
```
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Service UWF-protected devices](service-uwf-protected-devices.md)
|
||||
|
||||
|
@ -152,7 +152,7 @@ Set-OverlayType $DiskMode
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Unified Write Filter WMI provider reference](uwf-wmi-provider-reference.md)
|
||||
|
||||
|
@ -49,7 +49,7 @@ If the overlay type is RAM-based, your device must meet the following requiremen
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_OverlayConfig](uwf-overlayconfig.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -51,7 +51,7 @@ Before you can change the overlay type to RAM-based, your device must meet the f
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_OverlayConfig](uwf-overlayconfig.md)
|
||||
- [Overlay for Unified Write Filter (UWF)](uwfoverlay.md)
|
||||
|
@ -45,7 +45,7 @@ For more information about specific limitations and conditions when using the **
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter WMI provider reference](uwf-wmi-provider-reference.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -61,7 +61,7 @@ You should also be aware of the following items when you use the **GetOverlayFil
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Overlay](uwf-overlay.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -45,7 +45,7 @@ The critical threshold must be higher than the warning threshold.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Overlay](uwf-overlay.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -45,7 +45,7 @@ The warning threshold must be lower than the critical threshold.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Overlay](uwf-overlay.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -264,6 +264,6 @@ Clear-RegistryExclusions
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -52,7 +52,7 @@ You must restart the device before the registry key is excluded from UWF filteri
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -44,7 +44,7 @@ You must use an administrator account to change any properties or call any metho
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -46,7 +46,7 @@ You must use an administrator account to change any properties or call any metho
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -38,7 +38,7 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ If this method does not find any registry keys in the registry key exclusion lis
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ You must restart the device before the registry key is excluded from UWF filteri
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_RegistryFilter](uwf-registryfilter.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -44,7 +44,7 @@ Do not select **UwfServicingScr** as the screen saver and then click **Preview**
|
||||
|
||||
The next time the device enters UWF servicing mode, the UwfServicingScr.scr screen saver will use the custom settings.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Service UWF-protected devices](service-uwf-protected-devices.md)
|
||||
|
||||
|
@ -94,6 +94,6 @@ if ($nextSession) {
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -37,7 +37,7 @@ When this method is called, the system will leave servicing mode in the next ses
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Servicing](uwf-servicing.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -37,7 +37,7 @@ When this method is called, the system will enter servicing mode in the next ses
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Servicing](uwf-servicing.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -47,7 +47,7 @@ This method does not disable or enable Unified Write Filter (UWF). If you call t
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Servicing](uwf-servicing.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: Unified Write Filter (UWF) feature (uwf-turnonuwf)
|
||||
description: Unified Write Filter (UWF) feature (uwf-turnonuwf)
|
||||
ms.date: 05/20/2024
|
||||
ms.topic: article
|
||||
ms.topic: reference
|
||||
ms.custom: RS5
|
||||
---
|
||||
|
||||
@ -137,7 +137,7 @@ All configuration settings for UWF are stored in the registry. UWF automatically
|
||||
|
||||
UWF maintains configuration settings in the registry for the current session and for the next session after a device restart. Static configuration changes do not take effect until after a device restart, and these changes are saved in the registry entries for the next session. Dynamic configuration changes occur immediately and persist after a device restart.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Unified Write Filter]( index.md)
|
||||
|
||||
|
@ -306,6 +306,6 @@ Get-FileExclusions "C:"
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -50,7 +50,7 @@ However, you can exclude subdirectories and files under these items.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -41,7 +41,7 @@ You must use an administrator account to change any properties or call any metho
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -41,7 +41,7 @@ You must use an administrator account to call this method.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -42,7 +42,7 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ If **GetExclusions** does not find any files or folders in the file exclusion li
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ This method does not enable UWF if it is disabled; you must explicitly enable UW
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ You must use an administrator account to remove file or folder exclusions, and y
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -39,7 +39,7 @@ You must use an administrator account to remove file or folder exclusions, and y
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -44,7 +44,7 @@ Binding by volume name is considered more reliable than binding by drive letter,
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -37,7 +37,7 @@ Unprotecting the volume does not remove the [UWF_Volume](uwf-volume.md) entry or
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [UWF_Volume](uwf-volume.md)
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -38,6 +38,6 @@ This section describes the WMI provider classes for UWF.
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [uwfmgr.exe](uwfmgrexe.md)
|
||||
|
@ -209,6 +209,6 @@ The following list contains the UWF WMI provider methods that are not currently
|
||||
- [UWF_Volume.RemoveAllExclusions](uwf-volumeremoveallexclusions.md)
|
||||
- [UWF_Volume.SetBindByDriveLetter](uwf-volumesetbindbydriveletter.md)
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -128,6 +128,6 @@ You can often avoid this issue by using UWF to automatically initiate the shut d
|
||||
|
||||
Windows 10 19H1 and later will automatically restart if the maximum size of the overlay is exceeded.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
- [Unified Write Filter]( index.md)
|
||||
|
@ -20,7 +20,7 @@ UWF uses Windows Event Log to log events, errors and messages.
|
||||
* Error messages are logged in the **Applications and Services Logs\\Microsoft\\Windows\\UnifiedWriteFilter\\Admin** event log.
|
||||
* Informational messages are logged in the **Applications and Services Logs\\Microsoft\\Windows\\UnifiedWriteFilter\\Operational** event log.
|
||||
|
||||
## Related topics
|
||||
## Related articles
|
||||
|
||||
[Unified Write Filter]( index.md)
|
||||
|
||||
|
@ -47,7 +47,7 @@ sections:
|
||||
The smart card emulation feature of Windows Hello for Business verifies the PIN and then discards the PIN in exchange for a ticket. The process doesn't receive the PIN, but rather the ticket that grants them private key operations. There isn't a policy setting to adjust the caching.
|
||||
- question: Where is Windows Hello biometrics data stored?
|
||||
answer: |
|
||||
When you enroll in Windows Hello, a representation of your biometrics, called an enrollment profile, is created. The enrollment profile biometrics data is device specific, is stored locally on the device, and does not leave the device or roam with the user. Some external fingerprint sensors store biometric data on the fingerprint module itself rather than on Windows device. Even in this case, the biometrics data is stored locally on those modules, is device specific, doesn't roam, never leaves the module, and is never sent to Microsoft cloud or external server. For more details, see [Windows Hello biometrics in the enterprise](/windows/security/identity-protection/hello-for-business/hello-biometrics-in-enterprise#where-is-windows-hello-data-stored) and [Windows Hello face authentication](/windows-hardware/design/device-experiences/windows-hello-face-authentication).
|
||||
When you enroll in Windows Hello, a representation of your biometrics, called an enrollment profile, is created. The enrollment profile biometrics data is device specific, is stored locally on the device, and does not leave the device or roam with the user. Some external fingerprint sensors store biometric data on the fingerprint module itself rather than on Windows device. Even in this case, the biometrics data is stored locally on those modules, is device specific, doesn't roam, never leaves the module, and is never sent to Microsoft cloud or external server. For more details, see [Windows Hello biometrics in the enterprise](/windows/security/identity-protection/hello-for-business/how-it-works#biometric-data-storage) and [Windows Hello face authentication](/windows-hardware/design/device-experiences/windows-hello-face-authentication).
|
||||
- question: What is the format used to store Windows Hello biometrics data on the device?
|
||||
answer: |
|
||||
Windows Hello biometrics data is stored on the device as an encrypted template database. The data from the biometrics sensor (like face camera or fingerprint reader) creates a data representation—or graph—that is then encrypted before it's stored on the device. Each biometrics sensor on the device which is used by Windows Hello (face or fingerprint) will have its own biometric database file where template data is stored. Each biometrics database file is encrypted with unique, randomly generated key that is encrypted to the system using AES encryption producing an SHA256 hash.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Security Features Licensing And Edition Requirements
|
||||
description: Learn about Windows licensing and edition requirements for the features included in Windows.
|
||||
ms.topic: conceptual
|
||||
ms.topic: reference
|
||||
ms.date: 12/02/2024
|
||||
appliesto:
|
||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
|
Loading…
x
Reference in New Issue
Block a user